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

On May 11, 6:50 am, "Merv Porter [SBS-MVP]"
<mwport@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Jack,

If port 4125 is truly being blocked by the ISP, you can change that default
RWW port to something else:

HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal

Change the Port key to another port number (maybe in the 5000 or 6000
range).

--
Merv  Porter   [SBS-MVP]
============================

"Jack" <j...@xxxxxxxxxxxxxx> wrote in message

news:c7417321-8bfc-4094-96f6-de2359286f7b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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- Hide quoted text -

- Show quoted text -

Thank you Merv!
I am having some challenges changing the port 4125
- How can I detect which ports are not blocked from job site?
Do you know any efficient port scanner?
- I changed the port 4125 to 5631 which is used by PCAnywhere, but I
am not able to connect to TS even at my home after this change. I
guess either my home ISP or my company ISP is blocking 5631. I will
have to find a port opened by both my company's ISP and the Job site
ISP, which leaves this issue more challenging.

Any more ideas?

thanks

jack

.

Relevant Pages

  • 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)
  • Re: OWA-IE6 Access denied
    ... OWA works on port 443. ... you should get a blinking cursor if you run "telnet mail.mycompany.com 443" from a command prompt on the remote client. ... As this happened when you changed ISPs, and OWA still works from other locations, then the ISP should help you resolve it. ...
    (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, ... VBScripte: Remote Desktop Disconnected ... The client could not establish a connection to the remote computer. ...
    (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: Current status?
    ... You would still need to know who your MTA is ... justification for allowing anybody to use port 25. ... to the problem of how to get the email system to be more immune to SPAM. ... your ISP should never allow you ...
    (comp.os.vms)