Windows Server has 2 I.P. addresses, which one will clients use?

[Dublin73]

Hi,

I have a bit of a dilemma...

2 seperate subnets in 2 seperate offices. One Active Directory domain.

Subnet A has a network ID of 130.140.0.0/24
Subnet B has a network ID of 153.213.4.0/24

Subnet B needs to see 2 hosts on the Subnet A network. This is done via NAT at our firewall.The 2 hosts on subnet A are...

SERVER1 I.P. address: 130.140.0.22
SERVER2 I.P. address: 130.140.0.23

Subnet B sees these two servers as addresses 192.168.0.22 and 192.168.0.23. This is because of the 2 static NAT mappings on the firewall.

192.168.0.22 NATs to 130.140.0.22
192.168.0.23 NATs to 130.140.0.23

In the Advanced TCP/IP settings of the two servers, SERVER1 and SERVER2, there are two IP addresses, the 130.140.0.x address and the 192.168.0.x address.

The clients on Subnet A ( again, they are on the 130.140.0.0/24 network ) should ping the two servers and resolve the two servers by their 130.140.0.0/24 address.

This is not always the case. Sometimes the client PCs on Subnet A will ping SERVER1 and SERVER2 and will resolve them to their 192.168.0.x addresses, even though they are physically sitting on the same switch and subnet as the servers, the 130.140.0.0/24 network. The client PCs will continue to resolve the servers IP address to the 192.168.0.x addresses, until we flush out the local cash... ipconfig /flushdns.

How do I get the subnet A clients to always resolve the servers to their 130.140.0.x addresses and the subnet B clients to always resolve the servers to their 192.168.0.x addresses?

thanks in advance to anyone kind enough to help!

 

[cyberspace]

Im not really all that up on this sort of thing yet, so forgive me if this isn't correct...

but could you make an entry in the clients hosts files on Subnet a for the IP Address and Name of the server?

ie.

130.140.0.22 SERVER1
130.140.0.23 SERVER2

This would mean that any pings to server 1/2 should always come back as 130.140.0.22 or .23

At least I think so?

Im sure there is a better solution so the pros can feel free to dismiss my input

'When all else fails.......read the manual'

 

[pansophic]

I'm not sure that I see the issue. If people connect by name, then the IP that it resolves to should be irrelevant.

The obvious answer is to use different name resolution servers (DNS or WINS) for each of the subnets. Only define the address that you want to be used for that subnet on its server. Of course that isn't very efficient.


pansophic