Private network becomes public on reboot (or on rebooting other PC onLAN)

[Wessel Troost]

This computer has two network interfaces. One is connected to a DSL
router, the other is connected to a local computer.

Vista remarks the local interface as "Public" every time the computer
reboots, or when any other computer on the LAN reboots. This prevents
users on the other machines from using file shares on this machine.

Disabling the firewall on the private adapter resolves the problems,
but leaves the computer without a firewall on the LAN interface.

All computers on the LAN are in the same workgroup. All IP adresses
are assigned by this computer (it´s sharing its internet connection.)

If someone has pointers on one of the following, I´d appreciate it.
- Does Vista log the reason for the change in location somewhere?
- Where can I find more information about Vista Location Awareness?

 

[Robert L. \(MS-MVP\)]

A multihomed computer may have this behavior. Posting back with the result
may help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


This computer has two network interfaces. One is connected to a DSL
router, the other is connected to a local computer.

Vista remarks the local interface as "Public" every time the computer
reboots, or when any other computer on the LAN reboots. This prevents
users on the other machines from using file shares on this machine.

Disabling the firewall on the private adapter resolves the problems,
but leaves the computer without a firewall on the LAN interface.

All computers on the LAN are in the same workgroup. All IP adresses
are assigned by this computer (it´s sharing its internet connection.)

If someone has pointers on one of the following, I´d appreciate it.
- Does Vista log the reason for the change in location somewhere?
- Where can I find more information about Vista Location Awareness?

 

[Wessel Troost]

Thanks for your reply.

A multihomed computer may have this behavior.

What's a multi-homed computer?
The computer in question is a fixed desktop with two wired
connections.

Posting back with the result may help.

Which result?

 

[Robert L. \(MS-MVP\)]

A computer with two NICs is multihomed computer. Post the result of ipconfig
/all.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

[John Adams]

I have a very similar problem.

I have a Vista desktop and an old XP laptop. The Vista desktop has a USB
adapter for Sprint Mobile Broadband internet and it also has a built-in
ethernet LAN port. I connect to the internet on the Vista desktop through
the Sprint USB connection and then share that internet connection through
the LAN port to the laptop.

After every reboot and frequently even between reboots, the network on the
LAN port will switch back to "Public" which renders Internet Connection
Sharing useless until I manually change it back to "Private". It lists this
network in the Network and Sharing Wizard as an "Unidentified Network".

What can I do? This is horrible.

- John

 

[Wessel Troost]

I have a very similar problem.I guess the question is, can you tell Vista to give up a little
security in exchange for creating a working small company network.

So far, the answer has been "install XP".

 

[Wessel Troost]

Found a solution that "works", although it's less secure

Turn off your firewall entirely for the LAN network adapter:
1. Open network and sharing center
2. Click "Windows Firewall" (bottom left, in de side bar)
3. Click "Turn Windows Firewall on or off" (top left, side bar)
4. Go to the "Advanced" tab
5. Deselect your LAN adapter

After this, Vista will still mark your adapter as public, but it
won't
have any effect.

 

[Wessel Troost]

A computer with two NICs is multihomed computer. Post the result of ipconfig

/all.

Took a while, but I got back at to the networked involved today.
Here's the result of ipconfig /all:

Windows IP-configuratie

Hostnaam . . . . . . . . . . . . : JOS
Primair DNS-achtervoegsel . . . . :
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : lan

Ethernet-adapter Mobo-Internet:

Verbindingsspec. DNS-achtervoegsel: lan
Beschrijving. . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E
Gigabit Ethernet Controller
Fysiek adres. . . . . . . . . . . : 00-1D-60-55-1F-21
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::c22:1d20:c7f5:c78f
%8(voorkeur)
IPv4-adres. . . . . . . . . . . . : 192.168.1.64(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Lease verkregen . . . . . . . . . : vrijdag 18 januari 2008
22:08:41
Lease verlopen. . . . . . . . . . : zaterdag 19 januari 2008
22:08:40
Standaardgateway. . . . . . . . . : 192.168.1.254
DHCP-server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 234888544
DNS-servers . . . . . . . . . . . : 192.168.1.254
NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Ethernet-adapter PCI-Huisnet:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Fysiek adres. . . . . . . . . . . : 00-80-5A-60-A0-90
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
IPv4-adres. . . . . . . . . . . . : 192.168.0.1(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . :
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter LAN-verbinding* 9:

Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-
Interface
Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja

Tunnel-adapter LAN-verbinding* 7:

Verbindingsspec. DNS-achtervoegsel: lan
Beschrijving. . . . . . . . . . . : isatap.lan
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::5efe:
192.168.1.64%15(voorkeur)
Standaardgateway. . . . . . . . . :
DNS-servers . . . . . . . . . . . : 192.168.1.254
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter LAN-verbinding* 6:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : isatap.{A9071F9B-9CA9-4E71-A5DF-
A2DD6F9BBC33}
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::5efe:
192.168.0.1%13(voorkeur)
Standaardgateway. . . . . . . . . :
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter LAN-verbinding* 10:

Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : 6TO4 Adapter
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja