Re: Remote Access and Outlook Web Access on SBS 2003
- From: "/kj" <kj@xxxxxxxxxxx>
- Date: Sun, 5 Feb 2006 22:20:17 -0700
They say a picture is worth a thousand words....
So is your client using SMTP rather than the POP puller? If so you should
be able to telnet to port 25 on your clients public IP.
Is your client running premium edition with ISA installed?
You should also be able to do the same on ports 443, 444, 4125, and if you
enabled it, port 80.
And are we to assume that you can't connect to the client from other
locations as well?
/kj
"Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:02E9DCBA-57CA-433D-8F9E-FD8E966B071F@xxxxxxxxxxxxxxxx
Ok, I am going to make this CRYSTAL clear.
In my home office, located in Delray Beach, FL, my router is on local IP
172.16.0.1, and in my home office, located in Delray Beach, FL, my
computer
is at local IP 172.16.0.34.
In my client's office, in Boca Raton, FL, (about 7 miles away), his router
is on local IP 192.16.0.1, and his SBS 2003 server is on local IP
192.16.0.2.
My client has a static IP (on a T1 line) at 66.xxx.xxx.xxx.
I can easily connect to my client's D-Link DI-524 router at
http://66.xxx.xxx.xxx:8080/
I cannot connect to my client's server, for OWA or RWW.
What I was saying, was, that my home office's local subnet was different
that the subnet for my client, so THAT was not the problem.
I have no reason to be annoyed with either my ISP or my client's.
I have EVERY reason to be annoyed with Microsoft.
.
- References:
- Re: Remote Access and Outlook Web Access on SBS 2003
- From: Lanwench [MVP - Exchange]
- Re: Remote Access and Outlook Web Access on SBS 2003
- Prev by Date: Re: Remote Access and Outlook Web Access on SBS 2003
- Next by Date: RE: Clients Cannot Connect via http://Server/ConnectComputer
- Previous by thread: Re: Remote Access and Outlook Web Access on SBS 2003
- Next by thread: Re: Remote Access and Outlook Web Access on SBS 2003
- Index(es):
Relevant Pages
|
