• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 267
  • Last Modified:

Can not access a domain workstation, workstation stopped sharing

Hello Experts, I have a workstation on our domain network which decided to stop sharing and will not allow any access to it’s resources.  The workstation is displayed in the network list, but when anybody tries to access it the following error is returned.  It is not a firewall issue as I have tested the connection with the firewall disabled, and it returned the same result.  Where should I start?

(I should add that this workstation (Station-338) can access all other resources on the network without any issues, even other workstation shares.)

Error Screen Shot
1 Solution
Does the computer account still exist in AD?
shrimpforkAuthor Commented:
Yes it does exist in the AD.  It has full access to all network resources.
shrimpforkAuthor Commented:
I also just noticed that Station-338 will not respond to pings.
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

shrimpforkAuthor Commented:
I think this issue pertains to a few computers on my network.  I have 7 workstations on my network can not be accessed, but all computers show up in the network list and are in the AD with all the others.
Hypercat (Deb)Commented:
Have you checked the physical side of things - switches or other network equipment that is between these workstations and the others? If, for example, they're all connected to the same switch, then I'd suggest rebooting the switch first, as the easiest thing to do that might fix the problem.  

Do you have up-to-date antivirus/antimalware running on these workstations?  Is Network Discovery and File Sharing turned on for these machines? Have you checked not only the AD OU that they are in, but also DHCP/DNS to make sure that they have current DHCP leases and DNS registrations?  A computer can be seen in AD even when it's not communicating properly with the network.  Does anything happen (error messages or odd behavior) when you restart the workstations?  Are there any errors or warnings in the workstation event logs that might be relevant?
Lior KarasentiCommented:
Are your Workstation and Server services running?  The Server service should be configured to run as the Local System account, and the Workstation service should be running as the Network Service account.

shrimpforkAuthor Commented:
I have just discovered that I got something really funky going on.  This workstation (Station-338) was not listed in the list of reservations in the DHCP on the domain controller.  I discovered that this workstation has decided to connect and get a IP address from my firewall.  The firewall is configured as a DHCP for VPN connections and only has a list of 5 IP addresses.  For some reason this workstation is not wanting to get it's IP address from the domain controller.  Why is this?  My main DC which has the DHCP is Windows Server 2003.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now