Prev: Remote desktop disconnecting after some seconds
Next: salvage TS license
From: TrustedVolume on 28 Jan 2010 10:36
(Sorry, I also posted this earlier in the Polish forum by mistake)

Hi,

I am trying to connect to a Terminal Server with remote desktop over the web
but with no joy. If I forward a port on the firewall to any XP workstations
it does connect with remote desktop from home so I kinda eliminated the
Firewall as cause.

When I am at work and in the LAN I can remote desktop to the server with no
problem.

So yeah it doesn't make a lot of sense to me the fact that I can remote
desktop over the web to workstations but not the terminal server.

Someone please shed a bit of light?

Thx
From: RCan on 28 Jan 2010 15:58
When you can access the TS within your network without any issues then this
must be an network / routing issue here. Can u connect to any ressource of
the terminal server over the web, if this is allowed from the firewalls ? I
just want to check here if the TS traffic is routed on the same way as you
do that with your workstations. Do they use the same default gateway ?

I would strongly recommend here Windows 2008 Remote Desktop services cause
there are so many improvements made especially in TS area.

Regards
Ramazan

"TrustedVolume" <TrustedVolume(a)discussions.microsoft.com> wrote in message
news:40DDFAAA-0E44-4B13-9288-33E10B1703C9(a)microsoft.com...
> (Sorry, I also posted this earlier in the Polish forum by mistake)
>
> Hi,
>
> I am trying to connect to a Terminal Server with remote desktop over the
> web
> but with no joy. If I forward a port on the firewall to any XP
> workstations
> it does connect with remote desktop from home so I kinda eliminated the
> Firewall as cause.
>
> When I am at work and in the LAN I can remote desktop to the server with
> no
> problem.
>
> So yeah it doesn't make a lot of sense to me the fact that I can remote
> desktop over the web to workstations but not the terminal server.
>
> Someone please shed a bit of light?
>
> Thx

From: TrustedVolume on 28 Jan 2010 18:15
Think I am going to reply to both posts in one go...

@Bob Lin - You know the strange thing is that whenever I change the Firewall
port route to a normal XP workstation 3389/3390 I can telnet from the web
onto the workstation. If I do exactly the same for the server and just change
the IP address to reflect it's IP in the firewall I can't telnet and can't
see the session hitting the TS. So from that perspective I see your point.
The only 2 thing that baffles me... If I can access both the TS server and XP
workstation from within the LAN there should theoretically be no reason why
it shouldn't work from the web - given I changed the port on exactly the same
rule from the WS to the TS...

@RCan - I am going to double check the gateways etc. If I VPN in from home
and get assigned a local LAN IP from DHCP I can access the TS over the VPN
tunnel. Because we use static IP's from TS clients over the web I lock that
on the firewall. For testing purposes I use the same rule for both the XP and
TS server so I know the port routing variable is out of the way..

Thx
From: M. M�ller on 29 Jan 2010 03:07
On Thu, 28 Jan 2010 07:36:01 -0800, TrustedVolume
<TrustedVolume(a)discussions.microsoft.com> wrote:

>I am trying to connect to a Terminal Server with remote desktop over the web
>but with no joy. If I forward a port on the firewall to any XP workstations
>it does connect with remote desktop from home so I kinda eliminated the
>Firewall as cause.
>
>When I am at work and in the LAN I can remote desktop to the server with no
>problem.

Have you ever looked at the firewall rules concerning the TS? Just
comes across my mind, cause these days I enabled Remotedesktop to be
just accessible from a specific subnet. In firewall rules look for
remotedesktop and somewhere you should find a setting to adjust the
scope.

If that's not it, it might be helpful to know more about your set up
of mashines ;)

hth,

marcel
From: TrustedVolume on 29 Jan 2010 08:16
Hi Marcel,

I tried every location on the Firewall (WAN, LAN and *) but it is still the
same. If it was a very complex network the struggle would've been easier to
digest for me but the W2K3 TS is a standalone server just doing TServices. So
there isn't really much that can go wrong bar Firewall or local TS settings.
This is driving me up the wall :lol:

I've been over firewall policies/rules 300 times but to be sure to be sure I
am going to go over them once more. The only reason I don't think it is
firewall issue is because the workstations are accessible via the web using
the same rule...

Thx for the comment :)

"M. Müller" wrote:

> On Thu, 28 Jan 2010 07:36:01 -0800, TrustedVolume
> <TrustedVolume(a)discussions.microsoft.com> wrote:
>
> >I am trying to connect to a Terminal Server with remote desktop over the web
> >but with no joy. If I forward a port on the firewall to any XP workstations
> >it does connect with remote desktop from home so I kinda eliminated the
> >Firewall as cause.
> >
> >When I am at work and in the LAN I can remote desktop to the server with no
> >problem.
>
> Have you ever looked at the firewall rules concerning the TS? Just
> comes across my mind, cause these days I enabled Remotedesktop to be
> just accessible from a specific subnet. In firewall rules look for
> remotedesktop and somewhere you should find a setting to adjust the
> scope.
>
> If that's not it, it might be helpful to know more about your set up
> of mashines ;)
>
> hth,
>
> marcel
> .
>
 |  Next  |  Last
Pages: 1 2
Prev: Remote desktop disconnecting after some seconds
Next: salvage TS license