Re: RWW/Port 4125 Problems



Frank,

I did enable Firewall Setup when I ran CEICW. The RWW filter for port 4125
is present and enabled. I wasn't sure where to look for 443 but I did look
at the protocol definitions and it's there and looks like another server
that's working properly.

What should I check next?

Lesa
"Frank McCallister SBS MVP" <anonymous> wrote in message
news:esMm0syWFHA.3324@xxxxxxxxxxxxxxxxxxxxxxx
> CEICW should set this up if you checked enable in Firewall Setup access
from
> Internet. Since it hasn't go into ISA Server management and be sure the
RWW
> filter Port 4125 is present AND enabled. Also ck tht 443 is enabled.
>
> --
> Frank McCallister SBS MVP
> COMPUMAC
> "Lesa H." <itsplesa@xxxxxxxxxxxxxx> wrote in message
> news:uBUy2LyWFHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
> > Frank,
> >
> > Thanks for the help. I checked as you suggested by hooking a laptop to
the
> > server external NIC with a cross over cable then configuring the laptop
> > for
> > ip 10.0.2.3 (the server external NIC is 10.0.2.2). When I tried to
access
> > https://10.0.2.2/remote, I got the same page cannot be displayed message
> > (with the entire page displayed this time and an error message of 404).
It
> > must be something in the server. That is what I suspected.
> >
> > Any ideas where to check in the server?
> >
> > Lesa
> >
> > "Frank McCallister SBS MVP" <anonymous> wrote in message
> > news:udjNuPwWFHA.1508@xxxxxxxxxxxxxxxxxxxxxxx
> >> Hi Lesa
> >>
> >> If your router has extra ports on it hook a laptop up and Https to the
> >> External NIC Static IP (Not the public IP) If you don't have extra
ports
> >> hook laptop up to the external NIC with a crossover cable and using
> >> Static
> >> IP on laptop go Https to External NIC. If either of these work the
> >> problem
> >> is external to your server. If they don't work the problem is in Router
> >> or
> >> external Path. BTW if you are trying to RWW from an ISA server (not a
WS)
> >> this won't work. Also if your provider on the Remote client is AOL it
> > won't
> >> work.
> >>
> >> --
> >> Frank McCallister SBS MVP
> >> COMPUMAC
> >> "Lesa H." <itsplesa@xxxxxxxxxxxxxx> wrote in message
> >> news:%23oj46IvWFHA.3712@xxxxxxxxxxxxxxxxxxxxxxx
> >> > My server is SBS 2003 Premium configured with dual NICs. It was a
> > SwingIT
> >> > migration to new hardware from SBS 2000. I've got my router open for
> > port
> >> > 4125 and 443 but I can't get to the server via RWW. I'm using a
static
> > IP
> >> > for now during the testing phase and I've tested both inside and
> > outside.
> >> > When I try to access https://<servername>/remote from inside I get
the
> >> > login
> >> > screen with no problem. When I try to access the server with
> >> > https://<publicIP>/remote from outside, I get "The page cannot be
> >> > displayed". The page display is kind of strange, too. It shows the
page
> >> > cannot be displayed message and the next few words of the rest of the
> >> > message but never displays the entire error page. I've set the
security
> >> > certificate to the public IP so I don't think the problem is there.
> >> > I've
> >> > been through the CEICW numerous times and everything looks correct.
> >> > I've
> >> > also checked the ISA packet filters and they look fine when compared
to
> >> > another unit that's working properly.
> >> >
> >> > When I check the public IP with GRC it shows port 443 open and port
> >> > 4125
> >> > closed. I know it's not being blocked by the router because when the
> >> > router
> >> > was blocking it, GRC showed stealth. In addition, I put the server in
> > the
> >> > DMZ and tried GRC that way, port 4125 still showed closed.
> >> >
> >> > I've set lots of these up without issue. This one is driving me crazy
> > and
> >> > the worst part is it's my own server. Does anyone have suggestions on
> >> > where
> >> > I might check for possible problems?
> >> >
> >> >
> >>
> >>
> >
> >
>
>


.



Relevant Pages

  • Re: Remote Connection Issue
    ... > If you want to connect to connect to the SBS server box and the LAN client ... you can use the RWW site ... > all related settings in ISA, IIS and firewall automatically. ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Connection Issue
    ... the main reason many inidividuals went to 2003 is the RWW (remote web ... > If you want to connect to connect to the SBS server box and the LAN client ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... I get 'cannot find server or dns error' on both ... TCP [port number]> to open the ports. ... As for error messages when I fail to access RWW with the laptop, ... network, no connection seems possible. ...
    (microsoft.public.windows.server.sbs)
  • RE: laptop can connect to RWW but cannot connect to workstations o
    ... The laptop is being used by my while working in the field.. ... I used to be able to connect to any of my customer's RWW and from there ... connect to the computer or server with the problem. ... Click Services tab and select Hide All Microsoft Services and Disable ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW and OWA dont work remotely; VPN does
    ... > I ran CEICW and all services including RWW and OWA are enabled. ... I tried changing the server certificate to the public IP ... so port 1723 is being forwarded. ... >>> server remotely, without a VPN connection, just using the publicIP, as ...
    (microsoft.public.windows.server.sbs)