G'Day
I can connect via a Draytek 2600 Router remotely via VPN & run RDP to SBS if
I remove bitmap caching.
I cannot run RDP on the W2K Terminal Server remotely.
RDP runs OK in-house on all the workstations.
I can ping the Terminal server & SBS by ip address & name once connected
remotely to SBS.
Could this be an ISP bandwidth problem. If so how can I prove it.

Any help would be appreciated as this has gone on for weeks now & I need to
maintain the TS remotely

Regards
David Hellewell

Re: VPN reposted by jimbehning

jimbehning
Mon Sep 01 20:13:42 CDT 2003

RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt that
is the issue. I vpn or rdp into sbs, and then get to the apps server
all the time. I have one account that has 10 users vpning and then rdp
into the apps server without issues. We are working totally with
Microsoft VPN at the server and at the remote workstations.

"David Hellewell" <dhellewell@ozemail.com.au> wrote:

>G'Day
>I can connect via a Draytek 2600 Router remotely via VPN & run RDP to SBS if
>I remove bitmap caching.
>I cannot run RDP on the W2K Terminal Server remotely.
>RDP runs OK in-house on all the workstations.
>I can ping the Terminal server & SBS by ip address & name once connected
>remotely to SBS.
>Could this be an ISP bandwidth problem. If so how can I prove it.
>
>Any help would be appreciated as this has gone on for weeks now & I need to
>maintain the TS remotely
>
>Regards
>David Hellewell
>

Jim B. SBS MVP

Re: VPN reposted by David

David
Mon Sep 01 20:53:39 CDT 2003

Thamks for your reply,
I also have other sites that I VPN & RDP into SBS, then get into the apps
server with no problems.
I do not have any answers to this system however. Also As mentioned
previously, I have to turn off bitmap caching to get into SBS via RDP.
Do you have any suggestions?
Regards
David Hellewell
<jimbehning@doesthisblockporkmindspring.com> wrote in message
news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt that
> is the issue. I vpn or rdp into sbs, and then get to the apps server
> all the time. I have one account that has 10 users vpning and then rdp
> into the apps server without issues. We are working totally with
> Microsoft VPN at the server and at the remote workstations.
>
> "David Hellewell" <dhellewell@ozemail.com.au> wrote:
>
> >G'Day
> >I can connect via a Draytek 2600 Router remotely via VPN & run RDP to SBS
if
> >I remove bitmap caching.
> >I cannot run RDP on the W2K Terminal Server remotely.
> >RDP runs OK in-house on all the workstations.
> >I can ping the Terminal server & SBS by ip address & name once connected
> >remotely to SBS.
> >Could this be an ISP bandwidth problem. If so how can I prove it.
> >
> >Any help would be appreciated as this has gone on for weeks now & I need
to
> >maintain the TS remotely
> >
> >Regards
> >David Hellewell
> >
>
> Jim B. SBS MVP



Re: VPN reposted - lessons learned by Alan

Alan
Tue Sep 02 21:58:46 CDT 2003

Areas where I've had similar problems (& solutions). I'm sure there can be
other problems, since I still have one user with a weird DSL connection that
exhibits the same symptoms you're describing.

1) Recently I had to change my own (remote)VPN connection (which had been
working for years) to regain RDP capability. Go to the VPN connection,
Networking tab, TCPIP Properties, Advanced, and then check the box called
"Use default gateway on remote network". I think one of the recent Security
fixes or Service Packs changed this behavior.

2) One remote user had installed Norton Internet Security, whose firewall
properties excluded my internal network. So that user was able to VPN
(because that uses the external IP), but then was unable to RDP inside the
network at all. I added the SBS internal IP range to his list of "trusted
computers".

3) Does the site that is giving you problems have a different IP scheme than
all the ones that work? In one case, the remote user's local IP addresses
(part of a home network) duplicated the SBS address space, so we had to
change the user's local IP address scheme.

4) If your home system is Win9x or WinMe, it helps a lot to have a local
userid/password identical to one on the domain you're trying to reach.
WinXP doesn't seem to have this quirk.

5) Also, it helps to put your home system on a workgroup with the same
domain name as the one you're trying to reach. Again, WinXP doesn't seem to
have this quirk.

6) It is critical that the computer name of your home system not be a
duplicate of any computer or user name on the system you're trying to reach.



"David Hellewell" <dhellewell@ozemail.com.au> wrote in message
news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> Thamks for your reply,
> I also have other sites that I VPN & RDP into SBS, then get into the apps
> server with no problems.
> I do not have any answers to this system however. Also As mentioned
> previously, I have to turn off bitmap caching to get into SBS via RDP.
> Do you have any suggestions?
> Regards
> David Hellewell
> <jimbehning@doesthisblockporkmindspring.com> wrote in message
> news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt that
> > is the issue. I vpn or rdp into sbs, and then get to the apps server
> > all the time. I have one account that has 10 users vpning and then rdp
> > into the apps server without issues. We are working totally with
> > Microsoft VPN at the server and at the remote workstations.
> >
> > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> >
> > >G'Day
> > >I can connect via a Draytek 2600 Router remotely via VPN & run RDP to
SBS
> if
> > >I remove bitmap caching.
> > >I cannot run RDP on the W2K Terminal Server remotely.
> > >RDP runs OK in-house on all the workstations.
> > >I can ping the Terminal server & SBS by ip address & name once
connected
> > >remotely to SBS.
> > >Could this be an ISP bandwidth problem. If so how can I prove it.
> > >
> > >Any help would be appreciated as this has gone on for weeks now & I
need
> to
> > >maintain the TS remotely
> > >
> > >Regards
> > >David Hellewell
> > >
> >
> > Jim B. SBS MVP
>
>



Re: VPN reposted - lessons learned by David

David
Tue Sep 02 23:14:44 CDT 2003

Thanx for your reply.
As already mentioned, I can vpn & RDP to SBS but not the W2K terminal server
connected to the SBS network.

See below the answers
Regards
David Hellewell
"Alan" <nospam@home.com> wrote in message
news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> Areas where I've had similar problems (& solutions). I'm sure there can
be
> other problems, since I still have one user with a weird DSL connection
that
> exhibits the same symptoms you're describing.
>
> 1) Recently I had to change my own (remote)VPN connection (which had been
> working for years) to regain RDP capability. Go to the VPN connection,
> Networking tab, TCPIP Properties, Advanced, and then check the box called
> "Use default gateway on remote network". I think one of the recent
Security
> fixes or Service Packs changed this behavior.
>
This box is checked

> 2) One remote user had installed Norton Internet Security, whose firewall
> properties excluded my internal network. So that user was able to VPN
> (because that uses the external IP), but then was unable to RDP inside the
> network at all. I added the SBS internal IP range to his list of "trusted
> computers".
>
I am only using ISA firewall.

> 3) Does the site that is giving you problems have a different IP scheme
than
> all the ones that work? In one case, the remote user's local IP addresses
> (part of a home network) duplicated the SBS address space, so we had to
> change the user's local IP address scheme.
>
Yes
Internal 10.0.0.x
External 192.168.16.x

> 4) If your home system is Win9x or WinMe, it helps a lot to have a local
> userid/password identical to one on the domain you're trying to reach.
> WinXP doesn't seem to have this quirk.
>
I have used WinXP home & Pro same problems. Also used dialup & ADSL, same
results from home.

> 5) Also, it helps to put your home system on a workgroup with the same
> domain name as the one you're trying to reach. Again, WinXP doesn't seem
to
> have this quirk.
>
> 6) It is critical that the computer name of your home system not be a
> duplicate of any computer or user name on the system you're trying to
reach.
>
The computer name at home does not appear on the SBS.

>
>
> "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > Thamks for your reply,
> > I also have other sites that I VPN & RDP into SBS, then get into the
apps
> > server with no problems.
> > I do not have any answers to this system however. Also As mentioned
> > previously, I have to turn off bitmap caching to get into SBS via RDP.
> > Do you have any suggestions?
> > Regards
> > David Hellewell
> > <jimbehning@doesthisblockporkmindspring.com> wrote in message
> > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt that
> > > is the issue. I vpn or rdp into sbs, and then get to the apps server
> > > all the time. I have one account that has 10 users vpning and then rdp
> > > into the apps server without issues. We are working totally with
> > > Microsoft VPN at the server and at the remote workstations.
> > >
> > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > >
> > > >G'Day
> > > >I can connect via a Draytek 2600 Router remotely via VPN & run RDP to
> SBS
> > if
> > > >I remove bitmap caching.
> > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > >RDP runs OK in-house on all the workstations.
> > > >I can ping the Terminal server & SBS by ip address & name once
> connected
> > > >remotely to SBS.
> > > >Could this be an ISP bandwidth problem. If so how can I prove it.
> > > >
> > > >Any help would be appreciated as this has gone on for weeks now & I
> need
> > to
> > > >maintain the TS remotely
> > > >
> > > >Regards
> > > >David Hellewell
> > > >
> > >
> > > Jim B. SBS MVP
> >
> >
>
>



Re: VPN reposted - lessons learned by David

David
Wed Sep 03 20:42:49 CDT 2003

