How could changing the Binding Order affect server operation
Posted on 2003-03-13
How could swapping the binding order of the Remote Access WAN Wrapper and the Internal NIC adapters under the WINS (TCP/IP) protocol in the Remote Access Server Service affect the operation of the Server?
Currently the internal NIC is below the Remote Access WAN Wrapper.
Our Exchange 5.5 (SP4) server is a WinNT 4.0 (w/ SP6a) BDC server and also our RAS server. Multiple remote sites connect to both a Windows 2000 PDC and this WinNT 4.0 BDC server at our location (via LAN & WAN). Each remote office has a WinNT 4.0 BDC and LAN and our entire organization is under a single domain. There are also multiple mobile users that frequently connect to the network via dial up to this WinNT 4.0 RAS server. DHCP on our Windows 2000 PDC hands out IP addresses to these remote users. These RAS addresses are not excluded from the general pool of IP addresses given to the users on the local LAN.
Recently the Exchange MTA service failed when it attempted to re-start and in turn caused the dependent IMC service to also fail. Re-booting the server allowed all Exchange services to restart properly.
When the MTA service failed to re-start the Event Viewer logged several errors. Errors 2219, 2206, and 2207 suggested the MTA service had not shut down cleanly – however there were no other indications that it did not shut down properly. Errors 9321, 9266 and 9406 pointed me to KB article 279415 (we did not recently install Exchange 5.5 SP4, but might that still be relevant?) which recommended changing the binding order of all services so the internal NIC is at the top. This server has one service (Remote Access Server service) that is not configured properly (as referred to in my question). I need to be certain that “correcting” the order will not cause other issues to arise.
If changing the binding order of these adapters does not fix the “intermittent” MTA service startup problem, then there is an Exchange server 5.5 post-SP4 MTA Fix available that might help (KB article 283238). We have very few of the MS security fixes, etc. installed on this server.
Thanks in advance for any assistance.