2000 Server, XP Workstation - 1 Way Networking = BAD

  • Thread starter Thread starter T Guiles
  • Start date Start date
T

T Guiles

I have a Windows 2000 Server with Active Directory
Services running. It is a new install, for the record.

Across the WAN, and NOT behind a firewall, is an XP Pro
system (also a nice fresh install).

The XP system can see and browse the 2000 server just
fine. The 2000 server can NOT see the XP system, both by
computer name AND IP. Other workstations throughout the
network CAN connect to the 2000 server and NOT the XP
workstation.

The 2000 server can, however, connect just fine to the XP
workstation via HTTP and FTP, and it can be pinged via the
computer name and IP.

Thanks in advance for the help, and let me know if you
need any more information.

T Guiles
 
Is the XP machine a member of the domain?
If you look on the Win2000 machine, do you see a computer
account in Active Directory?
Is there a DNS record for the XP machine on the 2000
machine's DNS server?
 
-----Original Message-----
Is the XP machine a member of the domain?
Yes.

If you look on the Win2000 machine, do you see a computer
account in Active Directory?
Yes.

Is there a DNS record for the XP machine on the 2000
machine's DNS server?
Click to expand...

Yes.
 
Interesting...ok, so try the following (and make sure you
have a share that is at least read-only to Everyone on
the XP machine):
Click to expand...

Yep. This is already set up like that.
From the 2000 server (or whatever machine is having
problems hitting the XP machine):

"net view \\<xpcomputername>"
Click to expand...

-- System error 53 has occurred.

-- The network path was not found.
"net view \\<xpipaddress>"
Click to expand...

-- Unknown host \\209.69.191.51.
Can you explain what the network setup is between the
server and this XP machine?
Click to expand...

The server is located in our office. Standard network
connectivity and internet connection through a T1/Wireless
setup. The workstation is at my boss's house/office,
which is also through a T1 connection.

They are both on the same network as well. The XP
workstation is not behind a firewall.

FYI... we have many many systems throughout the network.
These 2 systems that are giving us the problem are on
their own domain, however. But as I mentioned before, the
other stations can access the server and not the
workstation.

They communicate just fine via HTTP and FTP and a choice
other proprietary methods... It's just the file browsing
of the workstation from the server that is giving us the
problems... I also can't manage the workstation through
the Active Directory control panel, even though it is
there.

Also... there are other stations and servers at the same
site as the XP workstation that communicate just fine...
it's just this XP workstation for whatever reason...

I think that about covers it...

"Interesting..."

Yeah... our sentiments exactly :)

Thanks again...

T
 
Are the services "Workstation" and "Server" running? I've never been too
clear about this, but I've heard on more than one occasion that they need to
be running to browse the network. Just a thought.
 
Are the services "Workstation" and "Server" running? I've
never been too
clear about this, but I've heard on more than one occasion that they need to
be running to browse the network. Just a thought.
Click to expand...

Yes.
 
Got it.
There's a couple other things you should verify here.
Make sure the XP machine has Netbios over TCP/IP enabled
(properties of the network interface, double-click
TCP/IP, click Advanced, click WINS, click Enable NetBIOS
over TCP/IP).
If that was disabled, it's possible that it would cause
this problem.

Are there other machines on the same domain as these two,
or are these the only machines in the domain? If there
are others, I'm assuming you can get to them fine?

Also, does this XP machine have SP1 installed?
One final question, are there any errors in the System
event log that appear related to networking on the XP
machine?
 
Back
Top