Alan,
Thanx again for your reply.
Answers below
Regards
David Hellewell
"Alan" <nospam@home.com> wrote in message
news:uzYc9QocDHA.1656@TK2MSFTNGP10.phx.gbl...
> a) When you RDP to SBS, are you using the internal address or the external
> address? <<if it is the external address, then the internal networking
> /firewall / routing might be the issue>>. Make sure you can RDP to the
> internal SBS address (10.0.0.2)
Internal Address or name eg sbs.myserver.local
>
> b) What is the IP address of the home system (not the SBS network)? In
> particular, does it start with 10.0.x.x or 192.168.16.x? <<bad idea to
have
> the same address range on a remote system and the SBS system>>
> 192.168.1.10
> c) Can your home system map to a drive on the W2K terminal server and also
> to a drive on the SBS? << tells us if the VPN is really working>>
> Will try later - need to remeber how - netuse something.
> d) Are you using the same userid/password when you internally access the
W2K
> terminal server as when you external attempt to access it? Terminal
servers
Yes - Administrator
> do have their own security settings separate from the normal SBS security
> settings, but this would be the same regardless of internal vs external
> access.
No
>
> e) If the routing table is the problem, see
>
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Proxy_client.html
> This article, though slightly off topic, shows how to decode the routing
> table. Suggest you compare the working routing table with the non-working
> routing table.
> Will look at this later
>
>
>
> "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> news:XUd5b.39$vQ1.3882@nnrp1.ozemail.com.au...
> > Thanx for your reply.
> > As already mentioned, I can vpn & RDP to SBS but not the W2K terminal
> server
> > connected to the SBS network.
> >
> > See below the answers
> > Regards
> > David Hellewell
> > "Alan" <nospam@home.com> wrote in message
> > news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> > > Areas where I've had similar problems (& solutions). I'm sure there
can
> > be
> > > other problems, since I still have one user with a weird DSL
connection
> > that
> > > exhibits the same symptoms you're describing.
> > >
> > > 1) Recently I had to change my own (remote)VPN connection (which had
> been
> > > working for years) to regain RDP capability. Go to the VPN
connection,
> > > Networking tab, TCPIP Properties, Advanced, and then check the box
> called
> > > "Use default gateway on remote network". I think one of the recent
> > Security
> > > fixes or Service Packs changed this behavior.
> > >
> > This box is checked
> >
> > > 2) One remote user had installed Norton Internet Security, whose
> firewall
> > > properties excluded my internal network. So that user was able to VPN
> > > (because that uses the external IP), but then was unable to RDP inside
> the
> > > network at all. I added the SBS internal IP range to his list of
> "trusted
> > > computers".
> > >
> > I am only using ISA firewall.
> >
> > > 3) Does the site that is giving you problems have a different IP
scheme
> > than
> > > all the ones that work? In one case, the remote user's local IP
> addresses
> > > (part of a home network) duplicated the SBS address space, so we had
to
> > > change the user's local IP address scheme.
> > >
> > Yes
> > Internal 10.0.0.x
> > External 192.168.16.x
> >
> > > 4) If your home system is Win9x or WinMe, it helps a lot to have a
local
> > > userid/password identical to one on the domain you're trying to reach.
> > > WinXP doesn't seem to have this quirk.
> > >
> > I have used WinXP home & Pro same problems. Also used dialup & ADSL,
same
> > results from home.
> >
> > > 5) Also, it helps to put your home system on a workgroup with the same
> > > domain name as the one you're trying to reach. Again, WinXP doesn't
> seem
> > to
> > > have this quirk.
> > >
> > > 6) It is critical that the computer name of your home system not be a
> > > duplicate of any computer or user name on the system you're trying to
> > reach.
> > >
> > The computer name at home does not appear on the SBS.
> >
> > >
> > >
> > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > > > Thamks for your reply,
> > > > I also have other sites that I VPN & RDP into SBS, then get into the
> > apps
> > > > server with no problems.
> > > > I do not have any answers to this system however. Also As mentioned
> > > > previously, I have to turn off bitmap caching to get into SBS via
RDP.
> > > > Do you have any suggestions?
> > > > Regards
> > > > David Hellewell
> > > > <jimbehning@doesthisblockporkmindspring.com> wrote in message
> > > > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > > > RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt
> that
> > > > > is the issue. I vpn or rdp into sbs, and then get to the apps
server
> > > > > all the time. I have one account that has 10 users vpning and then
> rdp
> > > > > into the apps server without issues. We are working totally with
> > > > > Microsoft VPN at the server and at the remote workstations.
> > > > >
> > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > > > >
> > > > > >G'Day
> > > > > >I can connect via a Draytek 2600 Router remotely via VPN & run
RDP
> to
> > > SBS
> > > > if
> > > > > >I remove bitmap caching.
> > > > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > > > >RDP runs OK in-house on all the workstations.
> > > > > >I can ping the Terminal server & SBS by ip address & name once
> > > connected
> > > > > >remotely to SBS.
> > > > > >Could this be an ISP bandwidth problem. If so how can I prove
it.
> > > > > >
> > > > > >Any help would be appreciated as this has gone on for weeks now &
I
> > > need
> > > > to
> > > > > >maintain the TS remotely
> > > > > >
> > > > > >Regards
> > > > > >David Hellewell
> > > > > >
> > > > >
> > > > > Jim B. SBS MVP
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: VPN reposted - lessons learned by David

David
Thu Sep 04 22:12:48 CDT 2003

Alan,
Thanks again.
I have all internal clients connected to Terminal Server via RDP without any
problems & can remotely RDP into SBS OK. Its only RDP into Terminal Server
remotely where I have the problem.
Whilst in SBS remotely via VPN/RDP I can map folders in the Terminal Folder
OK.
Regards
David Hellewell
"Alan" <nospam@home.com> wrote in message
news:ehVfSk0cDHA.560@TK2MSFTNGP11.phx.gbl...
> The first article is very thorough and most likely to lead you in the
right
> direction.
>
> 1) Troubleshooting RDP Client Connection problems
> http://support.microsoft.com/default.aspx?scid=kb;en-us;186645
>
> 2) Solving the mystery of the VPN/RAS/Web Proxy Client
>
>
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Proxy_client.html
>
> 3) How to Troubleshoot TCP/IP Connectivity with Windows XP
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
>
>
> "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> news:XUd5b.39$vQ1.3882@nnrp1.ozemail.com.au...
> > Thanx for your reply.
> > As already mentioned, I can vpn & RDP to SBS but not the W2K terminal
> server
> > connected to the SBS network.
> >
> > See below the answers
> > Regards
> > David Hellewell
> > "Alan" <nospam@home.com> wrote in message
> > news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> > > Areas where I've had similar problems (& solutions). I'm sure there
can
> > be
> > > other problems, since I still have one user with a weird DSL
connection
> > that
> > > exhibits the same symptoms you're describing.
> > >
> > > 1) Recently I had to change my own (remote)VPN connection (which had
> been
> > > working for years) to regain RDP capability. Go to the VPN
connection,
> > > Networking tab, TCPIP Properties, Advanced, and then check the box
> called
> > > "Use default gateway on remote network". I think one of the recent
> > Security
> > > fixes or Service Packs changed this behavior.
> > >
> > This box is checked
> >
> > > 2) One remote user had installed Norton Internet Security, whose
> firewall
> > > properties excluded my internal network. So that user was able to VPN
> > > (because that uses the external IP), but then was unable to RDP inside
> the
> > > network at all. I added the SBS internal IP range to his list of
> "trusted
> > > computers".
> > >
> > I am only using ISA firewall.
> >
> > > 3) Does the site that is giving you problems have a different IP
scheme
> > than
> > > all the ones that work? In one case, the remote user's local IP
> addresses
> > > (part of a home network) duplicated the SBS address space, so we had
to
> > > change the user's local IP address scheme.
> > >
> > Yes
> > Internal 10.0.0.x
> > External 192.168.16.x
> >
> > > 4) If your home system is Win9x or WinMe, it helps a lot to have a
local
> > > userid/password identical to one on the domain you're trying to reach.
> > > WinXP doesn't seem to have this quirk.
> > >
> > I have used WinXP home & Pro same problems. Also used dialup & ADSL,
same
> > results from home.
> >
> > > 5) Also, it helps to put your home system on a workgroup with the same
> > > domain name as the one you're trying to reach. Again, WinXP doesn't
> seem
> > to
> > > have this quirk.
> > >
> > > 6) It is critical that the computer name of your home system not be a
> > > duplicate of any computer or user name on the system you're trying to
> > reach.
> > >
> > The computer name at home does not appear on the SBS.
> >
> > >
> > >
> > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > > > Thamks for your reply,
> > > > I also have other sites that I VPN & RDP into SBS, then get into the
> > apps
> > > > server with no problems.
> > > > I do not have any answers to this system however. Also As mentioned
> > > > previously, I have to turn off bitmap caching to get into SBS via
RDP.
> > > > Do you have any suggestions?
> > > > Regards
> > > > David Hellewell
> > > > <jimbehning@doesthisblockporkmindspring.com> wrote in message
> > > > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > > > RDP can run inside of a vpn tunnel, even a slow tunnel so I doubt
> that
> > > > > is the issue. I vpn or rdp into sbs, and then get to the apps
server
> > > > > all the time. I have one account that has 10 users vpning and then
> rdp
> > > > > into the apps server without issues. We are working totally with
> > > > > Microsoft VPN at the server and at the remote workstations.
> > > > >
> > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > > > >
> > > > > >G'Day
> > > > > >I can connect via a Draytek 2600 Router remotely via VPN & run
RDP
> to
> > > SBS
> > > > if
> > > > > >I remove bitmap caching.
> > > > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > > > >RDP runs OK in-house on all the workstations.
> > > > > >I can ping the Terminal server & SBS by ip address & name once
> > > connected
> > > > > >remotely to SBS.
> > > > > >Could this be an ISP bandwidth problem. If so how can I prove
it.
> > > > > >
> > > > > >Any help would be appreciated as this has gone on for weeks now &
I
> > > need
> > > > to
> > > > > >maintain the TS remotely
> > > > > >
> > > > > >Regards
> > > > > >David Hellewell
> > > > > >
> > > > >
> > > > > Jim B. SBS MVP
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: VPN reposted - lessons learned by David

