Solved: Windows 7 and D-links WBR 1310 incompatibility issues

Are there any new, definite fixes for the problem of compatibility between Windows 7 Professional and the D-Link WBR 1310 router? My brand new super-duper computer running Windows 7 won't recognize it as a viable means of getting on the internet. I am currently typing this on my Lenova laptop, XP Professional SP3, which runs fine wireless on the same router.

Regardless of what I've tried (enter static IP addresses, opening up a new Broadband connection), the system won't recognize the router. The computer worked fine, and accessed the internet easily on my son's network (he put it together with the supervision of two of his techy friends).

I am not technical enough to run diagnosis stuff, nor do I have the time to do so (in process of packing to move). Since I'm moving 300 miles away from my son, I'd like to get this fixed now, if it's something he has to do. If I just need to go out and buy a new router (even though I think this router is fine, and maybe Windows 7 needs to be more compatible to everything else out there), I guess I'll have to bite the bullet and do that. Are there any lists of DEFINITELY compatible routers out there?

 

Hi:

Connection from the new PC (which is a hand-built PC with an ASUS P8P67LE, Rev. 3 motherboard, 4GB ram online, SATA 6G, running USB 3, and a 750 GB hard-drive) is through cable modem, which is attached to the D-Link router. In other words, this computer IS more or less DIRECTLY connected to my ISP (Cogeco), not wireless. The laptop I am using to send these results (Lenova) is wireless and gets along fine with the D-Link.

Nothing was switched on or off on the PC when my son brought it from his place (where he had no problem getting on the internet with his router) to my place.

