Networks

Ask something
Question Locked

WIn2003Server doesn't see one workstation

0 helpful
5 replies

by t.laskowski

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I have a problem with Windows 2003 Server domain controller. I am managing this server remotely. One workstation can log on to domain and everything works fine, however when trying to ping,remote desktop, access shares or anything really from the server it won't work.
Server doesn't recognize this machine in the network at all. No problems with any other workstations.
Server is running as dc,dns, file server and Routing/VPN to allow internet access from workstations.

I would appreciate any help.

5 replies

by scott_heath

Can you post any errors you receive when attempting to connect to this PC. It sounds like one of two things right now: local firewall on the PC or a trust issue with the domain. Can a user sit down at it and log into the domain? Have you verified Windows Firewall is not running?

by t.laskowski

Thanks for reply.
User can log on to domain from this machine and there are no problems at all.
I have disabled firewall through group policy but it didn't help.
The only thing I can think of is perhaps some dns issues... the local domain i am using for my server is the same as external website for this company or some NAT issues (i am not expert in it).
The error messages : unable to resolve host while trying to ping or connect via unc.
If i go to active directory I can see this workstation but i can't do anythig with it.
When i try to right click and MANAGE - "can't find the path"
When i ping this machine, it resolves the ip adress but i get time limit error.

It is a simple Win2003Server and 8 workstations. I have installed Server as a DC and it serves as Router for internet connection and file server.

please help

The problem is that i am in remote location now so I am unable to check or configure this pc on site. I am using Remote Desktop to connect to the server.

by scott_heath

Someone is going to have to be at the workstation. There are several possible issues here. Could be the policy didn't apply so the firewall is still active. Could be a trust issue is keeping the system from updating it's DNS entry. Could be the wrong DNS servers specified on the system. You'll need to walk a user through checking some of these things.

by triathlete1981

There should be no issue with using same domain on outside and inside. We do the same thing. But, our DHCP server was pointing people to external DNS servers. We noticed logging in took forever as well as saving to the servers. Also, some people were inexplicably unable to log in, and the only errors we got were "unable to log in" or "unable to find domain controller".

We had one server start running DNS and then pointed everyone to this new internal DNS server. That solved all problems mentioned above.

Running so many services on your domain controller isn't recommended, but it's possible. And with only 8 workstations, I would feel safe running DNS on the DC.

Good luck.

This discussion is closed to new replies.