David
Tue Sep 09 00:50:46 CDT 2003

Alan Thanks for your reply,
I have solve the problem by swapping routers Daytek Vigor 2600. I haven't a
clue why, the router I swapped was from my home system which is the same but
an earlier firmware level. The problem router had the same firmware level
as my other clients so don't know - exactly same settings.
Regards
David Hellewell
"Alan" <nospam@home.com> wrote in message
news:uj2MHhodDHA.3248@tk2msftngp13.phx.gbl...
> Sorry for the long absence. My paying job gets in the way of my hobbies
> sometimes.
>
> When I net view \\sbs or \\ts from home, I get System error 5 -- access is
> denied. Yet Remote Desktop works great. So that must not be required.
> Interesting that you get error 53 on the working SBS -- that indicates the
> wrong name for the server
>
> Can you RDP into the TS by just giving it the IP instead of the name?
>
> 5 questions to split this problem up:
>
> Once you have established the VPN,
> 1) What response do you get from "ping sbs" within a DOS window (where
sbs
> is the name of your server)?
> My working system responds with a ping from 10.0.0.2
>
> 2) What response do you get from "ping ts" within a DOS window?
> My working system responds with a ping from 10.0.0.80 (which is the
> correct address for my network)
>
> 3) What response do you get from "telnet sbs 3389" within a DOS window?
> My working system clears the screen and waits for additional input
>
> 4) What response do you get from "telnet ts 3389" within a DOS window?
> My working system clears the screen and waits for additional input
>
> 5) Is the answer from #2 the right address? Repeat "ping ts" from your
sbs
> to be sure it's the right IP. One time I had trouble with DNS getting out
> of sync, and I got a different address from "ping ts.yourdomainname.local"
>
>
> Basically, questions 1 & 2 (& 5) tell us if DNS is configured correctly
for
> the VPN
>
> Questions 3 & 4 tell us if there is a firewall issue
>
> Your earlier tests have ruled out almost everything else.
>
> "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> news:gST5b.437$vQ1.31865@nnrp1.ozemail.com.au...
> > Alan,
> > If I net view \\sbs or \\ts on my working clients once I have VPN
> > connected, it shows the share names.
> >
> > If I net view \\sbs on the failing system then I get the following error
> > even though I can RDP into SBS -
> > System error 53 - The network path was not found
> >
> > If I net view \\ts on the failing system I get the following error -
> > System error 5 - Access is denied
> >
> > Is there something there taht might help solve the problem?
> >
> > Regards
> > David Hellewell
> > "Alan" <nospam@home.com> wrote in message
> > news:ehVfSk0cDHA.560@TK2MSFTNGP11.phx.gbl...
> > > The first article is very thorough and most likely to lead you in the
> > right
> > > direction.
> > >
> > > 1) Troubleshooting RDP Client Connection problems
> > >
http://support.microsoft.com/default.aspx?scid=kb;en-us;186645
> > >
> > > 2) Solving the mystery of the VPN/RAS/Web Proxy Client
> > >
> > >
> >
>
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Proxy_client.html
> > >
> > > 3) How to Troubleshoot TCP/IP Connectivity with Windows XP
> > > http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
> > >
> > >
> > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > news:XUd5b.39$vQ1.3882@nnrp1.ozemail.com.au...
> > > > Thanx for your reply.
> > > > As already mentioned, I can vpn & RDP to SBS but not the W2K
terminal
> > > server
> > > > connected to the SBS network.
> > > >
> > > > See below the answers
> > > > Regards
> > > > David Hellewell
> > > > "Alan" <nospam@home.com> wrote in message
> > > > news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> > > > > Areas where I've had similar problems (& solutions). I'm sure
there
> > can
> > > > be
> > > > > other problems, since I still have one user with a weird DSL
> > connection
> > > > that
> > > > > exhibits the same symptoms you're describing.
> > > > >
> > > > > 1) Recently I had to change my own (remote)VPN connection (which
had
> > > been
> > > > > working for years) to regain RDP capability. Go to the VPN
> > connection,
> > > > > Networking tab, TCPIP Properties, Advanced, and then check the box
> > > called
> > > > > "Use default gateway on remote network". I think one of the
recent
> > > > Security
> > > > > fixes or Service Packs changed this behavior.
> > > > >
> > > > This box is checked
> > > >
> > > > > 2) One remote user had installed Norton Internet Security, whose
> > > firewall
> > > > > properties excluded my internal network. So that user was able to
> VPN
> > > > > (because that uses the external IP), but then was unable to RDP
> inside
> > > the
> > > > > network at all. I added the SBS internal IP range to his list of
> > > "trusted
> > > > > computers".
> > > > >
> > > > I am only using ISA firewall.
> > > >
> > > > > 3) Does the site that is giving you problems have a different IP
> > scheme
> > > > than
> > > > > all the ones that work? In one case, the remote user's local IP
> > > addresses
> > > > > (part of a home network) duplicated the SBS address space, so we
> had
> > to
> > > > > change the user's local IP address scheme.
> > > > >
> > > > Yes
> > > > Internal 10.0.0.x
> > > > External 192.168.16.x
> > > >
> > > > > 4) If your home system is Win9x or WinMe, it helps a lot to have a
> > local
> > > > > userid/password identical to one on the domain you're trying to
> reach.
> > > > > WinXP doesn't seem to have this quirk.
> > > > >
> > > > I have used WinXP home & Pro same problems. Also used dialup &
ADSL,
> > same
> > > > results from home.
> > > >
> > > > > 5) Also, it helps to put your home system on a workgroup with the
> same
> > > > > domain name as the one you're trying to reach. Again, WinXP
doesn't
> > > seem
> > > > to
> > > > > have this quirk.
> > > > >
> > > > > 6) It is critical that the computer name of your home system not
be
> a
> > > > > duplicate of any computer or user name on the system you're trying
> to
> > > > reach.
> > > > >
> > > > The computer name at home does not appear on the SBS.
> > > >
> > > > >
> > > > >
> > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > > > news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > > > > > Thamks for your reply,
> > > > > > I also have other sites that I VPN & RDP into SBS, then get into
> the
> > > > apps
> > > > > > server with no problems.
> > > > > > I do not have any answers to this system however. Also As
> mentioned
> > > > > > previously, I have to turn off bitmap caching to get into SBS
via
> > RDP.
> > > > > > Do you have any suggestions?
> > > > > > Regards
> > > > > > David Hellewell
> > > > > > <jimbehning@doesthisblockporkmindspring.com> wrote in message
> > > > > > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > > > > > RDP can run inside of a vpn tunnel, even a slow tunnel so I
> doubt
> > > that
> > > > > > > is the issue. I vpn or rdp into sbs, and then get to the apps
> > server
> > > > > > > all the time. I have one account that has 10 users vpning and
> then
> > > rdp
> > > > > > > into the apps server without issues. We are working totally
with
> > > > > > > Microsoft VPN at the server and at the remote workstations.
> > > > > > >
> > > > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > > > > > >
> > > > > > > >G'Day
> > > > > > > >I can connect via a Draytek 2600 Router remotely via VPN &
run
> > RDP
> > > to
> > > > > SBS
> > > > > > if
> > > > > > > >I remove bitmap caching.
> > > > > > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > > > > > >RDP runs OK in-house on all the workstations.
> > > > > > > >I can ping the Terminal server & SBS by ip address & name
once
> > > > > connected
> > > > > > > >remotely to SBS.
> > > > > > > >Could this be an ISP bandwidth problem. If so how can I
prove
> > it.
> > > > > > > >
> > > > > > > >Any help would be appreciated as this has gone on for weeks
now
> &
> > I
> > > > > need
> > > > > > to
> > > > > > > >maintain the TS remotely
> > > > > > > >
> > > > > > > >Regards
> > > > > > > >David Hellewell
> > > > > > > >
> > > > > > >
> > > > > > > Jim B. SBS MVP
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: VPN reposted - lessons learned by Marina

