Problem pinging PC from W2k3 server

[Chopsy]

I have a problem trying to ping a client PC from my server. I am at a different site, and am using Remote Desktop to access the server.

Server IP - 172.19.25.13
Client PC - 172.19.25.231
Router - 172.19.25.1

From a DOS window on the server, if I try to ping the client PC, I get one good response (1ms) and then 3 fails. If I do a tracert to that address, it tries to go out via my router, and I get 'request timed out' or 'TTL expired in transit' from the internal address of the router.

I have checked the routes on the server, and there is no reason why it should be trying to go via the router for that address.

I can ping other systems on the same subnet without any problems, and it seems that if I try and ping a local address that I know is not being used, it times out as you'd expect, and a tracert to that address fails as well (without trying to go out via the router)


Any suggestions?

Alan

 

[spool]

Is the Client's OS XP? Do you have Remote Desktop turned on at the client's side?

A small amount of help is better then none at all.
spool

 

[Chopsy]

The client PC is Win 95. It's running VNC for remote control, but I cant access the client.

 

[spool]

I was going to post some instructions on how to set up VNC. It's just to much to write down. I am going to give you the web site to Real VNC. It will be easier to understand.

I'm running VNC and have had no trouble with it. It is very simple to run. One thing I would say if you are using a router you will have to open some ports so VNC can run in out of your system. I think the ports are in the 5000 range.

http://www.realvnc.com/

A small amount of help is better than none at all.
spool

 

[Chopsy]

Thanks, but I already know how to use VNC. I was trying to access this client via VNC and couldn't and when I was trying to diagnose the problem I realised that I couldn't ping the client.

 

[PHead2]

What are the subnet masks on the server and the client PC?

Make sure they are both the same...