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

Server 2003 Cannot connect to some clients

We have MS Server 2003 and recently it became unable to connect to just 2 of the systems on the network. They all have had thier documnets folder mapped to network drives. When you try to connect to either of the two system as a network place for example it shows the system but none of the shared folders on that system. When I try to connect by typing either the IP of the system or the system names in the run box it says that the network path is not found. When I try to ping the ssytem it pings an address that is incorrect for the systems and times out. System IP = 192.168.1.123 but Server pings 192.168.1.184. I have tried to change the system's IP to match what the server is pinging but with no luck. When I try to ping the system by IP it times out 4 times. It really sounds like a connectivity problem but both systems can see, connect and use the server just fine. Other systems on the network can connect to the ones that the server is having issues with. The only thing that the two systems have in common is they has been testing VPN connections to the server with them recently.
0
JohnNewkirk
Asked:
JohnNewkirk
  • 3
  • 2
1 Solution
 
Jay_Jay70Commented:
Hi JohnNewkirk,

what results do you get when you run nslookup on the two client machines

do it on both name and ip and note the results for me

make sure windows firewall is disabled and any conflicting dns records are removed, try and find out where that different IP is coming from using nslookup on it as well

do you use DHCP at all

Cheers!
0
 
JohnNewkirkAuthor Commented:
I have cleared the arp even though it showed no conflicts. I ran nslookup on one of the machines. (I don't have access to the other one right now) It says "Default Server: ns1.mchsi.com Address: 204.127.203.135. I don't know how to clear the dns records. The server does not perform DHCP. We all get our IPs from the router. The server of course has a staic IP.
0
 
Jay_Jay70Commented:
ipconfig /flushdns
ipconfig /registerdns
0
 
JohnNewkirkAuthor Commented:
That worked for one of the systems! I though for sure that they had identicle problems. When I ping the other system by name, now instead of pingng an incorrect address is says cannot find host.
0
 
Jay_Jay70Commented:
ok so the record hasnt been recreated - jump into your dns manager and see if there is a host for the machine that is giving errors - if not then right click and create one
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

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