Unidentified Network Issue

[arren]

I recently reformatted my Win XP 32bit to Win 7 64 bit.

The first thing that I did was check internet connectivity (wired to a linksys tmobile hotspot router) and it kept telling me that the network was unidentified. I'm currently using my onboard ethernet port, and I have the most up to date drivers installed. I've tried a different NIC card but that gave the same results.

I've tried giving my computer a static ip, but that hasn't worked. Sometimes the router will give my computer a wrong ip address (169.254.x.x) instead of a 192.168.x.x one. Either way, it still doesn't work.

I've looked around the forums and did not have the bonjour service running, I've tried connecting directly to the modem but it still gives me the same issue.

If anyone has any suggestions it would be greatly appreciated.

Thank you

 

[Bootz]

Did you try disabling and then re-enabling the network adapter? Or check to make sure the settings are correct in the router and that the router is windows 7 compatable.

It sounds like something with dns.

 

[arren]

I've tried disabling and enabling the network adapter, and I've also manually set the DNS servers. Both did not solve anything. I'm not sure if it is the router or not, but I couldn't get internet even when connecting directly to the modem (bypassing the router completely).

 

[Darryl Licht]

I recently reformatted my Win XP 32bit to Win 7 64 bit.

The first thing that I did was check internet connectivity (wired to a linksys tmobile hotspot router) and it kept telling me that the network was unidentified. I'm currently using my onboard ethernet port, and I have the most up to date drivers installed. I've tried a different NIC card but that gave the same results.

I've tried giving my computer a static ip, but that hasn't worked. Sometimes the router will give my computer a wrong ip address (169.254.x.x) instead of a 192.168.x.x one. Either way, it still doesn't work.

I've looked around the forums and did not have the bonjour service running, I've tried connecting directly to the modem but it still gives me the same issue.

If anyone has any suggestions it would be greatly appreciated.

Thank you

1st off... Welcome to SevenForums! Also, NIC is an acronym for Network Interface Card, so no need to say NIC card! That's redundant LOL!

Since you said that sometimes you get an IP of 169.254.x.x and other times you get a 192.168.x.x... sounds like the issue is your router. A 169.254.x.x address is Windows autoconfig address (meaning it didnt get an IP from your routers DHCP server) and it will never get an Internet connection with that IP... . Have you tried resetting the router?

To get more specific on help...

What is the model of your router?

Also, where did you get your version of Win7?

 

[PooMan UK]

Yep ... gotta agree with Darryl "Router" and "Nic" make/model might help.

You could also go have a looky here to check that your router is compatible

windows-7 / router compatibility

Ps. check that you have the latest "Firmware" for your router

 

[arren]

I got my version of Windows 7 through a student discount deal.

 

[Darryl Licht]

I got my version of Windows 7 through a student discount deal.

Had to make sure its not a hacked/cracked/pirated torrent etc...

How about your router model #???

 

[aem]

Have you tried release and new, flushing the dns?

C:\ipconfig /release
C:\ipconfig /renew
C:\ipconfig /flushddn

After you do this, cna you provide details of your ipconfig /all

 

[arren]

The model number is WRTU54G-TM.

 

[Darryl Licht]

I'm still going to point my fault finger in the direction of your Linksys WRTU54G-TM router... as you sometimes get an IP and sometimes dont.

Do you have the latest firmware installed on that router? Latest version is 1.00.21 dated 6/29/09
You can DL here: Linksys by Cisco - WRTU54G-TM Support

Another thing to try... have a friend try with his or her lappy and see what results they get.

ANd I am assuming that you have the latest drivers for your NIC???

 

[arren]

If I do a ipconfig/release it says:
An error occured while releasing interface Loopback Psuedo-Interface 1 : The system cannot find the file specified.

The operation failed as no adapter is in the state permissible for this operation.

 

[arren]

I have a 2 other laptops and one other desktop connected to this router, the laptop I'm currently on is a windows xp 32 bit and is connected wirelessly. The other laptop is a windows 7 32bit and also wireless. The desktop is windows 7 (I believe it's 32 bit) and connected through an ethernet cable.

I have updated both the firmware for the router, and the driver for the network card.

 

[arren]

The other desktop is windows 7 64 bit.

 

[aem]

Can u give details if ipconfig /all of machine that work and of the one that doesn't. I'm thinking it might be a MAC issue.

 

[arren]

This is the log from the working computer:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Majaiku
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. . . . . . . . . : 6C-F0-49-07-EA-D8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f4f2:f59e:ae60:75b9%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, February 19, 2010 4:02:30 PM
Lease Expires . . . . . . . . . . : Friday, February 26, 2010 4:02:30 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 242020425
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-B3-82-84-6C-F0-49-07-EA-D8

DNS Servers . . . . . . . . . . . : 209.18.47.61
209.18.47.62
0.0.0.0
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{0E9FDCFD-1AFA-431F-A966-23800D3AF0CD}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

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
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1027:2808:b77d:fb2a(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::1027:2808:b77d:fb2a%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Here is the log from the non working one:


Windows IP Configuration

Host Name . . . . . . . . . . . . : Beef
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
it Ethernet Controller
Physical Address. . . . . . . . . : 00-18-F3-5A-60-8E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ec09:6ac6:c6c7:d721%13(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.215.33(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 268441843
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-10-0C-B1-00-18-F3-5A-60-8E

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 isatap.{C6573033-A204-434D-BE9A-170F643CAFB5}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

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

 

[Darryl Licht]

If I do a ipconfig/release it says:
An error occured while releasing interface Loopback Psuedo-Interface 1 : The system cannot find the file specified.

The operation failed as no adapter is in the state permissible for this operation.

This indicates that you may not have the proper wireless nic drivers installed... can you attach a screenshot of your device manager?

Now you just posted the info above this post and I see no wireless nic listed...

 

[arren]

Attached is a picture of my device manager.

The drivers should be correct, I went to the manufacturer website and downloaded the latest version for windows 7 64 bit as well as trying the one that windows automatically gave me.

I'm not trying to connect wirelessly.

 

[Darryl Licht]

Attached is a picture of my device manager.

The drivers should be correct, I went to the manufacturer website and downloaded the latest version for windows 7 64 bit as well as trying the one that windows automatically gave me.

I'm not trying to connect wirelessly.

That's your issues! Notice the 3 items that are not properly identified under Other Devices? One of them is your wireless NIC...

What is the make and model # of your PC? I will try and find the drivers for you!

 

[arren]

I'm not trying to connect wirelessly. I want to connect via ethernet, there is no wireless NIC on this computer. I tested the motherboard network adapter and a PCI one, both did not work.

 

[Darryl Licht]

OK sorry, but you still have a network controller that isnt properly identified and is probably related to your issue.

Your drivers should all be here: http://www.nvidia.com/Download/index5.aspx?lang=en-us

Once all of the unidentified devices are ID'd you should be up and working!