For you network gurus:

I work in a small office - 15 computers in a small Windows 2000 Pro network, NO domain, just a WORKGROUP. No server per se. All peer-to-peer. One Windows 2000 server just to host our FileMaker files and run a WINS server.

It's always worked just fine. No problems. But suddenly, I can't use "My Network Places" to "View Workgroup Computers" anymore - from any computer... it just hangs for a few minutes, then says "Workgroup may not me accessible."

I CAN however create a shortcut to anyone, such as \\server\public and such... that works fine once created. I can ping anyone. Everyone still has T1 internet access, etc. I just can't browse the local network.

I DO have a WINS server service running... I won't pretend to understand how it works, except that I only set it up so I could browse the network when VPN'ing from home. I set that up months ago though... everything worked fine before and after that.

IPCONFIG shows that everyone has a valid IP address from the DHCP server, DNS and WINS addresses were retreived correctly, etc.

I've read some stuff about the "Computer Browser" service, and how it elects a "Master Browser" and all... is it possible to FORCE another election? Or to somehow reset the list that's being passed around?

One clue: I noticed this problem yesterday while setting up a brand-new computer. At the time, everyone else worked fine, but the new computer would not browse. Now, no one can browse... as if everyone else now tried to get the latest list and failed, it's corrupted, etc..

Keep in mind I only know enough about this stuff to get myself in trouble ;)

Check to make sure that you have NetBios over TCP/IP enabled on all of your machines. Also, makes sure that the Computer Browser service is running on all of your Win2k and WinXP systems.

Also, when in doubt, reboot the network, restarting the server first.

Good luck.

I'm guessing that by adding that new machine, it took over as the domain master. There's a couple registry entries you can check for:

hkeylocalmachine/system/currentcontrolset/services/browser/parameters -> maintainserverlist = TRUE

hkeylocalmachine/system/currentcontrolset/services/browser/parameters -> IsDomainMaster = TRUE

I would change these on the Win2k server first and then go from there...

You may want to try using IPX/SPX for file/print sharing rather than TCP/IP.

1. Open Network Connections.
2. In Local Area Network, Right-click on your connection and select Properties, then Install.
3. In Select Network Component Type, click Protocol, and then Add.
4. Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, click OK, and then Close.
5. In Network Connections, on the Advanced menu, click Advanced Settings.
6. On the Adapters and Bindings tab, under Connections, click the local area connection on which you are enabling IPX/SPX file and print sharing.
Under Bindings for Local Area Connection, under File and Printer Sharing for Microsoft Networks, clear the Internet Protocol (TCP/IP) check box, and then click OK.

If all else, fails, you can add the NetBUI protocol to all machines, but there's some inherent security issues in doing this.

I actually had a similar problem a couple years back and had to research this, so these are just some of the things I tried...

Good luck!

khtm - You're asking him to do a lot more than someone of his (self proclaimed) level should be doing. If he added a new machine, then that is where he should start. Changing network protocols is like blowing out a birthday cake with a firehose. Sure you may put out the fire, but then you have another mess to clean up.

edit - Cleaned up spelling and grammatical errors. Was I asleep when I wrote this??? :confused: :o

khtm - You're asking him to do a lot more than someone of his (self proclaimed) level should be doing. If he added new machine, then that is where he should start. Changing network protocols is like blowwing out aborthday cake with a firehose. Sure you may put out the fire, but then you have another mess to clean up.

LOL, so true...

I just got it working now...

I peeked through everyone's Event Log, and saw entries saying something like COULD NOT RETREIVE BROWSE LIST FROM MASTER BROWSER \\JOHN.

So I rebooted him, and all is well.

But that really sucks, as I thought the Browser service was suppoed to be redundant, back itself up, use backup browsers if one failed, etc.? I mean, people here use laptops (including John), so there's not always turned on or in the office.

Thanks for the detailed suggestion(s), by the way. I'll admit I'd be terrified to go that deep, but it's nice to know that level of help is there if I need it. I appreciate the time it took to explain all that. I've saved it in my notes in case I need it again.

I'm assuming the PC you added was running WinXP. That's a common problem in a peer-to-peer network where the new XP machine will try to force itself as the master browser on the other machines. You don't have the same problem with a client-server domain (usually).

Glad to hear everything is working now. :)

Hey sorry for going overboard - glad you got it working!

I guess this goes to show that often the simplest solution (MadRonin: reboot all the machines) is what works :)

Hey sorry for going overboard - glad you got it working!

I guess this goes to show that often the simplest solution (MadRonin: reboot all the machines) is what works :)
It's usually my first response to my customers when they call with a problem. It drives them nuts but 99% of the time it solves their immediate problem. That gives me time to diagnose what the unlying reason is (usually operator error).

I'm assuming the PC you added was running WinXP. That's a common problem in a peer-to-peer network where the new XP machine will try to force itself as the master browser on the other machines. You don't have the same problem with a client-server domain (usually).

Glad to hear everything is working now. :)

Yup, WinXP Pro... and only SP1, if that matters, as our older Televantage system (phones - very cool) won't run under SP2.

I guess this goes to show that often the simplest solution (MadRonin: reboot all the machines) is what works :)

LOL, yea, it's a running joke in the office whenever they call me with a problem: "yea, yea, I know, you're gonna tell me to reboot my system, aren't ya? But I have [insert list of 6-12 applications] open!!!! I HATE you."