Re: Member server not in network n'hood.
From: Bill Grant (not.available_at_online)
Date: 03/07/05
- Next message: Todd J Heron: "Re: Member server not in network n'hood."
- Previous message: Matt Joyce: "Member server not in network n'hood."
- In reply to: Matt Joyce: "Member server not in network n'hood."
- Next in thread: Matt Joyce: "Re: Member server not in network n'hood."
- Reply: Matt Joyce: "Re: Member server not in network n'hood."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Mar 2005 17:31:06 +1100
The first thing to check is that Netbios over TCP/IP is enabled on the
server's NIC. The segment browse list is built using LAN broadcasts. The
machine will never appear in a domain browse list if it is not in the
local segment browse list.
When you are sure that Netbt is enabled, do a net view \\servername from
a command prompt on another machine in the same subnet. Does this display
the shares on the server? Can you map one using net use
\\servername\filename?
If that is working, try a net view command on this machine. Does it show
the W2003 server?
"Matt Joyce" <MattJoyce@discussions.microsoft.com> wrote in message
news:64224068-A440-403A-AD68-BF07B4EFD71F@microsoft.com...
>
> I have a 2003 standard server which does not appear when I browse the
> network.
> Browsing on a DC running DNS and WINS, it does not appear.
>
> `cmd /k ping MyServer`
> \\MyServer\Share work too.
>
> Running Browcon....
>
> ----------------------------------------------------------------------------------------------
> System Missing from its Local Subnet Master Browser's List
>
> Diagnosis:
>
> The subnet master browser on the missing system's subnet does not have the
> missing system in its browse list. Because of this, the missing system
> may
> also be missing from all other browse lists.
>
> This problem must be addressed before testing for other possible issues.
>
> NOTE: if the missing system was taken offline or hidden intentionally, it
> could take thirty minutes before this gets propagated across the network.
> Until then, the system may be missing in some master browser lists but not
> in
> others.
>
>
>
> Possible Causes:
>
>
> 1.
>
> Run the command "net config server" (without quotes) at the command
> prompt on the missing system. Is the "Server hidden" setting set to
> "Yes"?
> If so, this is why the system is missing in the browse list. To unhide
> the
> computer from the browser list, type "net config server /hidden:no"
> (without
> the quotation marks) at the command prompt on the missing system, and then
> press ENTER.
> 2.
>
> If the missing system is a Windows NT 4.0 system, check the length of
> the server comment. When the server comment is greater than 48
> characters,
> the server name may disappear from the browsing list. The server comment
> may
> be displayed by typing the following command at an MS-DOS command prompt:
> "net config server" (without the quotation marks). The server comment may
> be
> set by typing the following command at an MS-DOS command prompt:
>
> "net config server /srvcomment:"text"" (without the quotation marks)
>
> NOTE: This command does not allow you to specify a srvcomment greater
> than 48 characters. Nevertheless, the problem may exist if the srvcomment
> size is greater than 48 characters when it set directly in the registry
> (HKLM\System\CCS\Service\LanmanServer\Parameters).
>
> 3.
>
> The missing system's host announcement frame was not received by the
> subnet master browser. Reboot the missing system so that it will announce
> itself on the subnet again.
> 4.
>
> The subnet master browser may be multihomed. i.e. a system with more
> than one network interface including RAS/RRAS servers. Multihomed systems
> should not be allowed to hold a master browser role. Disable the Computer
> Browser Service on all multihomed systems. In this condition these
> systems
> will still be able to browse, but will not participate in browsing
> elections.
> 5.
>
> There may be contention between systems on the subnet as to which
> system is the subnet's master browser. Look for evidence of this problem
> in
> the System event log on systems located on the missing client's subnet. Do
> you see Browser events with the ID 8003? There are many possible reasons
> for
> these events:
>
> *
>
> Routers on the network are configured to forward UDP broadcasts.
> *
>
> IP subnet masks are not consistently set on all the systems on
> the
> subnet/network i.e. there is more than one logical IP subnet sharing one
> physical subnet. This is common on networks that use DHCP superscopes.
> *
>
> Incorrect static WINS entries. Ensure the entries for the 1B
> domain name, the PDC's NetBIOS name, and the subnet master browser's
> NetBIOS
> name are correct and consistent on all WINS servers on the network.
> *
>
> Switch configuration issues. i.e. switches should be
> consistently
> set to full-duplex or half duplex, but not mixed.
>
> ----------------------------------------------------------------------------------------------
>
> 1. the system is not hidden
> 2. this is a server 2003 system
> 3. the sytem has been rebooted several times
> 4. The Master Browser has several nics, but they are teamed and share a
> single ip.
> 5. I used to have 8003 eventys but have since stopped the Computer Browser
> on everything except a few servers.
>
>
> Any ideas ?
>
> This is really fraustrating.
>
>
> --
> Children's Cancer Institute Australia
> http://www.ccia.org.au
- Next message: Todd J Heron: "Re: Member server not in network n'hood."
- Previous message: Matt Joyce: "Member server not in network n'hood."
- In reply to: Matt Joyce: "Member server not in network n'hood."
- Next in thread: Matt Joyce: "Re: Member server not in network n'hood."
- Reply: Matt Joyce: "Re: Member server not in network n'hood."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
