Re: Problems with RWW connection after move

Leon,

Try this...

In the PIX, make sure port 4125 is forwarded to the SBS NIC. Then re-run
CEICW, select the services, complete the Web Server Certificate and finish
CEICW.

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

"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:%23bH3mOKMHHA.4888@xxxxxxxxxxxxxxxxxxxxxxx
We have an SBS2003 Standard up and that's been running for over a year
using RWW for email and remote desktop connection with no problems. Then
we moved to a larger location. Although the new location is only a few
blocks from our original location the DSL installation required the we be
issued a new series of fixed IP addresses. We use a single NIC with a PIX
506 at the front end, and had to completely recofigure the PIX. Our first
new PIX setup quickly allowed us to connect to the Internet, but we had no
email from our Exchange server. We then went back into the PIX and made
sure ports 25, 80, and 443 were open (we don't need VPN). This allowed us
Exchange email and the ability to access RWW's main menu for email and
internal web site. But when remote users tried to connect to their
computers at work, they couldn't. Today we went back into the PIX and
opened port 444, and immedately afterwards a remote user was able to
remotely connect to his desktop computer -- or at least we thought he did.
I called another remote user to try connecting, and she could not. I also
came home and tried connecting, but I could not connect to any computer at
work. Here's the error I'm getting:

"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 . . ."

From this experience I get the feeling we have missed one or more ports
that also need to be opened. But if so, which ones? Thanks.

Leon



.

Relevant Pages

  • Re: puTTy: Coonection reset by peer
    ... I'm always getting a "connection reset by ... Your problem has nothing to do with "port 3306," or anything with your ... The difference is that the first is localhost access and the second is from ... because the code's user does not have a login via a remote host. ...
    (comp.security.ssh)
  • Re: Using Remote Desktop From an SBS Domain
    ... Right click My Network Places...Properties. ... computer that is on a remote network now. ... Internet connection, bypassing my SBS/ISA network all together. ... the port number you connect to from 80 to a port of your ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace - Cannot Connect to Server Desktop, but can use outlook web access, tim
    ... You should absolutely close PORT 80 ... I had setup the services on the router but I hadn't then inserted them into the firewall rules set. ... Download Connection Manager, ... VBSCript: Remote Desktop Disconnected ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Rule for Remote Desktop?
    ... receives a connection on port 4125, it first compares the IP that sent the ... the remote PC is blocking 4125. ... logging interface in ISA to port 4125 when I attempt to do Remote Desktop ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not get Remote Connection Working on XP Pro
    ... TCP Port 80 is used by IIS if you want to use the web based Remote Desktop ... I could not make a connection from the outside. ... > my linksys router. ...
    (microsoft.public.windowsxp.work_remotely)