VPN

[Guest]

I am new to VPN's and having issues. I am using Microsoft's VPN software it is connecting fine but when I try to map a drive or ping the remote server it does not ping or I can't map the drive. I am getting an ip though and the correct DNS servers. Any ideas? Thanks

 

[Lanwench [MVP - Exchange]]

So you can ping by IP, but not by name?
Might need WINS installed on your server & use the WINS server IP in your
local IP config -

- or an LMHOSTS file. See http://support.microsoft.com/?scid=kb;en-us;180094

Note - the padding spaces for the domain name (0x1b) entry are very
important - be sure not to miscount!

For more info, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;150800

 

[Guest]

No I can not ping I do get an ip address though

So you can ping by IP, but not by name?
Might need WINS installed on your server & use the WINS server IP in your
local IP config -

- or an LMHOSTS file. See http://support.microsoft.com/?scid=kb;en-us;180094

Note - the padding spaces for the domain name (0x1b) entry are very
important - be sure not to miscount!

For more info, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;150800

 

[Lanwench [MVP - Exchange]]

If you can't ping the server by its LAN IP, you aren't getting a good VPN
connection or there's a configuration problem on the server side.

 

[Guest]

Ok well I got it to work. I didn't know that they needed to be on different subnets, so when I changed that it worked fine. I could map the drive, but my problem now is that it is very very slow. The application that I am trying to use never fully opens just the splash screen is stays there. It is dsl connections on both ends. The client machine is a p4 512 meg of ram. The server is p3 392 meg of ram. Thanks again

 

[Lanwench [MVP - Exchange]]

Ok well I got it to work. I didn't know that they needed to be on
different subnets, so when I changed that it worked fine.

Yes - if you're using 192.168.0.0 at home and at work you'll have problems
(etc.).

I could
map the drive, but my problem now is that it is very very slow. The
application that I am trying to use never fully opens just the splash
screen is stays there. It is dsl connections on both ends. The
client machine is a p4 512 meg of ram. The server is p3 392 meg of
ram. Thanks again

Opening applications across a VPN connection can be very slow indeed - same
with large files. Terminal Services/Remote Desktop is usually preferable in
these situations - with VPN you may lose your connection/freeze and lose
data.

 

[Phillip Windell]

Ok well I got it to work. I didn't know that they needed to be on

different subnets, so when I changed that it worked fine. I could map the
drive, but my problem now is that it is very very slow. The application
that I am trying to use

That is typical. VPN is a low performance type of link. The most successful
and productive way I have used it is by using PCAnywhere, VNC, Remote
Desktop, Terminal Services. You use these remote control solutions to
control a machine on the main LAN and all the heavey traffic stays between
it and the LAN Resource and does not travel over the VPN.

Client/Server Applications that have a small footprint will probably work
fine. Our Newsroom system works fairly well even when the Client software
is separated from the Server via an old 56k (Nailed 56) link.