> > Sorry I forgot to mention, we don't use DHCP and never > > will. Everything is static.
DHCP is actually useful for more than just address assignment. It's the admin's friend. Don't write it off too quickly, just because you've decided to assign addresses statically. > > Maybe I didn't make myself clear enough. Let me try again. > > When joe brings his computer to work, his computer will > > most likely have a > > different workgroup setup like say, joehome. > > So when I browse the network neighborhood, I see the > > workgroup joehome. > > Then If I go into joehome, I will see joe. > > But, what I'm trying to say is that, if I see the workgroup > > joehome, and try > > to access it, it times out or get some error message. > > How can I see what computer name is in that workgroup. Without the > > computer name I can't do a nbtstat command to get the Ip address. > > I hope this is more helpful. Do you run WINS? (And a WINS proxy to pick up hosts that are set to use broadcast instead....) I'm pretty sure that the workgroup name will get registered there, with an IP address. Failing that, the NT Server Resource Kit included a couple of useful tools for monitoring/troubleshooting "master browser" issues. (This is the network service that populates Network Neighborhood.) I no longer recall the specific tool names, but at least one of them would show you the current master browser(s) for each domain or workgroup. If there's only one machine in a workgroup, it's not going to get much competition in a browser election.... David Gillett
