Hi All
We have a 2003 SP2 server which is multihomed - Interface 1 is on 192.168.1.0/24 subnet and interface 2 is on 192.168.2.0/24 subnet.
Interface 1 is only being used for FTP access to IIS only, interface 2 is being used for "all other traffic". 192.168.1.0 is not registered in AD DNS as a subnet because there are not any AD clients or servers on there (with the exception of this one, which is only for FTP traffic). 192.168.2.0 is registered in AD DNS
The "register this connection's address in DNS" check box has been disabled for interface 1. However, periodically we get that log on one of our DC's saying "in the past 4.x hours there have been y number of connections from clients that do not match to any subnets" (sorry, don't remember the exact wording).
So it seems that AD authentication is going over interface 1, when we want it to go over interface 2. Does anybody have any ideas why or how to stop it ?
Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau
We have a 2003 SP2 server which is multihomed - Interface 1 is on 192.168.1.0/24 subnet and interface 2 is on 192.168.2.0/24 subnet.
Interface 1 is only being used for FTP access to IIS only, interface 2 is being used for "all other traffic". 192.168.1.0 is not registered in AD DNS as a subnet because there are not any AD clients or servers on there (with the exception of this one, which is only for FTP traffic). 192.168.2.0 is registered in AD DNS
The "register this connection's address in DNS" check box has been disabled for interface 1. However, periodically we get that log on one of our DC's saying "in the past 4.x hours there have been y number of connections from clients that do not match to any subnets" (sorry, don't remember the exact wording).
So it seems that AD authentication is going over interface 1, when we want it to go over interface 2. Does anybody have any ideas why or how to stop it ?
Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau