Re: S2003 poor netbios resolution
- From: "Robert L. \(MS-MVP\)" <blinNoEmailPlease@xxxxxxxx>
- Date: Wed, 26 Mar 2008 16:04:31 -0500
Do you have WINS server? Or use browstat to troubleshoot it.
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Anteaus" <Anteaus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2106F968-825A-476C-9AF7-052E626817EC@xxxxxxxxxxxxxxxx
Server 2003 R2, installed about a week ago, some clients won't be domain
members and hence will rely on netbios resolution.
Anyway, since installing the AD, netbios name resolution has been sluggish.
It was 100% reliable beforehand.
Symptoms are that some machines (why only some I don''t know) cannot browse
the LAN or connect to shares at startup. This can be resolved by pinging the
DC's IP address, which brings the connection to life. Not a question of
waiting either- no ping, no name resolution.
Until you ping the DC's IP address, you cannot ping the DC either by netbios
or DNS name. Once you ping it by IP, then you can do the former.
The DC is set to be the browse master.
The DNS side of things is fine, and one resolution (yet to be tried) is to
put the clients onto using the DC's DNS service as a resolver of internal
names. I may just do that and see if it improves matters. But, the problem
shouldn't be there anyway.
Just wondered if anyone could shed any light? A policy that stops netbios
announcements, perhaps?
.
- Follow-Ups:
- Re: S2003 poor netbios resolution
- From: Anteaus
- Re: S2003 poor netbios resolution
- Prev by Date: Re: VPN access to another server
- Next by Date: Re: Network Infrastructure
- Previous by thread: Re: netlogon and Gbit ethernet issue
- Next by thread: Re: S2003 poor netbios resolution
- Index(es):
Relevant Pages
|