From: MikeAdrenaline on
I recently had a client move offices, and in turn had to get a new ISP. I had
OWA and RWW, and Exchange working at the old location, but when they moved
nothing would work. Found out after a hours of router configuration, and sbs
restores and installs, that the ISP was blocking ports 25, 80, 443 and others
they would not mention. I did ask for these ports to be allowed but was
unsuccessful at having that happen. And I am unable to change ISP as there is
only one provider in my clients area now. But there has to be another
solution?

So far I have worked around two issues, but havent' been able to get past
the RWW homepage to connect to a computer or sign into OWA.

Port 25 >> enabled smarthost
-email works normal

Port 80 >> changed binding in IIS Manager to port 8081
Port 443>> changed binding in IIS Manager to port 4433
- now able to connect using both http and https
- also can connect to OWA and Remote Web Workplace homepage by adding the
port to my FQDN, https://remote.mydomain.com:4433/OWA and
https://remote.mydomain.com:4433/remote

On router I have unblocked ports 8081, 4433, 987, 3389, tested to make sure
these ports are open and all checks out okay.

OWA doesn't work becuse the link does not contain the portnumber in the
address, and connecting to a computer the TS Gateway launches but is unable
to connect to the computer and times out.

Any suggestions with regard to get th Remote desktop to work or OWA from RWW
homepage?


From: SteveB on
It looks like your client is trying to run a business using a residential
type ISP. Have you checked with the ISP to see if they offer a separate
business class service?

"MikeAdrenaline" <MikeAdrenaline(a)discussions.microsoft.com> wrote in message
news:32B787AA-B7B5-48C4-91BF-CBC10C536A59(a)microsoft.com...
>I recently had a client move offices, and in turn had to get a new ISP. I
>had
> OWA and RWW, and Exchange working at the old location, but when they moved
> nothing would work. Found out after a hours of router configuration, and
> sbs
> restores and installs, that the ISP was blocking ports 25, 80, 443 and
> others
> they would not mention. I did ask for these ports to be allowed but was
> unsuccessful at having that happen. And I am unable to change ISP as there
> is
> only one provider in my clients area now. But there has to be another
> solution?
>
> So far I have worked around two issues, but havent' been able to get past
> the RWW homepage to connect to a computer or sign into OWA.
>
> Port 25 >> enabled smarthost
> -email works normal
>
> Port 80 >> changed binding in IIS Manager to port 8081
> Port 443>> changed binding in IIS Manager to port 4433
> - now able to connect using both http and https
> - also can connect to OWA and Remote Web Workplace homepage by adding the
> port to my FQDN, https://remote.mydomain.com:4433/OWA and
> https://remote.mydomain.com:4433/remote
>
> On router I have unblocked ports 8081, 4433, 987, 3389, tested to make
> sure
> these ports are open and all checks out okay.
>
> OWA doesn't work becuse the link does not contain the portnumber in the
> address, and connecting to a computer the TS Gateway launches but is
> unable
> to connect to the computer and times out.
>
> Any suggestions with regard to get th Remote desktop to work or OWA from
> RWW
> homepage?
>
>


From: "Robbin Meng [MSFT]" on


Hello,

Thanks for your post and Steve's input.

Regarding the Remote Desktop connection in RWW, in order to allow a remote desktop connection to a client computer through Remote Web Workplace, TS Proxy is used to
forward TS requests through a firewall on TCP port 4125 , in essence keeping the connection alive. Once the connection is established on port 4125, the traffic is then redirected to
another dynamically allocated port. All subsequence traffic will flow through the new port at the server to the client at port 3389. So please check if the 4125 port is also open on your
firewall and ISP side.

If you are using SBS 2008, you can customize the links in RWW page to open you own websites, but this is unavailable in SBS 2003.

Hope this helps.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================