What could cause a workstation to loose connectivity to a server?

[Mike Turner]

My office has two locations, the file server is at location A using the subnet 192.168.0.1. Location B uses the subnet 192.168.1.1.

Typically, in order to connect workstations from location B to the file server in location A I have to modify the host file, add the appropriate credentials and I'm good to go (or map a network drive).

The problem child computer at location B has lost server connectivity. Workstation is running XP SP3 and file server is running MS Server 2003 R2 - SP2.

The curious thing is that the workstation can still connect to the internet and I can successfully ping the server but everytime I attempt to connect to the server, it displays the error message //the server is not accessible...ne twork path not found.

I have checked all network settings, credentials, did a system restore, uninstalled and re-installed the NIC, check the host file.....etc etc.

I am running out of patience with this issue..any help is appreciated!

Thanks, Mike

[Patrick M]

Mike,

A lot of times, if you're unable to connect to the server but you can get online and can ping the server, it usually is the firewall on the workstation causing an issue. Turn the firewall off and try the connection again. Sometimes, you might have multiple firewalls on the machine, especially if you have security software loaded. You don't want multiple firewalls being active as they will conflict with each other. Try it and see what happens.

Tier 3 Tech
New York Life Insurance Company

[Mike Turner]

I turned off the Windows firewall and nothing happened.!? I am really confused because this happened all of a sudden fr no apparent reason and I have 20 other workstations configured the same way and they have no problems at all!

[Patrick M]

Mike,

What is the OS of the workstation and the server? I doubt its with the server because the other workstations can connect. Have you checked the IP configuration of the workstation to make sure everything is correct? You might even want to flush the DNS cache on the workstation.

[Mike Turner]

Workstation = XP SP3 and the server is running MS Server 2003 R2 - SP2. And the ip configuration is correct.

[Patrick M]

Do you get any errors when trying to connect? How is the workstation connecting? Active Directory, domain, etc?

[Mike Turner]

We are not setup on a domain, only WORKGROUP.

Typically, in order to connect workstations from location B (subnet 192.168.1.1) to the file server in location A (subnet 192.168.0.1), I have to modify the host file adding the server ip and name, add the appropriate credentials and I'm good to go (or map a network drive).

When conneting I receive the error the server is not accessible, you may not have the credentials to access this computer...netw ork path not found.

[Patrick M]

Have you checked to make sure that the work group name on the failing workstation is correct?

The thing that makes no sense is that you have a server machine but you setup a work group. You're not utilizing the server machine to its full capacity.

When it comes to connecting workstations to the server, modifying the hosts file is usually something that wouldn't need to be modified.

What you should do is restructure your whole network. Don't use a work group when you have access to a server machine. Use a domain instead.

Either way, it looks like your DNS cache or IP addressing might need to be rebuilt. I would highly suggest a domain environment though seeing as though you have MS Server 2003 R2.

When it comes to the IP addressing, are you using static or dynamic IPs? Are you using a DHCP server anywhere?

[Mike Turner]

We only use static ip's for our servers. All client machines are dynamically assigned from our managed routers. When setting up a domain, can that work with different subnets? Or would I have to have the same subnet at each location?

[Patrick M]

You can use different subnets when setting up a domain. Just make sure that you configure the routing and remote access portion through Active Directory on the server for it.