Make remote PC part of the network!

  • Thread starter Thread starter Dave H
  • Start date Start date
D

Dave H

Please Help

I have a standalone Win2k server that has a DOD + Static
Route set up to attach to a remote Win2k pro PC.

If I ping from the static route IP from the server, it
connects OK and future ping requests echo back sucessfully.

However, If I ping from a clinet PC connected to the
server, they always timeout.

Details:-

Server
IP 192.168.200.1
Static Route IP 192.169.200.51

Local Client
IP 192.168.200.55 (assigned via DHCP)
Default Gateway IP 192.168.200.1

Remote PC
Incomming TCP/IP properties
Specified IP address range 192.169.200.51 - 192.169.200.52
Allow calling computer to sepcify address - checked

When trying to access the remote (connected) PC from the
client, it appears that we are reaching the remote PC but
the replies never make it back to the server/client!!!

I have checked to routing tables and they seem to be
correct.

Any ideas on this one?
 
Bill

Thanks for your reply, it was much appreciated.

One last thing...

If a "ordinary dialup connection" will not work. What sort
of dial-up would? I assume it would be OK if the remote
end was a server running its own copy of RRAS. Is there
any way I could get this to work with additional
hardware/software/protocols/configuration etc?

If the answer is a final no then at least I will know not
to spend any more time on it.

Cheers
-----Original Message-----
An ordinary dialup connection cannot be used by a client behind the
"calling" machine. You can set up the routing to send the traffic across,
but replies won't come back. If you look at
Click to expand...
the "answering" machine you will
 
Back
Top