Cleint computer cannot access LAN, but can access everything else.

[Guest]

I have a NT 2000 server, and a XP pro (SP2) client computer (named RD12), and
for some reason am unable to access the network resources. I am able to ping
the default gateway, and remote hosts, but cannot get RD12 to ping itself
(other than through 127.0.0.1). The server and other clients can
successfully ping RD12 ip address, but not the other way. I have tried
ipconfig /release, /renew, and gpupdate.exe. The event viewer on RD12 does
show errors for auto enrollment and userenv.

The server, coincidentally, shows an Mxsmrb error, that says "The master
browser has received a server announcement from the computer RD12 that
believes that it is the master browser for the domain on transport
NetBT_Tcpip_{4B61C064-E4AF-4D2A-A079."

I would appreciate any thoughts on how to correct this. Thanks.

 

[RWS]

Could try this - won't hurt and is entirely reversable -
On the XP Pro computer named RD12:

Start > Run > services.msc
Stop the Computer Browser service and then disable it -
Close out of Services
Reboot the computer and test for resolution

 

[Chuck]

On Thu, 4 Aug 2005 07:03:03 -0700, "Carl Dawson" <Carl

I have a NT 2000 server, and a XP pro (SP2) client computer (named RD12), and
for some reason am unable to access the network resources. I am able to ping
the default gateway, and remote hosts, but cannot get RD12 to ping itself
(other than through 127.0.0.1). The server and other clients can
successfully ping RD12 ip address, but not the other way. I have tried
ipconfig /release, /renew, and gpupdate.exe. The event viewer on RD12 does
show errors for auto enrollment and userenv.

The server, coincidentally, shows an Mxsmrb error, that says "The master
browser has received a server announcement from the computer RD12 that
believes that it is the master browser for the domain on transport
NetBT_Tcpip_{4B61C064-E4AF-4D2A-A079."

I would appreciate any thoughts on how to correct this. Thanks.

Carl,

I suspect that you need to provide more detail about your network. What network
resources are you unable to access, and from which computers? How are you
trying to access the resources - thru Network Neighborhood, by mapped shares,
what? What operating systems are on the network resources (name, edition,
service pack)?

How about you start by providing "browstat status" and "ipconfig /all" on the 2
computers you listed, and for 2 others?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

And look at RD12. First for any misconfigured or overlooked personal firewalls.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Then at registry setting restrictanonymous.
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>
Finally, at LSP / Winsock.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

If RD12 has an IPConfiguration, don't worry about "ipconfig /release" or
"/renew". And don't fool with gpupdate til you get your TCP/IP problems
resolved. Diagnose the problem first.

 

[Guest]

Chuck: I think maybe I meant domain as opposed to network. Disabling the
browser as suggested by RWS resolved the error message on my server but has
not resolved the computer's inability to access domain resources.

We have a microsoft network, with a domain that we access for resources on
the server (ie files, printers, exchange) the server is running microsoft
small business server which is NT 2000 with whatever the latest SP is (I
think 4), and is also our exchange server. All the other computers run XP
pro, with sp2 installed. About a week ago, this particular computer, named
RD12, just quit being able to access the domain. using "ping" I can ping the
other computers in the office from RD12, but RD12 cannot ping itself, nor can
the other computers in the office ping it.

Does that help explain the problem?

 

[Guest]

RWS: that appears to have resolved the error message on the server, but has
not allowed the other computer to access the domain. Thank you for the
assistance. If you have any other ideas, please let me know. I posted a
longer explanation to CHuck's questions about the network. Carl

 

[Chuck]

Chuck: I think maybe I meant domain as opposed to network. Disabling the
browser as suggested by RWS resolved the error message on my server but has
not resolved the computer's inability to access domain resources.

We have a microsoft network, with a domain that we access for resources on
the server (ie files, printers, exchange) the server is running microsoft
small business server which is NT 2000 with whatever the latest SP is (I
think 4), and is also our exchange server. All the other computers run XP
pro, with sp2 installed. About a week ago, this particular computer, named
RD12, just quit being able to access the domain. using "ping" I can ping the
other computers in the office from RD12, but RD12 cannot ping itself, nor can
the other computers in the office ping it.

Does that help explain the problem?

Carl,

That's a start to describing the scope of the problem, but to diagnose it you'll
still need to provide the diagnostic information, and investigate further per my
instructions.

The browser, and in particular the browser message, may be symptomatic of the
problem, but if you have ping problems, you'll need to start there (assuming
TCP/IP is the transport used). And "browstat status" and "ipconfig /all" should
be very useful. Then read my articles.