C
Chris
We have 3 servers on our network.
server1 - DC, file/print/dns/dhcp/wins/exchange
server2 - terminal server
server3 - DC, exchange, RRAS VPN
I setup RRAS on server3, using the wizard. Server3 has a single NIC,
and I only checked the VPN box. PPTP connections using only 128-bit
encryption and MSCHAP2 are working just fine.
In the RRAS MMC console, I clicked on Network Interfaces. It shows 3
interfaces - loopback (127.0.0.1), Local Area Connection (dedicated,
192.168.1.11), and Internal (192.168.1.110).
Server3 registers itself in DNS with both the 192.168.1.11 and
192.168.1.110 addresses. This causes major problems, since every
request to server3 from server1 seems to want to go to 192.168.1.110,
which isn't an IP accessable from anywhere except the console of
server3 itself.
How can I prevent the internal interface from registering in DNS?
server1 - DC, file/print/dns/dhcp/wins/exchange
server2 - terminal server
server3 - DC, exchange, RRAS VPN
I setup RRAS on server3, using the wizard. Server3 has a single NIC,
and I only checked the VPN box. PPTP connections using only 128-bit
encryption and MSCHAP2 are working just fine.
In the RRAS MMC console, I clicked on Network Interfaces. It shows 3
interfaces - loopback (127.0.0.1), Local Area Connection (dedicated,
192.168.1.11), and Internal (192.168.1.110).
Server3 registers itself in DNS with both the 192.168.1.11 and
192.168.1.110 addresses. This causes major problems, since every
request to server3 from server1 seems to want to go to 192.168.1.110,
which isn't an IP accessable from anywhere except the console of
server3 itself.
How can I prevent the internal interface from registering in DNS?