I was excited 5 years ago with the promises of XP networking improvements: "it'll just work." 5 years later with Vista on the horizon, and I've had trouble all the while. Perhaps some kind souls out there could lend their expertise?
The background:
The small, 5-10 computer network is made up of computers that run XP Home or Pro and access the internet through a Belkin router, either wirelessly or wired. DHCP is used, and pinging other computers from the command prompt works. However, I still get two problems sporadically on different computers:
The problems:
1) Computers are told that the workgroup is inaccessible.
2) Computers are told that a specific computer is inaccessible.
Other information:
All of the computers are running the latest version of McAfee Firewall. All are set to "allow pings" and designate 192.168.2.0-99 as safe IP addresses. I typically have Windows firewall disabled - is this advisable?
Another variable is the network setup wizard. In the past, I always said that the computers were connected to the Internet "through a residential gateway." Lately I've been choosing "other" and then "directly or through a hub," as it seems as though there's fewer problems. What's the difference, and could that be causing any problems?
The differences between Home and Pro systems seems minimal, yet the problems seem to arise more frequently on the Pro systems.
Thank you SO much for any help you may be able to provide!
XP Networking woes
Your problems are stemming from a fight between the computers to be the master domain browser. Basically, everytime a computer connects to your network, it forces an election for browse master between all of the computers. Once someone wins, all of the other computers have to register to that computer. With XP, this can take as long as 54 minutes--or until the next computer is rebooted, which starts the entire procedure again. Typically, the winner will be an XP Pro computer.
Note that this never happens when a singer server (or domain controller) is on the network, even if the network is not an NT domain.
On all computers except the two that are most connected to the network and least rebooted (and are XP Pro systems), do this:
Go to Control Panel, Administrative Tools, Services. Find either a Computer Manager or Computer Browser and double-click it. Change the startup type to Disabled. If the service is Started, Stop it. (Note that if the service is actually Started, you are on the master browser, and doing the preceeding will force another election.
To have the browser situation fixed right away:
1. Shut down all of the systems.
2. Power up the system you want to be the master browser.
3. Once it comes up completely, power up the other system that can browse. This will force an election between the two systems, which the first system will win.
4. Once you can see the two computers My Network Places on either machine, power up all the other systems. They will all register with the master browser. Note that if you shut down both of the browsers, you are going to have problems with your network.
One other note: If you are going to share files between systems, and users are required to log into their machine, you must have accounts on all of the machines you will be sharing files with. I.e., if Bob is going to pull files off of computer A, he will need to have an account/password on computer A that is identical to the system he has logged into. That means, if you have 10 users on 10 computers, all 10 computers will need to have 10 accounts that are identical with each other. (Now you know why most businesses use client/server networks).
HTH
Courtney
Note that this never happens when a singer server (or domain controller) is on the network, even if the network is not an NT domain.
On all computers except the two that are most connected to the network and least rebooted (and are XP Pro systems), do this:
Go to Control Panel, Administrative Tools, Services. Find either a Computer Manager or Computer Browser and double-click it. Change the startup type to Disabled. If the service is Started, Stop it. (Note that if the service is actually Started, you are on the master browser, and doing the preceeding will force another election.
To have the browser situation fixed right away:
1. Shut down all of the systems.
2. Power up the system you want to be the master browser.
3. Once it comes up completely, power up the other system that can browse. This will force an election between the two systems, which the first system will win.
4. Once you can see the two computers My Network Places on either machine, power up all the other systems. They will all register with the master browser. Note that if you shut down both of the browsers, you are going to have problems with your network.
One other note: If you are going to share files between systems, and users are required to log into their machine, you must have accounts on all of the machines you will be sharing files with. I.e., if Bob is going to pull files off of computer A, he will need to have an account/password on computer A that is identical to the system he has logged into. That means, if you have 10 users on 10 computers, all 10 computers will need to have 10 accounts that are identical with each other. (Now you know why most businesses use client/server networks).
HTH
Courtney
-
YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
I deal more with clients who have servers on their network..so a domain controller to "rule the roost". However...I have my share of basic peer to peer clients to take care of....
Some things that I've noticed..when mixing XPp and XPh...increase of fighting between the systems. I try to stick with XPp.
Network Browsing can take a while without a comain controller..as mentioned above..peer to peer networks will elect a "Master browser"...this has nothing to do with browsing the internet..but instead..browsing the local network. Some computer will maintain a list of available names on a network. Several factors are considered when a network forces an election. However...due to many circumstances...it doesn't always work smoothly. Circumstances such as various OS levels, various service pack levels, various "health" of the computers, different network cards/drivers, etc etc. I've never had to resort to the following trick...but you can pick one PC and manually force it to be the master browser..and manually turn it off on the others.
Network browsing also relies on netbios. By default, Windows "should" select it..as it's on an "auto" state. But..due to variables such as the differences I listed above..it doesn't always work. However you can go into advances TCP properties..WINS tab..and force it on..do this on each PC.
Normally a domain controller handles all these..the browser election (itself..no question asked)..and it runs a local DNS service for the network (or WINS for those that still have old Win9X clients). On peer to peers..there is no local DNS service.
Workgroup...technically you dont need PCs to be in the same workgroup for them to see each other..a lot of people think you NEED this to be the same in order to browse other computers....not true. But it helps them to "appear" in the top layer of network browsing..instead of having to drill into another workgroup. Takes a few hours longer..but if you build a network with different workgroups..they'll still all appear just fine in network places..you'll just see the different workgroups first..to get to PCs there..just drill into the workgroup. But for your home LAN..yeah..keep it the same, keep it simple.
For simplicity...if you can, keep your Administrator password the same on all PCs..just make sure it's not left <blank>
Not fond of McAfee products..but software firewalls can throw a wrench into networking. Just make sure you double check your safe zone settings.
Some things that I've noticed..when mixing XPp and XPh...increase of fighting between the systems. I try to stick with XPp.
Network Browsing can take a while without a comain controller..as mentioned above..peer to peer networks will elect a "Master browser"...this has nothing to do with browsing the internet..but instead..browsing the local network. Some computer will maintain a list of available names on a network. Several factors are considered when a network forces an election. However...due to many circumstances...it doesn't always work smoothly. Circumstances such as various OS levels, various service pack levels, various "health" of the computers, different network cards/drivers, etc etc. I've never had to resort to the following trick...but you can pick one PC and manually force it to be the master browser..and manually turn it off on the others.
Network browsing also relies on netbios. By default, Windows "should" select it..as it's on an "auto" state. But..due to variables such as the differences I listed above..it doesn't always work. However you can go into advances TCP properties..WINS tab..and force it on..do this on each PC.
Normally a domain controller handles all these..the browser election (itself..no question asked)..and it runs a local DNS service for the network (or WINS for those that still have old Win9X clients). On peer to peers..there is no local DNS service.
Workgroup...technically you dont need PCs to be in the same workgroup for them to see each other..a lot of people think you NEED this to be the same in order to browse other computers....not true. But it helps them to "appear" in the top layer of network browsing..instead of having to drill into another workgroup. Takes a few hours longer..but if you build a network with different workgroups..they'll still all appear just fine in network places..you'll just see the different workgroups first..to get to PCs there..just drill into the workgroup. But for your home LAN..yeah..keep it the same, keep it simple.
For simplicity...if you can, keep your Administrator password the same on all PCs..just make sure it's not left <blank>
Not fond of McAfee products..but software firewalls can throw a wrench into networking. Just make sure you double check your safe zone settings.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
-
drokkon
