Can't map driver on VPN through win2k server

  • Thread starter Thread starter paquette
  • Start date Start date
P

paquette

My office machine is a Win2k server, a subdomain of a large unversity
domain. Ever since SP4 I've had difficulty mapping drives through it.
I did a lot of reading on this problem a few years ago and decided that
after SP4 I would need to openate the DNS server on my server to use
DNS naming. To make a long story short I have used VPN IP numbers to
use VPN (PPTP) to my home machines and vice versa--pain in the neck
because I have to write down current ip numbers. I run WINS but it no
longer even registers any machine but my server itself.

So here is the situation in a nutshell:

1 multiple machines (all clients XP Pro) at home behind a multiple-VPN
router
2. VPN connections using office VPN ip (no DNS names) to office
machine have no problem with mapping or terminal-server sessions
3. Same is true of sessions on the office machine to home machines.
4. I absolutely cannot seem to map or get terminal-server connections
from remote machines although the VPN connection seems fine.

Can anyone help me with this problem?
 
PS. What I mean to say is I absolutely cannot map or get
terminal-server sessions TO home machines from remote machines. No
problem getting them to server!
 
Can you ping the home PPTP IP from remote machine? also you may want to use DDNS so that you don't need to remember the IP.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
My office machine is a Win2k server, a subdomain of a large unversity
domain. Ever since SP4 I've had difficulty mapping drives through it.
I did a lot of reading on this problem a few years ago and decided that
after SP4 I would need to openate the DNS server on my server to use
DNS naming. To make a long story short I have used VPN IP numbers to
use VPN (PPTP) to my home machines and vice versa--pain in the neck
because I have to write down current ip numbers. I run WINS but it no
longer even registers any machine but my server itself.

So here is the situation in a nutshell:

1 multiple machines (all clients XP Pro) at home behind a multiple-VPN
router
2. VPN connections using office VPN ip (no DNS names) to office
machine have no problem with mapping or terminal-server sessions
3. Same is true of sessions on the office machine to home machines.
4. I absolutely cannot seem to map or get terminal-server connections
from remote machines although the VPN connection seems fine.

Can anyone help me with this problem?
 
No I can't ping the home machines--only the office machine!

As for DDNS--sounds interesting. I wonder if our security people would
be upset????
 
Please explain your setup. Is the VPN being handled by the router at home?
Or (since you bring up PPTP) is this a Windows PPTP VPN from one of your
Windows clients at home to (a) a router at work, (b) a Windows RRAS server
at work (c) something else?

It sounds like you have a VPN initiated in both directions? What is that
setup (as above)?

....kurt

Can you ping the home PPTP IP from remote machine? also you may want to use
DDNS so that you don't need to remember the IP.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
My office machine is a Win2k server, a subdomain of a large unversity
domain. Ever since SP4 I've had difficulty mapping drives through it.
I did a lot of reading on this problem a few years ago and decided that
after SP4 I would need to openate the DNS server on my server to use
DNS naming. To make a long story short I have used VPN IP numbers to
use VPN (PPTP) to my home machines and vice versa--pain in the neck
because I have to write down current ip numbers. I run WINS but it no
longer even registers any machine but my server itself.

So here is the situation in a nutshell:

1 multiple machines (all clients XP Pro) at home behind a multiple-VPN
router
2. VPN connections using office VPN ip (no DNS names) to office
machine have no problem with mapping or terminal-server sessions
3. Same is true of sessions on the office machine to home machines.
4. I absolutely cannot seem to map or get terminal-server connections
from remote machines although the VPN connection seems fine.

Can anyone help me with this problem?
 
Thanks for the reply.

VPN is hosted by the Win2k server. Clients (PPTP) dialup into this
machine. No problem with these connections which are across a
multiple-VPN router at home. As long as I have established a VPN
connection from one of the home clients, I can map drives in either
direction (actually I have to use nbtstat -A ip# prior to mapping to a
home machine from the office server). What will not work is dialing in
from a remote location (other than home) to one of the home machines.
Even if I have the correct ip#, nbtstat -A will not work. A week or so
ago I needed a file that turned out to be only on one of my home
machines (very unlike me!). I was at the other end of the province and
wound up having to do a terminal-server session into my office machine,
retreive the file to that machine, and then transfer it from there to
my laptop on a map from the laptop to the server. Logically it seems
to me I should have been able to map directly to the home machine from
my laptop if both machines were connected by VPN.
 
Back
Top