VPN Access Problem

[mcp6453]

My host computer is Windows 2000 Pro. The remote computer is Windows XP
SP2 with firewall disabled. The host machine is behind a router with
PPTP forwarded to the static IP of the Win2K machine. Incoming
connections are allowed, and several users have been added to the
authorized user list.

When I dial into the host machine from the remote machine, the VPN
connects easily and quickly. The remote machine is handed an IP address
(192.168.1.103) by the host machine (192.168.1.11). The IP of the remote
machine is 192.168.4.49, so they are on different subnets.

After the VPN connects, I cannot get any further: I cannot see the
drives on the host machine even though there are several shares with
"Everyone" rights. I cannot ping \\machine_name or \\192.168.1.11. What
am I missing here? Is an lmosts entry needed to be able to ping an IP
address? (The host machine is set to respond to pings.)

 

[Phillip Windell]

My host computer is Windows 2000 Pro. The remote computer is Windows XP
SP2 with firewall disabled. The host machine is behind a router with
PPTP forwarded to the static IP of the Win2K machine. Incoming
connections are allowed, and several users have been added to the
authorized user list.

When I dial into the host machine from the remote machine, the VPN
connects easily and quickly. The remote machine is handed an IP address
(192.168.1.103) by the host machine (192.168.1.11). The IP of the remote
machine is 192.168.4.49, so they are on different subnets.

The IP# of the Nic doesn't mean anything,..the IP# of the VPN Adapter
aquired when the connection "happened" is what matters. So they are on the
same subnet, not different ones.

After the VPN connects, I cannot get any further: I cannot see the
drives on the host machine

You won't if they aren't the same workgroup or members of the same domain.

even though there are several shares with "Everyone" rights.

Everyone does not mean "litterally" Everyone. It only means everyone on the
particular local machine,...which doesn't incude the other machine dialing
into it with VPN. You need matching user accounts/passwords on both
machines.

I cannot ping \\machine_name or \\192.168.1.11. What am I missing here?

Nothing. I think it is working.

Is an lmosts entry needed to be able to ping an IP address? (The host
machine is set to respond to pings.)

If you want to use Netbios Names of the machines, that would be one way,
yes.

 

[mcp6453]

The IP# of the Nic doesn't mean anything,..the IP# of the VPN Adapter
aquired when the connection "happened" is what matters. So they are on the
same subnet, not different ones.




You won't if they aren't the same workgroup or members of the same domain.




Everyone does not mean "litterally" Everyone. It only means everyone on the
particular local machine,...which doesn't incude the other machine dialing
into it with VPN. You need matching user accounts/passwords on both
machines.




Nothing. I think it is working.

Is an lmosts entry needed to be able to ping an IP address? (The host
machine is set to respond to pings.)

If you want to use Netbios Names of the machines, that would be one way,
yes.

Thanks for the information. Unfortunately, you did not give me enough
information for me to understand how I can connect to the host drives
EXCEPT that the computers are in two different workgroups. Is the
easiest solution to change the workgroup for the remote computer(s) or
can a separate workgroup be specified specifically for the VPN
connection? What should the lmhosts entry be?

Your help is greatly appreciated!

 

[Phillip Windell]

Don't include the slashes when you ping.

can a separate workgroup be specified specifically for the VPN
connection?
No.

What should the lmhosts entry be?

You already have on on the machine. Eaxmine it,...the information to add to
it is in the file itself.

I have never seen a VPN situation work where you were VPN'ing from a
workstation to a workstation. I am not familiar with trying to make a
workstation act like a VPN Server.

 

[mcp6453]

Don't include the slashes when you ping.

Sorry, that was a typo. I know better.

I have never seen a VPN situation work where you were VPN'ing from a
workstation to a workstation. I am not familiar with trying to make a
workstation act like a VPN Server.

I had it working once before, but I am not having any luck now. I'm
connecting, but I cannot get anything after that to connect.

 

[Phillip Windell]

I had it working once before, but I am not having any luck now. I'm
connecting, but I cannot get anything after that to connect.

Ok, well,..hang around and see if anyone else has any ideas.