I've set up a VPN now what?

Hi,

I have set up a VPN and can get the clients to successfully connect to it.
However, none of the server shares are visible on the remote client. Server
is sbs2k3 and client is xp pro. Connection is via adsl with ports 1723
forwarded.

Any help appreciated.

Jan

"Jan" <(E-Mail Removed)> wrote...
>I have set up a VPN and can get the clients to successfully connect to it.
>However, none of the server shares are visible on >the remote client.
>Server is sbs2k3 and client is xp pro. Connection is via adsl with ports
>1723 forwarded.

You will need WINS and DNS name resolution on the remote client.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Todd,

Thanks for the response. It seems very slow though. Unusable in applications
like MYOB. Do you have any suggestions to speed things up a bit?

Rgds
Jan

"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Jan" <(E-Mail Removed)> wrote...
>>I have set up a VPN and can get the clients to successfully connect to it.
>>However, none of the server shares are visible on >the remote client.
>>Server is sbs2k3 and client is xp pro. Connection is via adsl with ports
>>1723 forwarded.
>
> You will need WINS and DNS name resolution on the remote client.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>

The problem may be the MTU size. You can try adjusting this at the remote
servers and see if it helps.

TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT
http://support.microsoft.com/default...;EN-US;q120642

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default...b;EN-US;314053

The best way to determine the optimum setting for the MTU provided known
guaranteed bandwidth is to run the command:

ping xxx.xxx.xxx.xxx -f -l yyyy

where xxx.xxx.xxx.xxx is the remote host and yyyy are different sizes
starting with 1472. Once a response is received, add 28 to the yyyy
number. This is the optimum setting for the MTU at the remote server.

http://www.speedguide.net/read_articles.php?id=156

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Todd,

Once again thanks for the response. I followed your directions and
unfortunately it still appears to be too slow for practical use. I think
terminal services might give better results but I am reluctant to install
applications on my server (if it gets hacked at least they can't run the app
to go through the data).

Many thanks
Jan

"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The problem may be the MTU size. You can try adjusting this at the remote
> servers and see if it helps.
>
> TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT
> http://support.microsoft.com/default...;EN-US;q120642
>
> TCP/IP and NBT Configuration Parameters for Windows XP
> http://support.microsoft.com/default...b;EN-US;314053
>
> The best way to determine the optimum setting for the MTU provided known
> guaranteed bandwidth is to run the command:
>
> ping xxx.xxx.xxx.xxx -f -l yyyy
>
> where xxx.xxx.xxx.xxx is the remote host and yyyy are different sizes
> starting with 1472. Once a response is received, add 28 to the yyyy
> number. This is the optimum setting for the MTU at the remote server.
>
> http://www.speedguide.net/read_articles.php?id=156
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>

"Jan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Once again thanks for the response. I followed your directions and
> unfortunately it still appears to be too slow for practical use. I think

Welcome to VPN. VPN is a "Slow-Link, Dialup-based" technology.

ADSL is asyncronous (not same speed both ways),....So, VPN runs both
directions at the slower "upload speed" of the DSL.

Network Places, and Microsoft Networking in general, were designed and
intended to run over normal LAN speeds of 10mpbs and upwards,...not 256k or
whatever the DSL upload speed happens to be.

That is why most people combine the VPN with some type of remote control
ability such as VNC, PCAnywhere, Citrix, Terminal Services, or MS's Remote
Desktop.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------