Hi all,
I am back from vacation!
This morning I attempted to remove M$ Proxy Server from the Exchange box and
reconfigure TCP/IP settings. The Exchange box is now fully functioning
behind the Dachstein router as originally intended.
Note: the box had to be rebooted for the gateway address chang
Doug Sampson ([EMAIL PROTECTED]) had this to say on 02/14/03 at 15:07:
> >
> > But ... the ONLY change we are suggesting you make is to the Exchange
> > server's default gateway. Does that *really* require a reboot
> > on Windows?
> > (I know the old joke about "You have moved your mouse - pre
>
> But ... the ONLY change we are suggesting you make is to the Exchange
> server's default gateway. Does that *really* require a reboot
> on Windows?
> (I know the old joke about "You have moved your mouse - press
> any key to
> reboot", but surely Microsoft has make networking
> reconfigu
At 10:06 AM 2/11/03 -0800, Doug Sampson wrote:
Ray/Charles,
I was afraid you'd both still point to the TCP/IP settings of the Exchange
box as the cause for the failure. I had thought that scanning a range of
ports was to check if it was open. But it looks like my assumption was
wrong. It checks f
Ray/Charles,
I was afraid you'd both still point to the TCP/IP settings of the Exchange
box as the cause for the failure. I had thought that scanning a range of
ports was to check if it was open. But it looks like my assumption was
wrong. It checks for responses and obviously the scanner isn't get
Doug Sampson wrote:
No, Dachstein isn't replacing anything that used to exist at that address. I
am still running a Proxy Server 2.0 at that address and it shows port 25 and
80 being open. Running a port scanner from outside the network against the
Dachstein router shows only port 80 (and 22) as b
At 04:28 PM 2/10/03 -0800, Doug Sampson wrote:
Ray,
> But with all of that, I cannot connect (using telnet) to your
> mail server
> from here (though I can ping you and connect to the Web server).
You couldn't- all attempts to port 23 are blocked.
Of course they are. But I was attempting to te
Ray,
> But with all of that, I cannot connect (using telnet) to your
> mail server
> from here (though I can ping you and connect to the Web server).
You couldn't- all attempts to port 23 are blocked.
>
> So ... how thoroughly have you checked the Exchange server for
> configuration problems
On Monday 10 February 2003 04:32 pm, Doug Sampson wrote:
>20 800 ACCEPT tcp -- 0xFF 0x00 eth0
> 0.0.0.0/00.0.0.0/0 * -> 25
> 0 0 MASQ tcp -- 0xFF 0x00 *
> 192.168.1.4 0.0.0.0/0 25 -> *
> :: Port FW ::
>
> prot l
OK. Nothing like looking at a real ruleset to sort things out. The input
chain appears to be working properly to allow port-25 traffic in, since
this rule shows matching packets:
20 800 ACCEPT tcp -- 0xFF 0x00 eth0
0.0.0.0/00.0.0.0/0 * -> 25
Since you a
> OK, are several things that could be going wrong, besides
> mis-configuration (it looks like you've got everything setup
> properly,
> but I can't tell for sure without the full output of "net
> ipfilter list").
>
> 1) Your ISP is blocking port 25. This is fairly common, and is
> typically
Doug Sampson wrote:
I want to port forward any packets sent to port 25 on the external interface
to an internal email server but I seem to be having trouble doing so. I've
made the necessary changes to the network config file but the changes aren't
taking hold. I've rebooted the server twice to no
I want to port forward any packets sent to port 25 on the external interface
to an internal email server but I seem to be having trouble doing so. I've
made the necessary changes to the network config file but the changes aren't
taking hold. I've rebooted the server twice to no avail (I'm a M$ tech
13 matches
Mail list logo
