Network Browsing Problem

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

Guest
Hello,
We just installed a new Windows 2003 Server domain controller on our
network. I demoted our old server and everything seemed to be working ok
until I tried to browse the network from an XP Pro client. It is extremely
slow and when it does open our domain it doesn't show the server. On Vista
Business machines I can browse without any problems. Also, sometimes the XP
Pro machines won't log in and give a "domain is not available" message. If I
log in locally and unc map to the server it will allow me to login, but if I
restart I still cannot login tot he domain. I've even unjoined and rejoined
the domain and it still gives that error. Any suggestions you have would be
greatly appreciated.
Thanks,
Tom
 
Re: Network Browsing Problem

Tom <Tom@discussions.microsoft.com> wrote:
> Hello,
> We just installed a new Windows 2003 Server domain controller on our
> network. I demoted our old server

If it was your sole domain controller, did you first transfer all the FSMO
roles to the new (replacement) DC?

> and everything seemed to be
> working ok until I tried to browse the network from an XP Pro client.

Browsing is a NetBIOS thing. If you want to browse, a) NetBIOS over TCP/IP
should be enabled on all servers/computers, and b) you should be using WINS.


> It is extremely slow and when it does open our domain it doesn't show
> the server. On Vista Business machines I can browse without any
> problems. Also, sometimes the XP Pro machines won't log in and give
> a "domain is not available" message.

Try posting an unedited ipconfig /all from a problem client & the server.

> If I log in locally and unc map
> to the server it will allow me to login, but if I restart I still
> cannot login tot he domain. I've even unjoined and rejoined the
> domain and it still gives that error. Any suggestions you have would
> be greatly appreciated.
> Thanks,
> Tom
 
Re: Network Browsing Problem

Yep, I transferred all of the FSMO roles from the old domain controller to
the new on before demoting it. Here is the server's IPCONFIG /ALL.
IP: 10.130.2.49
Sub: 255.255.254.0
Gwy: 10.130.2.1
DNS: 165.234.71.10
10.130.2.49
The clients are DHCP with their Primary DNS the same as the server, and the
Secondary DNS pointing to the DC's IP.
Enable NetBIOS or TCP/IP is enabled on the server and clients and like I
said only the Windows XP clients are having the problem. Vista is super fast
and has no login problems.
Thanks for the quick response.
Tom

"Lanwench [MVP - Exchange]" wrote:

> Tom <Tom@discussions.microsoft.com> wrote:
> > Hello,
> > We just installed a new Windows 2003 Server domain controller on our
> > network. I demoted our old server
>
> If it was your sole domain controller, did you first transfer all the FSMO
> roles to the new (replacement) DC?
>
> > and everything seemed to be
> > working ok until I tried to browse the network from an XP Pro client.
>
> Browsing is a NetBIOS thing. If you want to browse, a) NetBIOS over TCP/IP
> should be enabled on all servers/computers, and b) you should be using WINS.
>
>
> > It is extremely slow and when it does open our domain it doesn't show
> > the server. On Vista Business machines I can browse without any
> > problems. Also, sometimes the XP Pro machines won't log in and give
> > a "domain is not available" message.
>
> Try posting an unedited ipconfig /all from a problem client & the server.
>
> > If I log in locally and unc map
> > to the server it will allow me to login, but if I restart I still
> > cannot login tot he domain. I've even unjoined and rejoined the
> > domain and it still gives that error. Any suggestions you have would
> > be greatly appreciated.
> > Thanks,
> > Tom
>
>
>
>
 
Re: Network Browsing Problem

Tom <Tom@discussions.microsoft.com> wrote:
> Yep, I transferred all of the FSMO roles from the old domain
> controller to the new on before demoting it. Here is the server's
> IPCONFIG /ALL.
> IP: 10.130.2.49
> Sub: 255.255.254.0
> Gwy: 10.130.2.1
> DNS: 165.234.71.10
> 10.130.2.49

The DNS config is the problem. All servers & clients must specify only your
internal DNS server - no public IPs should be there at all. Your DNS server
should be configured to use forwarders to your ISP's DNS server for external
queries (and or root hints)


> The clients are DHCP with their Primary DNS the same as the server,
> and the Secondary DNS pointing to the DC's IP.

See above....


> Enable NetBIOS or TCP/IP is enabled on the server and clients and
> like I said only the Windows XP clients are having the problem.

Browsing isnt' related to DNS - and AD requires that DNS be set up as I
mentioned.


> Vista is super fast and has no login problems.

It is / will, even if you aren't seeing symptoms or problems right now!


> Thanks for the quick response.

No prob - hope this helps.

> Tom
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Tom <Tom@discussions.microsoft.com> wrote:
>>> Hello,
>>> We just installed a new Windows 2003 Server domain controller on our
>>> network. I demoted our old server
>>
>> If it was your sole domain controller, did you first transfer all
>> the FSMO roles to the new (replacement) DC?
>>
>>> and everything seemed to be
>>> working ok until I tried to browse the network from an XP Pro
>>> client.
>>
>> Browsing is a NetBIOS thing. If you want to browse, a) NetBIOS over
>> TCP/IP should be enabled on all servers/computers, and b) you should
>> be using WINS.
>>
>>
>>> It is extremely slow and when it does open our domain it doesn't
>>> show the server. On Vista Business machines I can browse without
>>> any problems. Also, sometimes the XP Pro machines won't log in and
>>> give a "domain is not available" message.
>>
>> Try posting an unedited ipconfig /all from a problem client & the
>> server.
>>
>>> If I log in locally and unc map
>>> to the server it will allow me to login, but if I restart I still
>>> cannot login tot he domain. I've even unjoined and rejoined the
>>> domain and it still gives that error. Any suggestions you have
>>> would be greatly appreciated.
>>> Thanks,
>>> Tom
 
Back
Top