Re: Rmote Access problem

Hi Alfredo

It doesn't matter what you call the firewall rule.

On your firewall open port 4125 and tell it to forward any traffic on that
port to your SBS Server.

Kev

"Alfredo F. Gonzalez" wrote:

Hi Kev,
When I open the router to forward to the server what name do I give the
application? "RWW"? "RDP"? or what for the SBS to know.
I can then assign the port number and the router IP, right?
Thanks for your help and assist!

and Pedro CR,

Access is remote remote Web Workplace,
Connecting from a separate location through the internet.

Thanks for your help!
Alfredo Gonzalez

"KevM" <KevM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A37283F-03F6-4840-98FA-7D174C67C051@xxxxxxxxxxxxxxxx
Hi

I had the same problem, I sorted mine by opening port 4125 on my firewall
and forwarding it to my SBS server

Kev

"Pedro CR" wrote:

what access method are you usign?

1) Are you usign Remote Web Workplace?
2) Are you connecting via VPN and then using mstsc.exe to connect to the
server?
3) Are you connecting from the internal network?

In case it's 2 check to see if, after loosing remote connection to the
server you can still ping the server.

"Alfredo F. Gonzalez" <lourdesg@xxxxxxxxxxx> escreveu na mensagem
news:VYdhj.18467$Xo1.3771@xxxxxxxxxxx
At the company we have a server running Windows Small Business Server
2003,
but we have a problem trying Remote Access to it.
We can get to the log on page.
From there, once logged on we are taken to the main menu page.
There you select the task to access the Server desktop, or to access a
client station or any other task and click to proceed.
And after you select the task the server just stops
All you get in response to the command is a blank page with headinga
and
the
log off - Main menu choices.
After a few minutes an error message appears:
***************
VBScript: Remote Desktop Disconnected
------------------------------------------------------------------------------------------------
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept 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.

OK
**********************************
We know that the remote connection is enabled. The server is not too
busy.
There are no other connections, the network is working.
We can access the Exchange and retrieve email, on the same sever.
We know we connect to the server since the logon page and subsequent
pages
emanate from it.
How can we solve this remote access problem? Any suggestions and help
will
be appreciated.
A. Gonzalez







.

Relevant Pages

  • Re: Cannot telnet some ports
    ... Some with remote administration feature I believe. ... >> From a Windows 2003 Server SP2 ... >> fromn the 2k3 serrver but can telnet into any other port. ... kerberos 750/udp kdc # Kerberos udp ...
    (microsoft.public.windows.server.general)
  • RE: Remote Web Workplace not completely working.
    ... In order to allow a remote desktop connection to a client computer through ... TS requests through a firewall on TCP port 4125, ... To open the port 4125 on ISA, we can re-run CEICW to confirm it. ... server certificate) and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Rule for Remote Desktop?
    ... My server has a private IP address on the WAN NIC. ... 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: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Kazzaa- spyware
    ... > server, then file retrievals from your machine must be done with the ... >>- Allow all UDP for both direction, for local port 123 and remote port ... > But unfortunately RR is changing the DNS addresses all the time. ...
    (comp.security.firewalls)