How does Windows Networking work?

[prowsej]

I'm using Windows XP. I'm in residence at a University so everyone on our floor with a computer shows up on the network. We can share files, printers, etc. My computer workgroup is set to "workgroup." Other people have their set to "mshome." (they are the defaults for WinXP Pro and Home, respectively) I'm able to see the files of people on "mshome" workgroup and they're able to see the files of people on my workgroup.

I'm wondering how this network works. I read an overview from the WinXP Resource Kit http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prcf_omn_gtbt.asp

What computers can I access?
[*]I can access all computers in the "View Workgroup Computers" list, but also more systems that aren't on that list if I type in \\ComputerName
[*]Will I be able to access all computers on my subnet regardless of their workgroup name? Is it depend on network architecture?

Thanks

 

[Nothinman]

How does Windows Networking work?

Poorly. *rimshot*

 

[Toxic]

Poorly. *rimshot*

That was my first thought as well, LOL.

 

[johnlog]

Prow,

You got two negative answers. The real answer is that Windows can network quite well. Just follow the network Wizard's instructions and it should work well for you.

 

[Nothinman]

For a "better" answer you can probably find the best documentation in the Samba suite and it's coverage of Windows browsing.

I can access all computers in the "View Workgroup Computers" list, but also more systems that aren't on that list if I type in \\ComputerName

This is because Windows network browsing sucks. 1 computer maintains a list of available computers and if that list isn't up to date you don't get a complete list. And when PCs are being turned on and off randomly the list gets out of date, and jumps from computer to computer, quickly.

Will I be able to access all computers on my subnet regardless of their workgroup name? Is it depend on network architecture?

Workgroup name is basicaly meaningless, if you know the name of the PC and have an account (or it's guest account is enabled) you can get in regardless of workgroup name.

 

[prowsej]

Workgroup name is basicaly meaningless, if you know the name of the PC and have an account (or it's guest account is enabled) you can get in regardless of workgroup name.

Thanks for the response. This is the sort of answer I was looking for. I'll look up the Samba site.

 

[prowsej]

I've looked at the Samba site and read a good article than answered the questions that I wanted to know (ironically, it was published in Linux Magazine - great soruce for Windows users).

Is there anything that I can do to minimize the appearance of this error message: http://chat.carleton.ca/~jmprowse//pics/network error.PNG

 

[Nothinman]

Since I almost always use Samba I have it set it up to be a WINS server, it handles the browsing instead of letting them fight and pass the browse list around. I also have the same box doing DHCP and in it's DHCP settings it tells all the clients the IP of the WINS server so they register on bootup, it works quite well and fixes 99% of browsing issues IME.

I don't have a simple solution for a Windows only network, ironically enough.

 

[Saltin]

This is because Windows network browsing sucks. 1 computer maintains a list of available computers and if that list isn't up to date you don't get a complete list. And when PCs are being turned on and off randomly the list gets out of date, and jumps from computer to computer, quickly.

While I'm not going to argue that the Network Browsing system in Windows is fairly archaic, if you understand how it actually works (which is nothing like your simplified discription), you can tweak it to become very reliable. To be perfectly honest with you, I don't know many people who are knowledgeable in regard to NT that use the Browser List to find thier shares anyhow.

I've built Win2k networks that don't use NetBIOS at all, infact. Active Directory can take care of pretty much everything.

The poster asked a question, and though it was extremely vauge, I don't think responses like "it sucks" or "not very well" are warranted. Obvoiusly, in competent hands, it works quite well, otherwise how would I be posting this?

It's become obvious to me over the years here that you don't like Windows. Why don't you get over it? You don't need to jump on every occassion that presents itself. Take it to slashdot...........

I know you post on Arstechnica once in a while too, and I notice you never say things like this in the NT forum, it's because they won't tolerate it. I don't know why they do here........

 

[Nothinman]

I've built Win2k networks that don't use NetBIOS at all, infact. Active Directory can take care of pretty much everything.

I know it's possible, but he's definately not setting up AD here. And he can't even control the other PCs to disable/enable holding of the browse list on them to try and control it like that. He was curious how computer browsing worked and without WINS or AD it basically comes down to broadcasts and browser master elections. Right? It's been a while since I read up on how browsing works, but I'm pretty sure I'm remembering correctly.

The poster asked a question, and though it was extremely vauge, I don't think responses like "it sucks" or "not very well" are warranted. Obvoiusly, in competent hands, it works quite well, otherwise how would I be posting this?

Umm, it was a joke, lighten up. You do know what a rimshot is, right ?IIRC you're not in the US, so I guess it's a valid question.

And you're posting from a web browser, which has nothing to do with "My Network Places" computer browsing.