Can connect using Remote Desktop but not Remote Desktop Web connec

[blinton25]

Hello,

I use Remote Desktop Web connection with a fixed IP to allow access to a
Windows 2003 server. Requests which come to port 3389 are forwarded to the
Windows Server 2003 machine. I can access the server either using Remote
Desktop or via the web site.

I switched my ISP and obtained a new fixed IP and new router (Linksys
WRT54G). I set up forwarding once again. However, when I try to access the
server via remote desktop web connection I received the following error:

"VBScript: Remote Session Disconnected

The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accepty new
connections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator."

I can still connect using Remote Desktop.

Any idea why this is occuring?

 

[Jiazhi Ou [MSFT]]

Are you saying that you can connect through mstsc.exe ("remote desktop
conenction") AFTER switching your ISP? Can you try "telnet servername 3389"
from your client machine to see if this is any connectivity issue?

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"blinton25" <blinton25@discussions.microsoft.com> wrote in message
news:991E5BF7-5BBD-4CB1-A94D-6E3FB370B381@microsoft.com...
> Hello,
>
> I use Remote Desktop Web connection with a fixed IP to allow access to a
> Windows 2003 server. Requests which come to port 3389 are forwarded to the
> Windows Server 2003 machine. I can access the server either using Remote
> Desktop or via the web site.
>
> I switched my ISP and obtained a new fixed IP and new router (Linksys
> WRT54G). I set up forwarding once again. However, when I try to access the
> server via remote desktop web connection I received the following error:
>
> "VBScript: Remote Session Disconnected
>
> The client could not connect to the remote computer. Remote connections
> might not be enabled or the computer might be too busy to accepty new
> connections. It is also possible that network problems are preventing your
> connection. Please try connecting again later. If the problem continues to
> occur, contact your administrator."
>
> I can still connect using Remote Desktop.
>
> Any idea why this is occuring?

 

[blinton25]

Re: Can connect using Remote Desktop but not Remote Desktop Web co

Helo,

I still had the old IP address as a hidden field in the initial page which
connects to the server. Once I changed it to the new IP I was able to
reconnect.

Thanks.



"Jiazhi Ou [MSFT]" wrote:

> Are you saying that you can connect through mstsc.exe ("remote desktop
> conenction") AFTER switching your ISP? Can you try "telnet servername 3389"
> from your client machine to see if this is any connectivity issue?
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "blinton25" <blinton25@discussions.microsoft.com> wrote in message
> news:991E5BF7-5BBD-4CB1-A94D-6E3FB370B381@microsoft.com...
> > Hello,
> >
> > I use Remote Desktop Web connection with a fixed IP to allow access to a
> > Windows 2003 server. Requests which come to port 3389 are forwarded to the
> > Windows Server 2003 machine. I can access the server either using Remote
> > Desktop or via the web site.
> >
> > I switched my ISP and obtained a new fixed IP and new router (Linksys
> > WRT54G). I set up forwarding once again. However, when I try to access the
> > server via remote desktop web connection I received the following error:
> >
> > "VBScript: Remote Session Disconnected
> >
> > The client could not connect to the remote computer. Remote connections
> > might not be enabled or the computer might be too busy to accepty new
> > connections. It is also possible that network problems are preventing your
> > connection. Please try connecting again later. If the problem continues to
> > occur, contact your administrator."
> >
> > I can still connect using Remote Desktop.
> >
> > Any idea why this is occuring?
>
>

 

[Jiazhi Ou [MSFT]]

Re: Can connect using Remote Desktop but not Remote Desktop Web co

Good to know that. Thanks for the update!

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"blinton25" <blinton25@discussions.microsoft.com> wrote in message
news:36240F10-9424-448E-9B7A-D35D54AB3D45@microsoft.com...
> Helo,
>
> I still had the old IP address as a hidden field in the initial page which
> connects to the server. Once I changed it to the new IP I was able to
> reconnect.
>
> Thanks.
>
>
>
> "Jiazhi Ou [MSFT]" wrote:
>
>> Are you saying that you can connect through mstsc.exe ("remote desktop
>> conenction") AFTER switching your ISP? Can you try "telnet servername
>> 3389"
>> from your client machine to see if this is any connectivity issue?
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "blinton25" <blinton25@discussions.microsoft.com> wrote in message
>> news:991E5BF7-5BBD-4CB1-A94D-6E3FB370B381@microsoft.com...
>> > Hello,
>> >
>> > I use Remote Desktop Web connection with a fixed IP to allow access to
>> > a
>> > Windows 2003 server. Requests which come to port 3389 are forwarded to
>> > the
>> > Windows Server 2003 machine. I can access the server either using
>> > Remote
>> > Desktop or via the web site.
>> >
>> > I switched my ISP and obtained a new fixed IP and new router (Linksys
>> > WRT54G). I set up forwarding once again. However, when I try to access
>> > the
>> > server via remote desktop web connection I received the following
>> > error:
>> >
>> > "VBScript: Remote Session Disconnected
>> >
>> > The client could not connect to the remote computer. Remote connections
>> > might not be enabled or the computer might be too busy to accepty new
>> > connections. It is also possible that network problems are preventing
>> > your
>> > connection. Please try connecting again later. If the problem continues
>> > to
>> > occur, contact your administrator."
>> >
>> > I can still connect using Remote Desktop.
>> >
>> > Any idea why this is occuring?
>>
>>