Marina
Tue Sep 09 05:40:56 CDT 2003

Hi David,

Just out of curiousity: Which firmware level did it have? And which level
did work?

Marina

"David Hellewell" <dhellewell@ozemail.com.au> schreef in bericht
news:XSd7b.1344$vQ1.81092@nnrp1.ozemail.com.au...
> Alan Thanks for your reply,
> I have solve the problem by swapping routers Daytek Vigor 2600. I haven't
a
> clue why, the router I swapped was from my home system which is the same
but
> an earlier firmware level. The problem router had the same firmware level
> as my other clients so don't know - exactly same settings.
> Regards
> David Hellewell
> "Alan" <nospam@home.com> wrote in message
> news:uj2MHhodDHA.3248@tk2msftngp13.phx.gbl...
> > Sorry for the long absence. My paying job gets in the way of my hobbies
> > sometimes.
> >
> > When I net view \\sbs or \\ts from home, I get System error 5 -- access
is
> > denied. Yet Remote Desktop works great. So that must not be required.
> > Interesting that you get error 53 on the working SBS -- that indicates
the
> > wrong name for the server
> >
> > Can you RDP into the TS by just giving it the IP instead of the name?
> >
> > 5 questions to split this problem up:
> >
> > Once you have established the VPN,
> > 1) What response do you get from "ping sbs" within a DOS window (where
> sbs
> > is the name of your server)?
> > My working system responds with a ping from 10.0.0.2
> >
> > 2) What response do you get from "ping ts" within a DOS window?
> > My working system responds with a ping from 10.0.0.80 (which is
the
> > correct address for my network)
> >
> > 3) What response do you get from "telnet sbs 3389" within a DOS window?
> > My working system clears the screen and waits for additional input
> >
> > 4) What response do you get from "telnet ts 3389" within a DOS window?
> > My working system clears the screen and waits for additional input
> >
> > 5) Is the answer from #2 the right address? Repeat "ping ts" from your
> sbs
> > to be sure it's the right IP. One time I had trouble with DNS getting
out
> > of sync, and I got a different address from "ping
ts.yourdomainname.local"
> >
> >
> > Basically, questions 1 & 2 (& 5) tell us if DNS is configured correctly
> for
> > the VPN
> >
> > Questions 3 & 4 tell us if there is a firewall issue
> >
> > Your earlier tests have ruled out almost everything else.
> >
> > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > news:gST5b.437$vQ1.31865@nnrp1.ozemail.com.au...
> > > Alan,
> > > If I net view \\sbs or \\ts on my working clients once I have VPN
> > > connected, it shows the share names.
> > >
> > > If I net view \\sbs on the failing system then I get the following
error
> > > even though I can RDP into SBS -
> > > System error 53 - The network path was not found
> > >
> > > If I net view \\ts on the failing system I get the following error -
> > > System error 5 - Access is denied
> > >
> > > Is there something there taht might help solve the problem?
> > >
> > > Regards
> > > David Hellewell
> > > "Alan" <nospam@home.com> wrote in message
> > > news:ehVfSk0cDHA.560@TK2MSFTNGP11.phx.gbl...
> > > > The first article is very thorough and most likely to lead you in
the
> > > right
> > > > direction.
> > > >
> > > > 1) Troubleshooting RDP Client Connection problems
> > > >
> http://support.microsoft.com/default.aspx?scid=kb;en-us;186645
> > > >
> > > > 2) Solving the mystery of the VPN/RAS/Web Proxy Client
> > > >
> > > >
> > >
> >
>
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Prox
y_client.html
> > > >
> > > > 3) How to Troubleshoot TCP/IP Connectivity with Windows XP
> > > >
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
> > > >
> > > >
> > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > > news:XUd5b.39$vQ1.3882@nnrp1.ozemail.com.au...
> > > > > Thanx for your reply.
> > > > > As already mentioned, I can vpn & RDP to SBS but not the W2K
> terminal
> > > > server
> > > > > connected to the SBS network.
> > > > >
> > > > > See below the answers
> > > > > Regards
> > > > > David Hellewell
> > > > > "Alan" <nospam@home.com> wrote in message
> > > > > news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> > > > > > Areas where I've had similar problems (& solutions). I'm sure
> there
> > > can
> > > > > be
> > > > > > other problems, since I still have one user with a weird DSL
> > > connection
> > > > > that
> > > > > > exhibits the same symptoms you're describing.
> > > > > >
> > > > > > 1) Recently I had to change my own (remote)VPN connection (which
> had
> > > > been
> > > > > > working for years) to regain RDP capability. Go to the VPN
> > > connection,
> > > > > > Networking tab, TCPIP Properties, Advanced, and then check the
box
> > > > called
> > > > > > "Use default gateway on remote network". I think one of the
> recent
> > > > > Security
> > > > > > fixes or Service Packs changed this behavior.
> > > > > >
> > > > > This box is checked
> > > > >
> > > > > > 2) One remote user had installed Norton Internet Security, whose
> > > > firewall
> > > > > > properties excluded my internal network. So that user was able
to
> > VPN
> > > > > > (because that uses the external IP), but then was unable to RDP
> > inside
> > > > the
> > > > > > network at all. I added the SBS internal IP range to his list
of
> > > > "trusted
> > > > > > computers".
> > > > > >
> > > > > I am only using ISA firewall.
> > > > >
> > > > > > 3) Does the site that is giving you problems have a different IP
> > > scheme
> > > > > than
> > > > > > all the ones that work? In one case, the remote user's local IP
> > > > addresses
> > > > > > (part of a home network) duplicated the SBS address space, so
we
> > had
> > > to
> > > > > > change the user's local IP address scheme.
> > > > > >
> > > > > Yes
> > > > > Internal 10.0.0.x
> > > > > External 192.168.16.x
> > > > >
> > > > > > 4) If your home system is Win9x or WinMe, it helps a lot to have
a
> > > local
> > > > > > userid/password identical to one on the domain you're trying to
> > reach.
> > > > > > WinXP doesn't seem to have this quirk.
> > > > > >
> > > > > I have used WinXP home & Pro same problems. Also used dialup &
> ADSL,
> > > same
> > > > > results from home.
> > > > >
> > > > > > 5) Also, it helps to put your home system on a workgroup with
the
> > same
> > > > > > domain name as the one you're trying to reach. Again, WinXP
> doesn't
> > > > seem
> > > > > to
> > > > > > have this quirk.
> > > > > >
> > > > > > 6) It is critical that the computer name of your home system not
> be
> > a
> > > > > > duplicate of any computer or user name on the system you're
trying
> > to
> > > > > reach.
> > > > > >
> > > > > The computer name at home does not appear on the SBS.
> > > > >
> > > > > >
> > > > > >
> > > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > > > > news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > > > > > > Thamks for your reply,
> > > > > > > I also have other sites that I VPN & RDP into SBS, then get
into
> > the
> > > > > apps
> > > > > > > server with no problems.
> > > > > > > I do not have any answers to this system however. Also As
> > mentioned
> > > > > > > previously, I have to turn off bitmap caching to get into SBS
> via
> > > RDP.
> > > > > > > Do you have any suggestions?
> > > > > > > Regards
> > > > > > > David Hellewell
> > > > > > > <jimbehning@doesthisblockporkmindspring.com> wrote in message
> > > > > > > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > > > > > > RDP can run inside of a vpn tunnel, even a slow tunnel so I
> > doubt
> > > > that
> > > > > > > > is the issue. I vpn or rdp into sbs, and then get to the
apps
> > > server
> > > > > > > > all the time. I have one account that has 10 users vpning
and
> > then
> > > > rdp
> > > > > > > > into the apps server without issues. We are working totally
> with
> > > > > > > > Microsoft VPN at the server and at the remote workstations.
> > > > > > > >
> > > > > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > > > > > > >
> > > > > > > > >G'Day
> > > > > > > > >I can connect via a Draytek 2600 Router remotely via VPN &
> run
> > > RDP
> > > > to
> > > > > > SBS
> > > > > > > if
> > > > > > > > >I remove bitmap caching.
> > > > > > > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > > > > > > >RDP runs OK in-house on all the workstations.
> > > > > > > > >I can ping the Terminal server & SBS by ip address & name
> once
> > > > > > connected
> > > > > > > > >remotely to SBS.
> > > > > > > > >Could this be an ISP bandwidth problem. If so how can I
> prove
> > > it.
> > > > > > > > >
> > > > > > > > >Any help would be appreciated as this has gone on for weeks
> now
> > &
> > > I
> > > > > > need
> > > > > > > to
> > > > > > > > >maintain the TS remotely
> > > > > > > > >
> > > > > > > > >Regards
> > > > > > > > >David Hellewell
> > > > > > > > >
> > > > > > > >
> > > > > > > > Jim B. SBS MVP
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: VPN reposted - lessons learned by David