The only other issue I can think of that might be affecting this (but shouldn't) is that the ISP's cable connection runs from the ISP's modem TO my Vonage telephone (VOIP) box, then out to the D-Link, which is then attached directly to the computer (big yellow cable) with phone-like pinch connector that goes into the back of the computer. This worked fine for 5 years with the other (Dell4500) that fried a while ago.

Here is the information you asked for:

.................................................................................
Windows IP Configuration
Host Name . . . . . . . . . . . . : (myrealname) PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : F4-6D-04-47-B1-67
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ed76:155e:b511:4bfd%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 250899716
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-51-33-7C-F4-6D-04-47-B1-67
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{A8C4BCC5-F171-4AB8-B2E6-6BAB6FB23143}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
..........................................................................


As to compatibility of the D-Link WBR 1310 with Windows 7, I've scoured ample forums that would heartily argue that point, and very few came up with workable solutions (that ordinary, non-techy people can fix), that I could see. I think Microsoft rushes these things out to make more money, regardless of the aggravation they cause people who don't have bottomless pockets to replace all or most of their hardware and software every time one of their techies has a bright idea he thinks MIGHT work. I also think that companies like D-Link could do a better job of updating drivers for new operating systems, rather than expect us to run out and buy a new router, when the old one was working fine before that upgrade. (And truthfully, I don't like Windows 7, much prefer XP for looks and workability, but was told I couldn't have XP on the new system).

Hoping you have a solution for this mess!

 

Below is the laptop config file:
.............................

Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
Physical Address. . . . . . . . . : 00-1E-EC-0C-2B-18

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-C7-6A-07
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : November 19, 2011 12:31:43 PM
Lease Expires . . . . . . . . . . : November 19, 2011 3:31:43 PM
............................................................

The solution on the link you provided DID NOT WORK. I reset the IPv4 settings to automatic (it had numbers in it before that) and when I checked on the IPv6 settings they were already set to automatic.

For the heck of it, I ran another IPCONFIG and found that under Ethernet adapter the DHCP is NOW enabled, however it still shows as NOT ENABLED on the Tunnel adapter Teredo Tunneling Pseudo-interface and the Tunnel adapter isatap. The "autoconfiguration IPv4 address" now shows 169.254.75.253 (Preferred). The Subnet Mask changed to 255.255.0.0. I did not do Step 7 on the "advanced" thing because I haven't got a clue what that's all about, and they're not very forthcoming on helping with it. I am also not sure what to do for this piece of instruction ..... "Note
To install IPv4, run Command Prompt as an administrator, type netsh interface ipv4 install, and then press Enter" or IF it is necessary for me to do that (seems like it's already there anyways). All other settings are as per the above printout.


I also re-started the computer, just in case the settings needed to be refreshed. It is still giving me the same message - "Unidentified Network: No internet access".

I'm ready to just give up and go out and buy another router. Problem is, I'm not sure ANYTHING will work with the obtuse piece of expensive crap!

Any other ideas?

 

I did give it to you (as above), but here it is again, just fresh hot off the keyboard:

Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
Physical Address. . . . . . . . . : 00-1E-EC-0C-2B-18

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-1F-E1-C7-6A-07
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : November 19, 2011 2:01:43 PM
Lease Expires . . . . . . . . . . : November 19, 2011 5:01:43 PM

Nothing has changed either!

 

From the so-called faulty pc:

Windows IP Configuration
Host Name . . . . . . . . . . . . : (myrealname)-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : F4-6D-04-47-B1-67
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ed76:155e:b511:4bfd%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.75.253(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 250899716
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-51-33-7C-F4-6D-04-47-B1-67
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{A8C4BCC5-F171-4AB8-B2E6-6BAB6FB23143}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

RE YOUR SAFEMODE WITH NETWORKING SOLUTION:
The "new" PC - the one that won't access the internet - IS connected to the router directly by the YELLOW CONNECTOR cable that runs out of the backside of the modem directly into the back-end of the computer. If I disconnect the incoming ISP BLUE cable that runs from the modem into the Vonage box, and remove it from the Vonage box and put IT directly to the router, I will lose my phone service. If this is the "solution", then it's not going to work for me, as I don't have a "regular" phone line - it is Voice Over Internet Protocol - and my phone IS working presently, so I know the "juice" running from the internet through the Vonage box and into the router IS working properly. And it's working the the wireless laptop. AND worked previously with my other computer.

Just to be clear - the ISP cable runs into the ISP modem. From there, a dark blue cable runs into the back of the VONAGE modem box. From the VONAGE modem box, a light blue cable runs into the WAN port at the back of the router. From the router, a yellow cable runs from LAN Port 1 on the router TO the back of the faulty PC. My phone line connects into the Vonage Box. When I was without the BIG PC, I occasionally plugged the yellow cable directly into my laptop, rather than to run wireless, and it worked the same as the old PC did.

I have previously cycled the router (unplugged it for 10 seconds to have it reset) at my third post above AFTER I had done all of the changes you requested, restarted my computer, tried to get on the internet, ran through the internet diagnostic (which asked me to recycle the router). I doubt recycling it again will achieve anything new.

I only have the onboard Windows Firewall in operation - my son didn't install any anti-virus because he knows I want to use the "F-Secure" package that comes with my ISP if I can EVER get online to get to it. Nothing else was pre-installed.

To reiterate - any solutions that leave the Vonage modem box out of the mix are not workable for me. It has never been an issue before and shouldn't be one now.

 

When I (continually) tap F8 as the computer boots, it brings up a box asking me which drive I want to boot from, and lists the hard drive, and three other onboard drive/devices (DVD burners, CD) that are installed. If I hit "enter" on the main drive, it simply continues on as if I booted up regularly. There was no option to choose "safemode with networking".

In answer to the other questions, yes I can connect the laptop and everything works. This is how I've been operating the laptop for several weeks while waiting for the new PC to show up. The power on the router has been cycled several times since then, as we've had power failures recently (before hooking up to the new PC), and whenever there is a power failure, I have to unplug and re-plug the router to get it working properly again. I have also had to uplug/replug several times in the process of trying previous options provided by the onboard windows help files (useless crappola). The lights are operating properly.

I am giving up on this for today as I need to catch up on my packing. My son is bringing over a techy friend and they are going to review what I've done (this thread) and then hopefully find some other solution. If they do manage to come up with a solution short of firing the fracking thing off my balcony (which is what I'm tempted to do at this point), I'll post it here. Thanks for your help to this point.