Re: WINS issue
From: Todd J Heron (todd_heron_no_spam_at_hotmail.com)
Date: 02/20/05
- Next message: Michael Giorgio - MVP: "Re: WINS issue"
- Previous message: Herb Martin: "Re: Slow browse on Windows NT world domain - latency 300 ms"
- In reply to: Ian: "Re: WINS issue"
- Next in thread: Michael Giorgio - MVP: "Re: WINS issue"
- Reply: Michael Giorgio - MVP: "Re: WINS issue"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 20 Feb 2005 03:16:13 -0500
As Bill said, browsing across subnets (My Network Places) requires a WINS
server and a domain master browser (domainname 1B entry in WINS). You said
you had WINS server in place, so now follow all the steps below to determine
why the server is not showing up in My Network Places.
1) First, NetBIOS over TCP/IP must be enabled if you want a computer to show
up in My Network Places. If NetBIOS over TCP/IP is enabled but the computer
still cannot be seen, go to step #2.
2) File & Print Sharing must be enabled
3) No host-based firewall blocking the NetBIOS ports 137, 138 & 139
4) Open a command prompt and run the following command on the problem
machine:
Net config server
If the output of 'Server hidden' displays 'Yes' that's the problem. If
value is 'No" go to step #5.
5) The machine description cannot be more than 48 characters or else the it
will not appear in Network Places.
6) A master browser on that subnet may have recently been turned off or
re-started. If no master browsers have been turned off or re-started
recently, go to step #7.
7) Go to the Local (Subnet) Master Browser and verify if you can see the
missing computer in it's Network Neighborhood. You determine a Local
(Subnet) Master Browser by running the command "browstat status" on any
computer in that subnet. Browstat.exe is a Resource Kit utility. If you
can find the missing computer in the Network Neighborhood of the Local
(Subnet) Master Browser, then go to the Domain Master Browser (which should
be the PDC Emulator in a Windows 2000 or above domain, or the PDC in an NT
4.0 domain (domainname 1B entry in WINS)), and see if you can find the
missing computer in it's Network Neighborhood. If you do not see the
missing computer then the problem is with the sharing of the browse list
between the Local (Subnet) Master Browser and the Domain Master Browser.
This can be caused by who has the IsDomainMaster setting in the registry.
Go to both the Local (Subnet) Master Browser and Domain Master Browser and
see and compare this registry setting. It exists at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
Normally, only the Domain Master Browser should be configured for the
IsDomainMaster setting. Without a PDC or PDCE, browsing is limited to the
local segment. (Only a PDC or PDCE has the ability to merge browse lists.)
Any server which can potentially be a Master Browser should have the
"IsDomainMaster" setting set to TRUE.
8) Restart the Computer Browser service on the Domain Master Browser (The
PDC of an NT 4 domain or the PDC Emulator of a Windows 2000 or above
domain). Although this may not be necessary it can't hurt.
9) Run the command browstat elect <transport> <domain> on a computer in the
subnet where browsing is a problem. You can obtain <transport> information
by running the command browstat status, and <domain> is the NetBIOS name of
you domain.
This forces an election in the subnet for a new Master Browser. A new
Master Browser will, hopefully, have the correct, updated list of NetBIOS
resources in the domain.
NOTE: A common end-user workstation can be a Subnet Master Browser and this
is not necessarily, in and of itself, a problem for domain browsing (esp. in
situations where there are no servers on that subnet). Most corporate
environments maintain servers in a common Data Center and therefore there
will be end-user workstations functioning as Subnet Master Browsers. As
long as it keeps an updated list all should be fine.
102878 - Information on Browser Operation:
http://support.microsoft.com/?id=102878
102878 - Information on Browser Operation:
http://support.microsoft.com/?id=102878
SRX040902603949
-----------------------------------
The first thing I would do is to disable the built in firewalls on the XP
SP2 computer or modify them so that they allow traffic from your subnet on
ports 137 UDP,138 UDP,139 TCP, and 445 TCP. If you are protected from the
internet by a router/firewall I would simply disable the ICF firewall on all
the computers. Also give some time for the browse list to build and be sure
to shut down the computers properly. Since you have a server I would also
configure wins on it and make sure that all computers are wins clients
including that the server is a wins client to itself.
By default netbios over tcp/ip should be enabled on all the computers
[tcp/ip properties/advanced/wins]. If you run Ipconfig /all it will tell you
ONLY if it is disabled. Running nbtstat -n on each computer should show at
least three name registries with the server probably showing more and at
least one computer needs to show that it is a master browser. Personal
firewalls or other "protection" software may interfere with the browse list
and often booting into safe mode with networking will bypass such programs.
11-16-04
S. Umbach
-- Todd J Heron, MCSE Windows Server 2003/2000/NT ---------------------------------------------------------------------------- This posting is provided "as is" with no warranties and confers no rights
- Next message: Michael Giorgio - MVP: "Re: WINS issue"
- Previous message: Herb Martin: "Re: Slow browse on Windows NT world domain - latency 300 ms"
- In reply to: Ian: "Re: WINS issue"
- Next in thread: Michael Giorgio - MVP: "Re: WINS issue"
- Reply: Michael Giorgio - MVP: "Re: WINS issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
