Re: Remote Web Workplace from client = Page Not Found for most att
- From: "thabrown" <thabrown@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Dec 2005 07:33:03 -0800
Hello, again,
By RDP'ing into my server, I removed the port forwarding on my SBS network's
router for ports 80 and 443. I added 443 back, and RWW now works --
accessing from internet at remote location. So, it seems my router's port
forwarding was the problem -- as it did not retain the port forwarding that I
had previously set up -- even though its admin page indicated those ports
were still forwarded. Is this a common dilemma -- routers not retaining port
forwarding they are configured to do? I bet tomorrow when I try RWW, it
won't work; but if I redo the port forwarding again it will.
My router is a Netgear RangeMax WPN824.
Thomas
"Lanwench [MVP - Exchange]" wrote:
>
>
> In news:57C5F4F7-8C39-426F-B949-706CCDDFE434@xxxxxxxxxxxxx,
> thabrown <thabrown@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> > Thank you, Lanwench, for your reply.
> > RWW works internally, whenever I've tried, although I have not
> > coordinated an attempt with someone remotely at the same time. Will
> > do so in the next couple of days.
> > Yes, I created a certificate when running CEIW for my public IP. I
> > repeated the CEIW and re-created, just in case, but to no avail.
> > Remotely telneting to ports 443 and 4125 to my public IP does not
> > work -- "Could not open connection to the host, on port 4125: Connect
> > failed". Can you tell me what that may mean?
>
> And yet this works from other machines at the same time?
> Can you telnet on port 443 to anything on that computer? Such as
> citibank.com ?
> Are you using ISA?
>
> > Meanwhile, some attempts on browser yield Page not found, while other
> > attempts hang for very long -- showing "connecting to
> > xxx.xxx.xxx.xxx..." in status bar -- and then "Done" with blank
> > browser screen.
> >
> > I appreciate any other ideas you may have.
> > Thank you,
> > Thomas
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >>
> >>
> >> In news:5A14F7C0-A3F5-43C7-81EA-0631CB5463E6@xxxxxxxxxxxxx,
> >> thabrown <thabrown@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> >>> Hello,
> >>> I recently enabled Remote Web Workplace via my SBS2003 SP1 server,
> >>> and I was able to access it fine a couple of times -- remotely on
> >>> internet, using http://mystaticpublicIPaddress/remote. However,
> >>> most of the times I've attempted over the past several days, I
> >>> consistently get a "Page Not Found" -- from different XP SP2
> >>> clients, on different days/times. My remote internet connection is
> >>> cable broadband and is usually fine, so I don't understand why
> >>> accessing RWW only works a small percentage of times I try.
> >>
> >> When it isn't working from the Internet, is it still working
> >> internally on the network? Can you ask someone to test
> >> https://myservername/remote internally?
> >>>
> >>> I've searched and read many postings in this newsgroups but found
> >>> nothing specific to explain the intermittent accessibility. I've
> >>> tried using https, instead of http, but that did not alleviate. Can
> >>> someone explain, by the way, when to use https versus http?
> >>
> >> I only use https:// - I don't allow inbound connections on port 80.
> >> When you ran the CEICW, you were prompted to create an SSL
> >> certificate, right?
> >>>
> >>> I use a public static IP, as I have not registered a FQDN to that
> >>> IP,
> >>
> >> If you have a registered domain name, the IP doesn't matter. You can
> >> have whomever manages the public DNS create an A record that points
> >> at the public IP.
> >>
> >>> so http://FQDN/remote is not an option. Should that matter though?
> >>
> >> Nope. It's just easier to remember a name than an IP address.
> >>
> >>> I have port forwarded 4125, 443, 80, and 3389 on my router to the
> >>> private IP of my server.
> >>
> >> I wouldn't use 80. And unless you want direct RD to your server,
> >> which many don't, you don't need 3389.
> >>
> >>> Is there any configuration or settings
> >>> necessary on my remote XP machines?
> >>
> >> No, as long as you've downloaded the ActiveX control to allow remote
> >> connections to the computers on the LAN.
> >>
> >>> On those machines, I've added my
> >>> public IP to "trusted sites" via Internet options. Is there any
> >>> settings I should do on my remote's router? Windows firewall is off
> >>> on the remote XP machines, as I am using TrendMicro. I have allowed
> >>> my public IP in TrendMicro's Network Security Personal Firewall
> >>> exception list for Outgoing tcp/udp all ports.
> >>
> >> Can you telnet on ports 443 and 4125 to your public IP when this
> >> happens?
> >>>
> >>> Any other suggestions I would much appreciate.
> >>> Thank you!
> >>>
> >>> Thomas
>
>
>
.
- Follow-Ups:
- Re: Remote Web Workplace from client = Page Not Found for most att
- From: Lanwench [MVP - Exchange]
- Re: Remote Web Workplace from client = Page Not Found for most att
- References:
- Re: Remote Web Workplace from client = Page Not Found for most attempt
- From: Lanwench [MVP - Exchange]
- Re: Remote Web Workplace from client = Page Not Found for most att
- From: thabrown
- Re: Remote Web Workplace from client = Page Not Found for most att
- From: Lanwench [MVP - Exchange]
- Re: Remote Web Workplace from client = Page Not Found for most attempt
- Prev by Date: Re: Problem Installing POP3 Connector
- Next by Date: Re: Offline folders icon still displays in startup menu
- Previous by thread: Re: Remote Web Workplace from client = Page Not Found for most att
- Next by thread: Re: Remote Web Workplace from client = Page Not Found for most att
- Index(es):
Relevant Pages
|
