@%$#&@(%*#^@$! DLink wireless router. Just bought it and can't get it to work right.

[kestrel91316]

8 hours of struggle last Saturday, hour or ore on the phone with tech support, finally got it working FABULOUSLY!! Then I got the bright idea to try to hook up my wireless printer to the network and now the router just gives me a really really really slow and completely useless connection, or none at all.

I have redone the manual setup multiple times, all to no avail.

Help.

Dell Vostro laptop new last summer, Windows 7, Time Warner cable internet.

[Melissa G]

1. ^%^&E%!! Lynsys Router did that hell thing to me

on Thursday (yesterday). Sympathy to you. I starter at 12 and went until 8pm when I finally said

It's halfway up. Taking a break until Monday.

Hope yours works out better, sooner..

[ChromeFoundry]

2. Can you post a little more info...

Last edited Sat Mar 3, 2012, 12:13 AM - Edit history (1)

What model and version of DLink WiFi router are you configuring?
What model of Cable Modem do you have?
Are you trying to configure the normal 192.168.1.X network with a mask of 255.255.255.0?
Are your clients setup as DHCP (get IP address from network)?
What did you have before? How was it configured? Do you see the SSID from your clients?
Can you connect? What speed and status do you see after you connect?

[HopeHoops]

3. I've never had a DLink fail on me, but it actually does sound like a hardware problem.

Make sure you keep the receipt and, if necessary, return it before the store's return policy expiration. In the mean time, get whatever you can out of Time Warner, DLink, and your printer's manufacturer in that order. What you described isn't typical.

On Edit: Don't bother with Dell tech support - it is useless.

[kestrel91316]

4. Hey, I totally love my Dell tech support - they ALWAYS get me fixed right up.

But this isn't a situation for Dell, it's clearly the router that's the problem.

[HopeHoops]

7. No, it isn't a Dell problem, but my experiences with their tech support have been terrible.

HP on the other hand is amazing.

[angryfirelord]

5. I'm inclined to agree

The only other thing I could think of that would cause it is if there were some conflicting IP addresses (if they were all static IPs), but it certainly shouldn't fail because another device connects to it. If a hard reset doesn't fix it, then I would take it back for a refund.

[HopeHoops]

6. It should be using NAT. It's pretty unlikely to get an IP conflict.

I'm inclined to agree that it is likely a bad unit, but that's just a real shocker to me.