Sign in with
Sign up | Sign in
Your question
Closed

Windows 7 unidentified network on LAN

Last response: in Networking
Share
June 23, 2012 6:15:16 PM

Hi, this is my first post here.

I have a serious issue with my network.

I have my wireless router that gives internet to all my computers (4), each one having their own usb wifi adaptor. This part works fine, never had any issue with internet.

Each of the computers also have its own GBE adapter but i wasn't really using them. Until now, i bought a switch and connected all 4 computers through rj-45 to the switch just so i could transfer files easier and especially much faster than through the wireless.

This is where my problem is, the network works, i can see and transfer files just fine, the issue being, on each and every computer, the lan is considered as unidentified public network. I've tried everything i could think of, yet, nothing, i can't change the status of the lan connection.

Oh yeah, and, the ips on the lan are all error ips (169.xx.xx.xx).

Anyone can help ?
June 23, 2012 11:44:41 PM

have you tried assigning static IPs to the LAN cards but no gateway IP
June 24, 2012 8:02:39 AM

Yes i did, with or without gateway, didn't make any difference, still unidentified.
Related resources
June 24, 2012 8:10:29 AM



Are you by any chance running McAfee? If so, even turning off the firewall does nothing because it remains on and blocking Internet access when you think it's off. I had to uninstall it from a system yesterday just to get Net access back. Sometimes, if McAfee isn't present, stopping the Bonjour Service running at boottime does the trick.


June 24, 2012 8:16:09 AM

I'm not using McAfee, i'm using Symantec Endpoint Protection, i've tried it enabled and disabled.

Besides, this isn't about internet access, i'm not supposed to get internet access through my LAN, it's only there to connect the 4 computers together, i get my internet from the wireless.

It's only about the unidentified status of the LAN.

June 24, 2012 8:20:28 AM

Here's a shot of my network, the first connection (Wifi) is just fine, it's the second one that isn't.

June 24, 2012 8:29:26 AM

Just incase this could help, here's an ipconfig /all (this is while as suggested above, i specify an ip for the lan card without gateway)

Quote:
Windows IP Configuration

Host Name . . . . . . . . . . . . : JOBE-LAPTOP-01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 130
Physical Address. . . . . . . . . : DC-A9-71-C0-28-A3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f048:b42:f121:b791%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : dimanche 24 juin 2012 10:08:50
Lease Expires . . . . . . . . . . : lundi 25 juin 2012 10:08:50
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 182233457
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-E4-4A-AA-DC-A9-71-C0-28-A3

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 6C-62-6D-36-F6-EB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b8fd:fb8:D 9ba:5268%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.200.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 359424621
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-E4-4A-AA-DC-A9-71-C0-28-A3

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.Home:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Home
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

Tunnel adapter isatap.{E07E7274-3A70-469B-8584-E13B3E4AB877}:

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
June 24, 2012 1:04:07 PM

For the record, the 169.254.x.x IPs are not errors. Those are perfectly valid IPs and will work under the right circumstances. They occur when a client’s DHCP request does not receive a response from a DHCP server (usually running on your router). So the client takes a fallback position and assigns itself a randomly generated IP in the 169.254.x.x. network. The theory being, in the absence of a DHCP server, at least all the computers will have unique IPs and be able to communicate w/ each other. A clever idea, but not always a practical one.

Anyway, so we know that attempts to contact the DHCP server are failing. The reason you have an unidentified network at that point is because the network gets its name from the domain name provided by the (you guessed it) DHCP server!

So from everything I’m seeing, it appears the fundamental problem is the lack of a response from the DHCP server, presumably the same one that works fine w/ your wireless adapters. All I can assume is that you don’t have that same switch connected to the router (further suggested by the fact the unidentified network says no internet access). IOW, it’s just hanging out there as an island, with the four computers connected to it. As I said, if the computers are all configured w/ DHCP and (in this case) the DHCP server is literally inaccessible, it should still work due to the way the 169.254.x.x network works. But again, because there’s no DHCP server to provide a domain name, so there’s no named network. It’s just a bookkeeping issue. It doesn’t affect connectivity in any way.

