Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[blackpool9]

I had to do a fresh Windows install on my PC this past weekend, so I figured I'd go ahead and install Windows 7 RC instead of an XP reinstall. Since the OS upgrade, I have been unable to maintain an internet connection with my DIR-655 when connected via an ethernet port. The machines in the house connected via the WLAN have no internet issues. What I see is the router taking an unusually long time to assign a network address to my machine. Once it does connect to the router, internet access is usually down. Not only that, but when I try to access the router's management console, I can usually only get one or two pages to load after admin login before I start getting "the router is measuring your internet connection" repeatedly. At that point the only way to get access to the console is to reboot either the desktop or the modem. I updated the firmware after this issue first began, but that didn't help anything. Right now I'm plugged into the DSL modem directly instead of the DIR-655, but I'd prefer to get back behind the DIR-655 firewall. Oh, and my mobo has two native 10/100/1000 ethernet ports, a Marvell and an nVidia. The same behavior is exhibited regardless of which ethernet port is being used. Does anyone have any idea what might be happening and how to fix this?

[davevt31]

Did you install the chipset and nic drivers for the board?  I was running 7 RC on a Evga 780iFTW that is a nVidia based board and I did not have any issues connecting with my 655.  Just go to the nVidia site, they have a bunch of drivers for Win7.

[blackpool9]

Yes, I installed Windows 7 compatible drivers for all hardware where available. If not, I used Windows Vista drivers. Both nVidia and Marvell offered Win7 drivers. Both drivers defaulted to active IPv4 and IPv6. I removed IPv6 support hoping that was the issue, but it didn't clear anything up.

[jason1722x]

Is DHCP running on your modem as well as the Dir 655? You could also try running MAC addresses with asigned LAN ip's.

[blackpool9]

I'll have to play around with DHCP when I get home (I'm at work now), but the 655 and the DSL router/modem had been playing nice for about a year before I reinstalled Windows. And initially after the upgrade I didn't change any settings on either router, nor did I update the firmware. I only started changing settings when I started seeing problems with the internet connectivity right after the upgrade. Since I wasn't changing anything other than the desktop's OS I didn't think that would cause any issue with the router. The 655 worked fine with the Linux OS running on my other hard drive, and I have been dual-booting Windows 7 and Windows XP Pro for a couple of months prior to the full-time switch to Windows 7, and never saw any problems with the 655 when I was using Win7.

I also tried switching the network cable connecting the modem with the 655, in case the cable had gone bad. No improvement there either.

[jason1722x]

Well if nothing was change with the hardware you would have to think the OS. Is your power saving feature in win 7 enabled? Drivers maybe, you running 64 bit? I have not played around with win 7 yet but since you had xp installed could win 7 be running in native xp mode.
I mean why try to fix something thats not broken.

[blackpool9]

As for fixing things that aren't broken, I needed more space so I put in a larger HD. Since I was going to do a full reinstall of Windows on the new HD, decided to go ahead with the upgrade to Win7 that I would be doing in Oct anyway. If I had seen any issues while running Win7 64-bit RC on the same hardware prior, I wouldn't have done it. But I have been running the Win7 64-bit RC install on a second partition for a couple of months with no connectivity issues and with no reconfiguration of the 655 (it even handled the port forwarding for my ftp server whether I was running XP or Win7). I'm racking my brain trying to figure out what could have changed when I went from dual-boot to single Win7 install that could have caused the 655 to give me so many problems.

[jason1722x]

Well if I understand you right you still have DHCP running on the Dir 655, if so go into Advanced tab->Network Filter and register your MAC's and then go to Setup-> Network Settings and under Add DHCP Reservation asign a lan ip for your computer.
This way the will not be searching or assigning a random ip for your system. You will not know what the LAN ip is, plus you can ping it from Tools-> System Check.

But hey thats what I would do.
good luck

[blackpool9]

Tried turning off DHCP and assigning an IPv4 address to the ethernet adapter. No joy. Then I tried turning DHCP back on and resetting the ethernet adapter but adding an address reservation for my MAC address. No joy. Tried deleting both ethernet adapters from device management and rebooting to force reload of the drivers. No joy.

The more I think about this, the less likely I think this is an OS or driver issue. Why would Windows 7 and my ethernet ports have no problem interacting with my crappy little Westell DSL modem/router, but be nearly incapable of communicating with my D-Link?

Got a better handle on what's going on with the console during these most recent experiments. When I manage to get access to the management console on the router, I can go almost anywhere on the console, as long as I do it FAST. For instance, when I went to the wireless network setup (after another router re-set), if I adjusted the transmission settings and set up a WAP password, when I would hit "save settings" I would get the "Please Wait....router is testing network speed" page for almost a minute, and when the console management page returned none of my settings were saved. But when I got to the same page, quickly changed the transmission type, and hit "save", it would save quickly and be right back on the console. If I tried to type in a WAP password and hit "save" I'd get "please wait..." and a save failure. But if I then used a text editor to type in the WAP password, get it to the clipboard, get the console management page, paste in the password and hit save, it would work just as expected. It's like the router is renegotiating with the ethernet adapter (and the Westell) every 15 seconds or so, until it finally gives up and freezes. At that point a desktop reboot doesn't help, only a forced router reboot allows any communication with the router.

I appreciate everyone's attention and help on this.

[blackpool9]

I've narrowed this down to an issue between the DIR-655 and the Westell DSL. I connected a Windows XP machine to the 655 and had the same problem. Now none of the PCs in the house, including the wireless connectors, have anything but spotty internet connections through the 655. If I plug my Win7 machine into the 655 with the internet cable disconnected, I am able to navigate anywhere in the management console without issue. The moment the internet cable is reconnected, the "Please Wait..." page returns. I've tried setting up the 655 in the Westell as the DMZ, as the Static NAT, and I've tried having it connected to the Westell with no DMZ or Static IP and with the Westell firewall turned off. I've switched cables from the DSL to the internet port on the 655. Nothing has made a difference.

Did my internet port go bad on the 655 and it's just a coincidence it happened the same time I did the OS install? Or is there a firmware issue here?