Re: not able to connect to the Terminal Server on SBS network

On May 11, 6:24 am, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Jack <j...@xxxxxxxxxxxxxx> wrote:
We have a SBS2k3 Standard (2 nic and a router) and a Terminal Server
within the domain.
We have a job site where users get on the net via satellite.
Everything was fine until the satellite internet ISP was changed - the
users on the job site are not able to connect to the terminal server
any more, while users from other remote locations are fine.

Here is the details
- Users on the job site are able to launch RWW without a problem.
(https://office.mycompany.com/remote)
- However, when they click on "Connect to my company's application-
sharing server", they get errors like below:
VBScripte: Remote Desktop Disconnected
The client could not establish a connection to the remote computer.
The most likely causes for this error are:
1) Remote connections might not be enabled at the remote computer.
2) The maximum number of connecitons might be exceeded at the remote
computer
3) A network error might have occurred while establishing the
connection.
4) The remote Web Workplace designated port might be blocked by a
firewall
- Users from other remote locations do not have this problem.

I think the new satellite ISP is blocking port 4125. But they will not
do anything or change anything, simply nothing they will do for this
problem.
Is there anything I can do from the SBS end? for example, change the
port 4125 to another one?
or you may have other solutions?

Thanks in advance

jack

Can you not just switch back to the other ISP or find another
provider/service? I have heard little good about satellite for anything
beyond basic surfing/email.

I'm not sure you *can* change the listening port, but even if you could, it
might not be the cause of the problem to begin with - unless you know
specifically what the ISP is blocking.- Hide quoted text -

- Show quoted text -

Thank you Lanwench!
Unfortunately, the job site belongs to our client, they are not
willing to change back ISP and they are not willing to look into this
issue for us. We are on our own.
I figured that the only solution would be changing the port 4125 to
something else.

good day!
.

Relevant Pages

  • Re: not able to connect to the Terminal Server on SBS network
    ... We have a job site where users get on the net via satellite. ... VBScripte: Remote Desktop Disconnected ... I think the new satellite ISP is blocking port 4125. ...
    (microsoft.public.windows.server.sbs)
  • Re: not able to connect to the Terminal Server on SBS network
    ... We have a job site where users get on the net via satellite. ... VBScripte: Remote Desktop Disconnected ... port 4125 to another one? ...
    (microsoft.public.windows.server.sbs)
  • Re: not able to connect to the Terminal Server on SBS network
    ... If port 4125 is truly being blocked by the ISP, ... We have a job site where users get on the net via satellite. ... VBScripte: Remote Desktop Disconnected ...
    (microsoft.public.windows.server.sbs)
  • Re: not able to connect to the Terminal Server on SBS network
    ... but you may have to re-run CEICW after you make the port change. ... We have a job site where users get on the net via satellite. ... Everything was fine until the satellite internet ISP was changed - the ... while users from other remote locations are fine. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Rule for Remote Desktop?
    ... Someone (isp) is probably blocking something and they do not know it. ... I've just had an opportunity to try testing Remote Desktop through RWW from ... attempts being made from the logging interface in ISA to port 4125 when I ... There are three connection ...
    (microsoft.public.windows.server.sbs)