Print

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

[kengo]

Using a DIR-825, but another general question...  I have about 20 devices on my home network.  They all work except one, my computer!  My Dell D830 laptop works fine on the network wirelessly, but not when wired.  Actually, skype works, but outlook email and browsers don't work.  So I am getting some connection.  I have also tried with different cables and different access points, no change.  I have a similar network setup at another location and my wired access works just fine there (so it is not the laptop NIC).  It used to work ok, but became a problem after I replaced my old router with the DIR-825. I'm sure it is user error and not the 825's fault though.  Any ideas?

When I connect wirelessly, ipconfig shows all the addresses as expected, 192.168... but when I connected by wired ethernet cable, the IP addresses are some crazy numbers that I don't recognize.  That is the problem.  DHCP for wired connections works fine at location 2 but not at location 1.

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
   Physical Address. . . . . . . . . : 00-------
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c959:894d:d1ed:6f%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 116.86.68.15(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Lease Obtained. . . . . . . . . . : Wednesday, August 04, 2010 10:25:02 PM
   Lease Expires . . . . . . . . . . : Thursday, August 05, 2010 4:53:36 AM
   Default Gateway . . . . . . . . . : fe80::226:5aff:fefb:5b26%12
                                       116.86.68.1
   DHCP Server . . . . . . . . . . . : 172.17.0.48
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
   Physical Address. . . . . . . . . : 00--------
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80xxxxxx(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.30(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, August 04, 2010 10:34:22 PM
   Lease Expires . . . . . . . . . . : Wednesday, August 11, 2010 10:34:22 PM
   Default Gateway . . . . . . . . . : fe80::226:5aff:fefb:5b26%11
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled



My configuration is:
Cable modem -> DIR-825 router -> dlink 24-port gigabit switch
then off the 24-port switch are:
DAP-1353 wireless access point extender
5-port dlink gigabit switch
4 Windows 7 pc's. 3 XP pc's. a bunch of stereo equipment, tv, xbox, etc.

[rickm1350]

did you try to release the IP address it has, then renew?

if you're using win 7, click on the windows button on lower left of the screen.  When your programs pop up.. in the little search box, type CMD and hit the Enter key on your keyboard, this will bring up a command prompt.

From a command prompt, type:   ipconfig /release

that should release any IP address your computer may have.

next, from the command prompt, type:  ipconfig /renew

that should grab a new IP address from your router.

If you want to see what the new IP address is, just type in: ipconfig 

[smlunatick]

I have seen some software firewalls and anti-virus that will block a wireless network name (aka SSID.) The software may need to be told to trust the network.

[kengo]

fix: i disabled IPv6 and that did the trick.  disabling IPv6 permanently requires a regedit; otherwise it gets turned back on every reboot.

[kengo]

disabling IPv6 only worked temporarily.  but i think i found the culprit.  my cable box has a DHCP server so I had 2 on the network at the same time.  I disabled it and things have been working for awhile now.