Main > Everything Else
Network Issues
SavannahLion:
I did a search on that reg entry. Apparently here's how it's supposed to work.
Setting Maintainserverlist to TRUE forces the PC to act as a master browser if no other PC is acting as such.
Setting the same to TRUE if another PC is acting as a master server list puts that PC into a backup "mode" when it sees a master on the network.
Setting Maintainserverlist to AUTO causes the PC to take over the role of a master if no other master exists or acts as a backup if not enough backups exist on the network.
Setting it to FALSE forces the PC to never hold a master or backup role even if no master browser exists on the network.
In other words, putting all the PC's on a network to TRUE causes one PC to become the master and the rest to become backups. Expected behavior for that setting. That's why it works for you when you set them all to TRUE.
So it appears there's a deficiency in how Maintainserverlist set to AUTO works. I'm going to have to try this when I get home tonight.
In any case, a quick peek through the MSDN and Technet pages, Microsoft is rather vague on how it all works. MSDN has better information on a technical basis, but hardly any nutshell information. Oddly enough, I did note that the browser list is supposed to be one master and one backup for a network with 32 or fewer PC's and an additional backup for every 32 beyond that. Seems to me that the AUTO setting can't decide which PC should act as a master and backup.
Here's a thought. Anyone with problems using non-Windows PCs in their network? Linux, Wii, PS3 perhaps? Anyone that don't have problems, are they using a pure Windows network? Just a thought, I recall my Barricade refused to list any Linux PC unless I used some hacked firmware.
Corrected annoying spelling error
saint:
Frizzle: From a command prompt, what do you get when you do a
"net view" (no quotes)
Do you see the cocktail cabinet showing up?
What do you see if you do a
"net view w.x.y.z" where "w.x.y.z" is the IP address of the cocktail cabinet?
FrizzleFried:
--- Quote from: saint on November 17, 2008, 03:23:24 pm ---Frizzle: From a command prompt, what do you get when you do a
"net view" (no quotes)
Do you see the cocktail cabinet showing up?
What do you see if you do a
"net view w.x.y.z" where "w.x.y.z" is the IP address of the cocktail cabinet?
--- End quote ---
NET VIEW shows:
\\COCKTAIL Cocktail
\\OFFICEPC Office PC
NET VIEW 192.168.1.105 (cocktail address) shows:
Share name Type Used As Comment
C Disk
COCKTAIL_BACKUP Disck
F Disk
HPLaserJet Print
L BACKUP Disk
So it's seeing it!
EDIT: While NET VIEW shows both \\COCKTAIL and \\OFFICEPC, NET VIEW 192.168.1.105 does not show anything but "System error 53 has occured. The network path was not found"... the results above were from 192.168.1.103 (the office PC)...
EDIT 2: While I posted earlier that it pinged, I was being an idiot and pinging my office PC (103) not the cocktail (105) which is still not pinging.
FrizzleFried:
Welp, I can get in via IP address (\\192.168.1.103)... not sure WHY or HOW it was fixed...
\\computername isn't working though.
EDIT: I am a dumbass...I was getting in to my OFFICE PC at .103... the cocktail cab (.105) still is not pinging nor is it accessable via \\192.168.1.105...
Essentially I am at the same spot I was...but you can see the damn thing with NET VIEW.
patrickl:
Maybe its a problem with the NetBios registration?
Verify WINS registration of client NetBIOS names
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version