David
Tue Sep 09 14:25:19 CDT 2003

G'day Marina,
The Firmware it had was V2.3.6_AU
It now has V2.3.2_AU
Regards
David Hellewell
"Marina Roos" <marina@roos.nodontwantspam.nl.com> wrote in message
news:Y6i7b.98172$506.99802@typhoon.bart.nl...
> Hi David,
>
> Just out of curiousity: Which firmware level did it have? And which level
> did work?
>
> Marina
>
> "David Hellewell" <dhellewell@ozemail.com.au> schreef in bericht
> news:XSd7b.1344$vQ1.81092@nnrp1.ozemail.com.au...
> > Alan Thanks for your reply,
> > I have solve the problem by swapping routers Daytek Vigor 2600. I
haven't
> a
> > clue why, the router I swapped was from my home system which is the same
> but
> > an earlier firmware level. The problem router had the same firmware
level
> > as my other clients so don't know - exactly same settings.
> > Regards
> > David Hellewell
> > "Alan" <nospam@home.com> wrote in message
> > news:uj2MHhodDHA.3248@tk2msftngp13.phx.gbl...
> > > Sorry for the long absence. My paying job gets in the way of my
hobbies
> > > sometimes.
> > >
> > > When I net view \\sbs or \\ts from home, I get System error 5 --
access
> is
> > > denied. Yet Remote Desktop works great. So that must not be
required.
> > > Interesting that you get error 53 on the working SBS -- that indicates
> the
> > > wrong name for the server
> > >
> > > Can you RDP into the TS by just giving it the IP instead of the name?
> > >
> > > 5 questions to split this problem up:
> > >
> > > Once you have established the VPN,
> > > 1) What response do you get from "ping sbs" within a DOS window
(where
> > sbs
> > > is the name of your server)?
> > > My working system responds with a ping from 10.0.0.2
> > >
> > > 2) What response do you get from "ping ts" within a DOS window?
> > > My working system responds with a ping from 10.0.0.80 (which is
> the
> > > correct address for my network)
> > >
> > > 3) What response do you get from "telnet sbs 3389" within a DOS
window?
> > > My working system clears the screen and waits for additional
input
> > >
> > > 4) What response do you get from "telnet ts 3389" within a DOS window?
> > > My working system clears the screen and waits for additional
input
> > >
> > > 5) Is the answer from #2 the right address? Repeat "ping ts" from
your
> > sbs
> > > to be sure it's the right IP. One time I had trouble with DNS getting
> out
> > > of sync, and I got a different address from "ping
> ts.yourdomainname.local"
> > >
> > >
> > > Basically, questions 1 & 2 (& 5) tell us if DNS is configured
correctly
> > for
> > > the VPN
> > >
> > > Questions 3 & 4 tell us if there is a firewall issue
> > >
> > > Your earlier tests have ruled out almost everything else.
> > >
> > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > news:gST5b.437$vQ1.31865@nnrp1.ozemail.com.au...
> > > > Alan,
> > > > If I net view \\sbs or \\ts on my working clients once I have VPN
> > > > connected, it shows the share names.
> > > >
> > > > If I net view \\sbs on the failing system then I get the following
> error
> > > > even though I can RDP into SBS -
> > > > System error 53 - The network path was not found
> > > >
> > > > If I net view \\ts on the failing system I get the following error -
> > > > System error 5 - Access is denied
> > > >
> > > > Is there something there taht might help solve the problem?
> > > >
> > > > Regards
> > > > David Hellewell
> > > > "Alan" <nospam@home.com> wrote in message
> > > > news:ehVfSk0cDHA.560@TK2MSFTNGP11.phx.gbl...
> > > > > The first article is very thorough and most likely to lead you in
> the
> > > > right
> > > > > direction.
> > > > >
> > > > > 1) Troubleshooting RDP Client Connection problems
> > > > >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;186645
> > > > >
> > > > > 2) Solving the mystery of the VPN/RAS/Web Proxy Client
> > > > >
> > > > >
> > > >
> > >
> >
>
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Prox
> y_client.html
> > > > >
> > > > > 3) How to Troubleshoot TCP/IP Connectivity with Windows XP
> > > > >
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;314067
> > > > >
> > > > >
> > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > > > news:XUd5b.39$vQ1.3882@nnrp1.ozemail.com.au...
> > > > > > Thanx for your reply.
> > > > > > As already mentioned, I can vpn & RDP to SBS but not the W2K
> > terminal
> > > > > server
> > > > > > connected to the SBS network.
> > > > > >
> > > > > > See below the answers
> > > > > > Regards
> > > > > > David Hellewell
> > > > > > "Alan" <nospam@home.com> wrote in message
> > > > > > news:OD7C$cccDHA.2436@TK2MSFTNGP12.phx.gbl...
> > > > > > > Areas where I've had similar problems (& solutions). I'm sure
> > there
> > > > can
> > > > > > be
> > > > > > > other problems, since I still have one user with a weird DSL
> > > > connection
> > > > > > that
> > > > > > > exhibits the same symptoms you're describing.
> > > > > > >
> > > > > > > 1) Recently I had to change my own (remote)VPN connection
(which
> > had
> > > > > been
> > > > > > > working for years) to regain RDP capability. Go to the VPN
> > > > connection,
> > > > > > > Networking tab, TCPIP Properties, Advanced, and then check the
> box
> > > > > called
> > > > > > > "Use default gateway on remote network". I think one of the
> > recent
> > > > > > Security
> > > > > > > fixes or Service Packs changed this behavior.
> > > > > > >
> > > > > > This box is checked
> > > > > >
> > > > > > > 2) One remote user had installed Norton Internet Security,
whose
> > > > > firewall
> > > > > > > properties excluded my internal network. So that user was
able
> to
> > > VPN
> > > > > > > (because that uses the external IP), but then was unable to
RDP
> > > inside
> > > > > the
> > > > > > > network at all. I added the SBS internal IP range to his list
> of
> > > > > "trusted
> > > > > > > computers".
> > > > > > >
> > > > > > I am only using ISA firewall.
> > > > > >
> > > > > > > 3) Does the site that is giving you problems have a different
IP
> > > > scheme
> > > > > > than
> > > > > > > all the ones that work? In one case, the remote user's local
IP
> > > > > addresses
> > > > > > > (part of a home network) duplicated the SBS address space, so
> we
> > > had
> > > > to
> > > > > > > change the user's local IP address scheme.
> > > > > > >
> > > > > > Yes
> > > > > > Internal 10.0.0.x
> > > > > > External 192.168.16.x
> > > > > >
> > > > > > > 4) If your home system is Win9x or WinMe, it helps a lot to
have
> a
> > > > local
> > > > > > > userid/password identical to one on the domain you're trying
to
> > > reach.
> > > > > > > WinXP doesn't seem to have this quirk.
> > > > > > >
> > > > > > I have used WinXP home & Pro same problems. Also used dialup &
> > ADSL,
> > > > same
> > > > > > results from home.
> > > > > >
> > > > > > > 5) Also, it helps to put your home system on a workgroup with
> the
> > > same
> > > > > > > domain name as the one you're trying to reach. Again, WinXP
> > doesn't
> > > > > seem
> > > > > > to
> > > > > > > have this quirk.
> > > > > > >
> > > > > > > 6) It is critical that the computer name of your home system
not
> > be
> > > a
> > > > > > > duplicate of any computer or user name on the system you're
> trying
> > > to
> > > > > > reach.
> > > > > > >
> > > > > > The computer name at home does not appear on the SBS.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote in message
> > > > > > > news:GKS4b.28$dR.2242@nnrp1.ozemail.com.au...
> > > > > > > > Thamks for your reply,
> > > > > > > > I also have other sites that I VPN & RDP into SBS, then get
> into
> > > the
> > > > > > apps
> > > > > > > > server with no problems.
> > > > > > > > I do not have any answers to this system however. Also As
> > > mentioned
> > > > > > > > previously, I have to turn off bitmap caching to get into
SBS
> > via
> > > > RDP.
> > > > > > > > Do you have any suggestions?
> > > > > > > > Regards
> > > > > > > > David Hellewell
> > > > > > > > <jimbehning@doesthisblockporkmindspring.com> wrote in
message
> > > > > > > > news:8ir7lvs42niqfbde6kk4u9hruuejr4ppg8@4ax.com...
> > > > > > > > > RDP can run inside of a vpn tunnel, even a slow tunnel so
I
> > > doubt
> > > > > that
> > > > > > > > > is the issue. I vpn or rdp into sbs, and then get to the
> apps
> > > > server
> > > > > > > > > all the time. I have one account that has 10 users vpning
> and
> > > then
> > > > > rdp
> > > > > > > > > into the apps server without issues. We are working
totally
> > with
> > > > > > > > > Microsoft VPN at the server and at the remote
workstations.
> > > > > > > > >
> > > > > > > > > "David Hellewell" <dhellewell@ozemail.com.au> wrote:
> > > > > > > > >
> > > > > > > > > >G'Day
> > > > > > > > > >I can connect via a Draytek 2600 Router remotely via VPN
&
> > run
> > > > RDP
> > > > > to
> > > > > > > SBS
> > > > > > > > if
> > > > > > > > > >I remove bitmap caching.
> > > > > > > > > >I cannot run RDP on the W2K Terminal Server remotely.
> > > > > > > > > >RDP runs OK in-house on all the workstations.
> > > > > > > > > >I can ping the Terminal server & SBS by ip address & name
> > once
> > > > > > > connected
> > > > > > > > > >remotely to SBS.
> > > > > > > > > >Could this be an ISP bandwidth problem. If so how can I
> > prove
> > > > it.
> > > > > > > > > >
> > > > > > > > > >Any help would be appreciated as this has gone on for
weeks
> > now
> > > &
> > > > I
> > > > > > > need
> > > > > > > > to
> > > > > > > > > >maintain the TS remotely
> > > > > > > > > >
> > > > > > > > > >Regards
> > > > > > > > > >David Hellewell
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Jim B. SBS MVP
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>