D-Link DP-311U Wireless Print Server, 1-USB Port, 802.11b, 11Mbps

I will never buy another D-Link product. After buying this wireless print server, I followed all install instructions but couldn't get it to work. I assumed it was me, so I paid a PC technician to help me out. He spent 2 hours on the phone with D-Link tech support troubleshooting, and they decided the unit was faulty.When I called customer service to find out how to exchange it, they sent me back to tech support and made me troubleshoot again before they would give me a return merchandise authorization (RMA). After I paid a skilled tech more than $100 to be on with their techs!!! Overall I had to talk to three people and spent 45 minutes on hold to get the RMA.Finally I got my RMA and sent the unit back, with all documentation and accessories. When they sent me a replacement, it was just the unit, no manuals, no software, not even an AC adaptor. So I had to spend 20 more minutes with their excruciatingly annoying hold music to talk to customer service. They "promised" me the AC adaptor and manual, but who knows if I'll ever actually get it.Add to that a complete lack of contrition over selling me a bad product in the first place, and I'm just really disappointed in the whole experience and feel like I've wasted a lot of time and money (price of the unit + tech guy). If I ever get the thing running (with my Netgear router and brother MFC6800 printer) I'll post again about how/if it works.Update: They did send me the AC power cord and I was able to get the thing up and running but only after blundering through on my own - I found the documentation unhelpful in that the instructions stopped 1/2 through the setup process. So, although I now enjoy having my printer remote from my computer, I still won't ever buy another product from D-Link.

My network is two wireless XP laptops and a Linksys 802.11b router so I was a little worried about mixing networking brands - but it worked out fine. Virtually no slowdown compared to having the printer directly connected to the laptop and I print some pretty big files. Setup wasn't too bad (~15-20 min staring at the manual really confused, 5 min reading amazon.com reviews, ~20-30 min installation). Much like what Hafizullah said, it's better to config in steps: configure the printer in the wired configuration and then get it to work wirelessly. Since the manual is mostly useless, here's what I did:1. Wire it up (connect the print server to the router with an ethernet cable and the printer to the print server by USB).2. Turn on printer, power on the print server (after startup sequence of ~20 sec, ethernet light should be lit).3. At this point open up a browser and go to "192.168.0.10" and the print server config utility should start.4. Click on the "configuration" tab and set: password, connection mode (mine is infrastructure), ESS-ID (your network's name), wireless channel, WEP (# bits and password). It's important to type the WEP key in exactly with no spaces or dashes because the utility won't give any error message if the password is wrong. Click 'save'.5. Click on the "Network" tab and change the IP address if you want. It has to be within the range of assignable IP addresses for your wireless network (e.g. my router assigns from 192.169.1.1 to 192.169.1.101, so I set the print server to 192.169.1.2). Make sure to set "manually assign" otherwise you won't know what address your printer is on! I think the workgroup has to be set, but I'm not sure (I set it to the name of the wireless network).. Click 'save'.6. At this point you should be able to print a test page. Click on the "tools" tab and click to print a test page. If it prints, you're in business.7. Now you can set up the printer drivers. The instructions are actually pretty good for this, so use them here. Once that's done, try printing something that isn't a test page to make sure the printer itself is set up OK.8. Now to configure the wireless portion. Unplug the ethernet cable, and click the reset button (recessed in the back of the print server). Once it finishes booting, the "wireless" light should be on or blinking. If so then you should be done. Try printing something.. I didn't have everything correctly set up initially, so this step took a few minutes. I think everything necessary to set was covered in #4.Good Luck!

Although I'm not a computer novice, this unit was hard to install. While the green LAN (Ethernet) light came on when plugged into the router or DSL modem, it didn't work when plugged directly into my PC or laptop. Someone here wrote that in such case you need a "crossover" ethernet cable (or adapter). THANK YOU! I learned that routers have the smarts to figure our what type of unit is plugged in, and automatically assign transmit and receive signals to the proper pins. My PC and laptops didn't do that, and the DP-311U wasn't smart enough either. Hence I needed the cross-over cable (just for the one-time setup). Sad thing, before I figured this out, I spoke with 2 people at D-Link's technical support; we spent easily two hours. But neither one suggested the cross-over cable. They must have had tons of calls like this before. Of course, the manual says mothing about this either. Amazing how they waste time and money.

I cannot write a bad review on a product that is not compatible to my computer (Windows 7). I was simply attempting to solve a problem for cheap.

The server works great on my HP 2200. It's fast, reliable and can be easily velcro-ed to the side. Downside, it's got to be the single most difficult piece of hardware I've ever had to setup. NO WIZARD! Anyway, I followed the instructions to the letter and after setting my network IP address back to normal, the box would cease to work. I tried a bunch of things to get it to work, but in the end it was something simple. I'm using a Netgear WGR614v6 which is set to be a DHCP server. The list of available IP addresses missed the default 192.168.0.10 so the computer could not recognize it. I changed the DP-311U's default IP address in the PSadmin program and BAM! Works first try! The morale of the story, if you're running a DHCP server, check the list of IP addresses.