TS Remote Access via Dialup works sometimes only !!

I have approx 20 users succesfully using TS on W2K SP3 distributed on a
local lan or some from a branch office via a hardware VPN. I want to be
able to 'manage' the server from my home location using a dialup connection.
I have setup RRAS using its default settings - I have RAS get its IPs from
DHCP (a block of 10 IPs gets reserved) - I have given one user permission to
connect via dialup. The following happens . . .

When I dial up to the server I always get a successful connection and
authentication of the users logon credentials - no probs. When I try to
establish a TS session - I (19 times out of 20, or worse) get a 'Server may
be busy' type message - it is as if it cannot find the server. Once I do
get a successful connection to the TS I can work the remote desktop
indefinately with no further probs - it is just establishing that initial
session that seems to be so difficult.

I note that although the lan is using 192.168.111.x / 255.255.255.0 when I
'ipconfig' my NIC the interface for the remote is showing an IP of
192.168.111.x / 255.255.255.255 - this subnet appears to be isolating me
from the remote network, i.e. I cannot ping the server which is running TS,
AD, DNS, WINS, DHCP, etc. I am using the same IP range on my 'home lan'
i.e. 192.168.111.x / 255.255.255.0 - could this be causing the
roblem?? -or- is the subnet the issue ??

I am struggling with this one - I thought I understood IP, now I am doubting
myself - help

Stuart

Ah...since your home subnet and the TS subnet are the
same, the systems may be getting confused. People on this
newsgroup have reported things like this happening. Can
you change your home subnet to see if the problem still
persists?

-M

>-----Original Message-----
>I have approx 20 users succesfully using TS on W2K SP3
distributed on a
>local lan or some from a branch office via a hardware
VPN. I want to be
>able to 'manage' the server from my home location using a
dialup connection.
>I have setup RRAS using its default settings - I have RAS
get its IPs from
>DHCP (a block of 10 IPs gets reserved) - I have given one
user permission to
>connect via dialup. The following happens . . .
>
>When I dial up to the server I always get a successful
connection and
>authentication of the users logon credentials - no
probs. When I try to
>establish a TS session - I (19 times out of 20, or worse)
get a 'Server may
>be busy' type message - it is as if it cannot find the
server. Once I do
>get a successful connection to the TS I can work the
remote desktop
>indefinately with no further probs - it is just
establishing that initial
>session that seems to be so difficult.
>
>I note that although the lan is using 192.168.111.x /
255.255.255.0 when I
>'ipconfig' my NIC the interface for the remote is showing
an IP of
>192.168.111.x / 255.255.255.255 - this subnet appears to
be isolating me
>from the remote network, i.e. I cannot ping the server
which is running TS,
>AD, DNS, WINS, DHCP, etc. I am using the same IP range
on my 'home lan'
>i.e. 192.168.111.x / 255.255.255.0 - could this be
causing the
>roblem?? -or- is the subnet the issue ??
>
>I am struggling with this one - I thought I understood
IP, now I am doubting
>myself - help
>
>Stuart
>
>
>
>.
>