Re: Remote Access and Outlook Web Access on SBS 2003
- From: "/kj" <kj@xxxxxxxxxxx>
- Date: Sun, 5 Feb 2006 22:44:23 -0700
If you're not establishing a connection on 25,80,443, or 444, then;
1) Your DI-524 isn't correctly forwarding to the server -or-
2) There is no server service listening on those ports.
Run the CEICW wizard and fix the DHCP and DNS misconfigurations. Then look
into the DI-524. If you can connect with Telnet locally on these ports, then
the rest is up to the DI-524 and perhaps port blocking by your ISP(s).
/kj
"Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:5374ADA4-7012-4C3D-B961-68FDECBEE91E@xxxxxxxxxxxxxxxx
I'm playing as nice as I can, given the stress my client is putting on me.
No offense intended. I thought I had explained myself well enough, the
first
time; but I could see that more than one had interpreted my remarks
differently than I intended.
I am not using UPnP, and I have configured the DI-524 manually, to allow
traffic on ports 443, 444, 1723, and 4125 to be routed to the server
(192.168.0.2).
Telnet won't work to port 4125, as was mentioned in a previous newgroup
message. As for the other ports, none of them are responding, even though
I
have NO trouble changing settings on the router itself
(http://66.xxx.xxx.xxx:8080).
.
- 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
- From: Lanwench [MVP - Exchange]
- Re: Remote Access and Outlook Web Access on SBS 2003
- Prev by Date: RE: Clients Cannot Connect via http://Server/ConnectComputer
- Next by Date: Re: Dell SC430 servers
- 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
|