If it bothers you, I suppose you could manually update the domain name on each computer’s IP configuration. But then you might as well manually configure their respective IP configurations too. Just use a different network from the primary router, so if the primary network is 192.168.1.x, perhaps make it 10.0.0.x.
June 24, 2012 1:15:24 PM

I did assign an ip to the 4 gbe adapters in the range of 10, actually it's 10.205.215.1-2-3-4 (IP and subnet, no gateway or dns) but that didn't change anything, the network is still unidentified.

I don't have a switch connected to the router

A. Computer 1, 2, 3, 4 are connected together through their wired adapter and to a switch.

B. Computer 1, 2, 3, 4 all have their wireless adapters connected to the router and to the internet.

As you can see, the switch isn't connected to the router at all. they're independant.

And the problem i'm having only concerns point A.

Anyway could you give me more details about your last point please ? (the part about assigning a domain name, how do i do that, since assigning the 10.x IP didn't help) ?
June 24, 2012 1:28:07 PM

The network is still unidentified because you didn't also configure the domain name in that same TCP/IP configuration. You mostly likely left it blank. Again, it's not strictly necessary and thus why it's under the advanced settings, specifically General->Advanced->DNS->"DNS suffix for this connection".

June 24, 2012 1:41:03 PM

eibgrad said:
The network is still unidentified because you didn't also configure the domain name in that same TCP/IP configuration. You mostly likely left it blank. Again, it's not strictly necessary and thus why it's under the advanced settings, specifically General->Advanced->DNS->"DNS suffix for this connection".


I understand this is strictly not necessary but i really would like to do it so

I just did assign a name, or well i think i did:



But nothing changed. What did i do wrong ?
June 24, 2012 1:42:47 PM

You may need to refresh the network adapters (e.g., pull and reinsert the cables, or else reboot).
June 24, 2012 1:48:43 PM

Well, i just did, unplug, reboot, replug, still unidentified :( 

Oh yeah, and something quite funny, whatever i do, when i close the network page, the network troubleshooter opens up, but obviously doesn't find anything.
June 24, 2012 2:05:20 PM

Hmm, should have worked, go to Network Connections (Start->Run, type "ncpa.cpl" (no quotes), and hit enter). Select the connection, right-click, and hit disable. Then right-click again and enable. You should see the named network updated right there on that screen.
June 24, 2012 2:07:09 PM

Did that too, more often than not actually, still no joy, i really don't understand :( 
June 24, 2012 2:26:22 PM

Go to a command prompt and issue the ipconfig /all command again, let's see if the DNS suffix (domain name) is now at least filled in, it should be.
June 24, 2012 2:34:09 PM

Quote:
Windows IP Configuration

Host Name . . . . . . . . . . . . : JOBE-LAPTOP-01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home
Test

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 130
Physical Address. . . . . . . . . : DC-A9-71-C0-28-A3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f048:b42:f121:b791%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : dimanche 24 juin 2012 15:45:45
Lease Expires . . . . . . . . . . : lundi 25 juin 2012 15:45:44
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 182233457
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-E4-4A-AA-DC-A9-71-C0-28-A3

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Test
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 6C-62-6D-36-F6-EB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b8fd:fb8:D 9ba:5268%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.205.215.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 359424621
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-E4-4A-AA-DC-A9-71-C0-28-A3

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:

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:5ef5:79fd:84f:11e6:3f57:fefd(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::84f:11e6:3f57:fefd%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.Home:

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

Tunnel adapter isatap.Test:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Test
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
June 24, 2012 2:50:52 PM

Well, I can see it there, "Connection-specific DNS Suffix . : Test"

Notice that the same line on the wireless connection shows Home, which does appear on Network Sharing Center screen. Might just be a quirk in how the Network Sharing Center works. Perhaps once the network is named on that particular screen, it remains fixed, no matter if it changes underneath as the protocol level. You may have to manually rename it on that same screen, or perhaps delete the connection and have it created again. If you click on the "little house" on that screen, you'll find you can manually rename it, or even delete it (the deletion will only work if not in use, so you'd either have to delete from the wireless connection, or disable it first).

Can you believe all this hassle for a name change?
June 24, 2012 2:56:41 PM

What, what screen are you talking about, i'm confused now, the only screen with a "house" i can think of is this one:



what should i rename and where now then ?
June 24, 2012 3:12:58 PM

LOL, ok, well in this case, it's the one w/ the park bench (icons vary according to whether they're public or private). Click on that bench, you can rename it there.
June 24, 2012 3:17:12 PM

eibgrad said:
LOL, ok, well in this case, it's the one w/ the park bench (icons vary according to whether they're public or private). Click on that bench, you can rename it there.


