Re: RWW/Port 4125 Problems
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Tue, 17 May 2005 12:16:52 -0500
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?
>
>
.
- Follow-Ups:
- Re: RWW/Port 4125 Problems
- From: Lesa H.
- Re: RWW/Port 4125 Problems
- References:
- RWW/Port 4125 Problems
- From: Lesa H.
- RWW/Port 4125 Problems
- Prev by Date: RE: Cannot get WSS Companyweb to "link to Outlook" externally
- Next by Date: RE: companyweb
- Previous by thread: RWW/Port 4125 Problems
- Next by thread: Re: RWW/Port 4125 Problems
- Index(es):
Relevant Pages
|
