Re: Problems with RWW connection after move

I opened port 4125, pointed it to the NIC IP address, and reran CEICW, and
now the whole system works just as before our move. Thanks Merv.

Leon




"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eEN7ChMMHHA.2456@xxxxxxxxxxxxxxxxxxxxxxx
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: Problems with RWW connection after move
    ... In the PIX, make sure port 4125 is forwarded to the SBS NIC. ... using RWW for email and remote desktop connection with no problems. ...
    (microsoft.public.windows.server.sbs)
  • Problems with RWW connection after move
    ... RWW for email and remote desktop connection with no problems. ... and had to completely recofigure the PIX. ...
    (microsoft.public.windows.server.sbs)
  • VPN SBS2003
    ... opened port 1723 on the router ... and set up the remote computer using disk created in SBS. ... When I attempt to connect I get a secure connection then ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: RDC on SBS 2003
    ... the SBS Server itself? ... We are having issues making a successful Remote Desktop Connection to ... We opened port 3389 on the servers using the Connect to Internet Wizard ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... If you have more than a couple of remote workstations connecting to the SBS ... server via VPN, you really need to consider a Terminal Server in the main ... "Log in using a dial up connection" checkbox, ... roaming profile then synchronizes with the server over the VPN); ...
    (microsoft.public.windows.server.sbs)