Well, i wish it was that easy, no you can't rename by clicking it, no matter what you type, it won't print.

I've even modified the security policies to be able to change it from public to private, but i still wasn't able to rename it.

This is actually the root of the problem, i'm unable to change it from unidentified to home network.
June 24, 2012 3:21:32 PM

Well then it sounds like a privileges problem. Are you logged in as an Admin? I am, and I can change the name, no problem.
June 24, 2012 3:27:13 PM

eibgrad said:
Well then it sounds like a privileges problem. Are you logged in as an Admin? I am, and I can change the name, no problem.


I believe this is where it's becoming funny... yes i am

June 24, 2012 4:00:44 PM

Then I don't what else to tell ya, it should work, it doesn't, beats me. Sorry.
June 24, 2012 4:02:50 PM

eibgrad said:
Then I don't what else to tell ya, it should work, it doesn't, beats me. Sorry.



That's just my everyday's luck :( 
June 24, 2012 5:30:57 PM

can you change the LAN from Public to Home network
June 24, 2012 6:06:22 PM



Maybe uninstalling the connection - or even the adapter - and restarting will force it to offer the chance to choose a Home network. Make sure there is no tick in "Treat all future networks as public" before clicking Close.

June 24, 2012 11:49:11 PM

Emerald said:
can you change the LAN from Public to Home network


No, i can't.
June 24, 2012 11:49:37 PM

Saga Lout said:


Maybe uninstalling the connection - or even the adapter - and restarting will force it to offer the chance to choose a Home network. Make sure there is no tick in "Treat all future networks as public" before clicking Close.




Done that too, no luck.

As i understand it, the problem is that, on the LAN, there's no DHCP server to attribute the IPs to the 4 computers, and giving them manually doesn't solve the identification problem because there's no gateway. The only easy solution i've found was to enable ICS which i don't want to.
Another option i tried was to add one of my old router to the equation, serving as DCHP server, in this case, everything works just fine.

I've heard about managed switches, i know they can serve as DHCP relays but i'm not sure if they can work as DCHP servers, does anyone know ?
June 25, 2012 12:00:44 AM

Sure, a managed switch might very well have its own DHCP server, but why all this trouble for a named network? It's just a name, it serves no other useful purpose.

You could also install a DHCP server on one of the computers, as a service. I'm sure there are freebies out there. Or just grab an old router, something cheap, even something from the local thrift shop, and use it. I wouldn't spend big bucks on a managed switch just to get a DHCP server.
June 25, 2012 10:28:18 AM

Ok then good to know (about the managed switch) just have to eventually find one, because they never say if it can work as a server in the description.

Using a dhcp third party app wouldn't do the trick for me because it would mean that i have to keep one computer turned on at all time.

I am currently using an old router, but since it's a 10/100 it slows everything down (transfers between computers)

Right now, i'm even trying something else (all wired)

Internet -> Router > gigagit (unmanaged) Switch -> spread the connection through all the computers and i am hoping that, that way i can have both the conection on every computer and full speed between them. But i have to dig holes first haha :p 

Why all the hassle, well, i don't know really, either it's perfect or it's not, at all, matter of perspective i guess :) 
March 28, 2013 8:04:35 AM

This may not help in your quest for a solution but I've had exactly the same issue on a customer's Acer laptop and whilst it doesn't affect the wireless internet access it's very annoying. I've even done a complete reinstall of Windows 7 and the issue is still there. Most odd!
!