> > 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 > reconfiguration a bit > more sane by now). OR does the proxy server require that it > be the default > gateway to function (if so, in what sense does it proxy)?
Yep, Win NT still requires a reboot for most configuration changes. Yes, we are still using Win NT- haven't seen the need to upgrade. See below for further info. > > In principle, this approach should work just fine for not > dropping mail. > But remember to do it far enough in advance so that the > change propagates > to cached records elsewhere. And consider if the Exchange > server itself > requires any special reconfiguration. The added MX record > should point to > an FQN that is externally resolvable to the router's IP address. > > A quick check of your MX records says that you already have > external MX > backups: > > autovcr@waverly:~$ host -t MX dawnsign.com > dawnsign.com MX 20 smtp.easydns.com > dawnsign.com MX 30 smtp2.easydns.com > dawnsign.com MX 0 mercury.dawnsign.com > dawnsign.com MX 10 mail.dawnsign.com > > Both the 0 and 10 entries point to your proxy-server IP > address. But if the > 20 and 30 entries are functional, they should protect you > against e-mail > loss during your test phase. Noted. > But before you go on with this ... why do you need this > Exchange server to > be reachable both via the old proxy server and via the new Dachstein > router? Is it just a transition issue, or is there something more > fundamental that requires this duplication? Why not handle everything > through suitable MX entries that get all mail to a single IP address? > It's a transition issue. The proxy server and the Exchange box is the same box! Due to cash flow restrictions, it was decided to combine proxying and email functions in one box. Since then I've experienced random and intermittent crashes with the Winsock proxy service which I was unable to resolve. I was advised to upgrade to ISA which I totally nixed. I have to change the proxy server setting on all client browsers to point to a Squid server which uses the Dachstein router as it's gateway. Then remove the Proxy Server software (and the second NIC) and change the IP settings on the Exchange box before I can use it as originally intended. Not a change easily performed. Since I will be going on vacation next week, I've tabled this until my return. I'll report back in once the switch-over has been attempted. Thanks for all your help. ~Doug ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
