• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I can't connect to workgroup computers but I can through Run typing in \\ComputerName

network neigborhood is a craptastic beta of a product (actually almost all network browsers are), ignore it
 
you're stuck in MS network neighboorhood hell.

You'll need a sniffer to really see what is going on.

Biggest thing is making sure all computers have exactly the same protocols (hopefully only 1), that netbios is enabled on TCP, and that under bindings file and print sharing are bound to NBT (netbios over TCP)
 
For some reason the network just came back. My only guess now is that someone from our main head quarters is messing with the network. Is this even possible though? Cuz now I can see computers that are connected but they're not physically here, I guess it's like a VLAN.
 
depending on how the network is setup it can take hours for network neighboor hood to stabalize. If you are using a WINS server it should work pretty well. If there are routers involved there can be other issues.

But the moral of the story is don't use network neighborhood.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top