Unidentified Network

I just installed Windows 7 64-bit on a system and can not get a connection to my router which I am connected to through a cable. (interestingly I first did a 32-bit install and it worked fine)

I do not have Bonjour or that funky string in my Services.
I installed the updated driver for my adaptor.

I have tried setting the IP address manually - did not work
(I used all the information from this PC that is working for the one that is not - yes I did give it a different IP address)

I have disabled IPv6 - did not work

I have un-installed the Adapter - did not work

I have rebooted the computer and the router - did not work.

I have tried to PING my router - packets sent = 4, received = 0, Lost = 4 (100%)

I have tried ipconfig/release and ipconfig renew and I get this

An error occurred while renewing interface Local Area Connection: unable to contact your DHCP server. Request has timed out.

Here is my current Ipconfig/all

Ethernet adapter local area connection:

Connection-specific DNS Suffix . :
Description .............................: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical address ......................: 00-1C-25-3D-CA-E0
DHCP Enabled ..........................: yes
Autoconfiguration Enabled ..........: yes
Autoconfiguration IPv4 Address....: 169.254.173.101 (Preferred)
Subnet Mask ........................... : 255.255.0.0
Default Gateway .......................:
NetBIOS over Tcpip ...................: Enabled

A few observations - shouldn't my Subnet mask be 255.255.255.0
and shouldn't I have a Default Gateway address?

Any suggestions?

jkjs said:

I just installed Windows 7 64-bit on a system and can not get a connection to my router which I am connected to through a cable. (interestingly I first did a 32-bit install and it worked fine)

I do not have Bonjour or that funky string in my Services.
I installed the updated driver for my adaptor.

I have tried setting the IP address manually - did not work
(I used all the information from this PC that is working for the one that is not - yes I did give it a different IP address)

I have disabled IPv6 - did not work

I have un-installed the Adapter - did not work

I have rebooted the computer and the router - did not work.

I have tried to PING my router - packets sent = 4, received = 0, Lost = 4 (100%)

I have tried ipconfig/release and ipconfig renew and I get this

An error occurred while renewing interface Local Area Connection: unable to contact your DHCP server. Request has timed out.

Here is my current Ipconfig/all

Ethernet adapter local area connection:

Connection-specific DNS Suffix . :
Description .............................: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical address ......................: 00-1C-25-3D-CA-E0
DHCP Enabled ..........................: yes
Autoconfiguration Enabled ..........: yes
Autoconfiguration IPv4 Address....: 169.254.173.101 (Preferred)
Subnet Mask ........................... : 255.255.0.0
Default Gateway .......................:
NetBIOS over Tcpip ...................: Enabled

A few observations - shouldn't my Subnet mask be 255.255.255.0
and shouldn't I have a Default Gateway address?

Any suggestions?

The 169.254.173.01 is a local IP (of course).

I am thinking the most obvious which is driver.

Can you look in device manager to see if it is there and working.

Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If your driver is missing, or there is a yellow triangle on it, you will need to update it.


Let us know if you need additional help


Ken

Hi Ken

The address " 169.254.173.101" is not relevant to my system. My local IP addresses are of the 192.168.0.XXX variety.

I have been reading here and elsewhere that somehow my system can't find the Default Gateway to have a local IP address assigned using the DHCP (I think I am using the terminology correctly). That is why I tried manually entering all the information in and I still can't connected.

If you notice, my Default Gateway is empty.

The system works fine when I am using Windows 7 32-bit. It is only when I upgrade to Windows 64-bit that I have the problem.

Is there a way to use the 32-bit driver in the 64-bit OS?

thanks

joe

p.s. I installed the 64-bit driver for the ethernet card from the manufacturer. That didn't help

I had problems with mine once - the small reset button on the bottom of the router seemed to solve it, for me at least. The only trouble is you have to reopen/forward your ports if you have any set up.

allend66 said:

I had problems with mine once - the small reset button on the bottom of the router seemed to solve it, for me at least. The only trouble is you have to reopen/forward your ports if you have any set up.

I have seen this as a solution as well but have't tried it because I have one system that connects via a LAN cable with no problem and one that won't. To me it seems the issue is with the system that can't connect and not the router. yes?

jkjs said:

allend66 said:

I had problems with mine once - the small reset button on the bottom of the router seemed to solve it, for me at least. The only trouble is you have to reopen/forward your ports if you have any set up.

I have seen this as a solution as well but have't tried it because I have one system that connects via a LAN cable with no problem and one that won't. To me it seems the issue is with the system that can't connect and not the router. yes?

Incorrect, most routers will require a firmware update in order to work properly with Windows 7 machines. As it stands you aren't getting anything from your router at all, no default gateway, IP,or subnet nothing at all.

I would suggest you update your firmware on your router as it's been know to fix this exact problem on many occasion. If that doesn't fix the problem then it can only be a driver problem of some sort.

chev65 said:

jkjs said:

allend66 said:

I had problems with mine once - the small reset button on the bottom of the router seemed to solve it, for me at least. The only trouble is you have to reopen/forward your ports if you have any set up.

I have seen this as a solution as well but have't tried it because I have one system that connects via a LAN cable with no problem and one that won't. To me it seems the issue is with the system that can't connect and not the router. yes?

Incorrect, most routers will require a firmware update in order to work properly with Windows 7 machines. As it stands you aren't getting anything from your router at all, no default gateway, IP,or subnet nothing at all.

I would suggest you update your firmware on your router as it's been know to fix this exact problem on many occasion. If that doesn't fix the problem then it can only be a driver problem of some sort.

I checked. My router has the most recent firmware installed so it must be a driver issue.

Sounds like MAC Adress Filtering in the router. I use this for extra protection at router level and sounds exactly like the MAC address isnt in the filter to be allowed so wont connect. Try a reset as JKJS suggested. Most routers allow you to back up your current settings so if it doesnt resolve it you can reload the same settings.

Whats the make/model of router?

The Router is a Linksys E3000.

jkjs said:

Hi Ken

The address " 169.254.173.101" is not relevant to my system. My local IP addresses are of the 192.168.0.XXX variety.

I have been reading here and elsewhere that somehow my system can't find the Default Gateway to have a local IP address assigned using the DHCP (I think I am using the terminology correctly). That is why I tried manually entering all the information in and I still can't connected.

If you notice, my Default Gateway is empty.

The system works fine when I am using Windows 7 32-bit. It is only when I upgrade to Windows 64-bit that I have the problem.

Is there a way to use the 32-bit driver in the 64-bit OS?

thanks

joe

p.s. I installed the 64-bit driver for the ethernet card from the manufacturer. That didn't help

Nope you cant use the 32bit driver on 64, is there a 64 bit driver available? What subnet mask are you using with the 169.254.x.x??