General discussion

Locked

vpn server name resolution

By jedimaster ·
Hi there. I've some problem which is pestering me. But I have to explain the whole network first so bear with me.

Server:
FQDN: test.testdom.plyfoam.local
NetBIOS: TEST
Services: DNS
DHCP (192.168.1.10-192.168.1.80)
RRAS: Router (LAN and Demand-dial routing, Remote access server)
Enable IP Routing, Allow IP-based RA and DD routing
Static address pool: 192.168.1.81-192.168.1.100
Enable broadcast name resolution
Use adapter NIC1 for DHCP, DNS etc?
IGMP: NIC1 ? Router v3, NIC2 - Proxy

NIC1: 192.168.1.1/255.255.255.0 using DNS 192.168.1.1 connected to switch to which all LAN pcs are conencted.

NIC2: 192.168.10.2/255.255.255.0, Gateway 192.168.10.1, DNS 192.168.1.1 connected to netgear ADSL Router.

ADSL Router: 192.168.10.1/255.255.255.0
DHCP Server: 192.168.10.2 ? 192.168.10.254
WAN: Dynamic address from ISP
Firewall rules: Allow TCP 1373, UDP 1434, VPN: TCP 1723

I have registered the server on the web using dyndns.org

If I connect to the server through VPN, all goes well. However, if I ping 192.168.1.1, I get replies but if I ping test.testdom.plyfoam.local, I get replies from IP 192.168.10.2. Why is that? And is there any way for me to get replies for the name test.testdom.plyfoam.local at IP 192.168.1.1?

My thing is that I also have SQL server running on the server and when I log on through VPN, there are some default settings used in replication where they use the settings from the server which contains the names instead of IP. e.g. Distributor [TEST\TEST] and when the client tries to access the distributor, it addresses the wrong IP. For the client connecting through VPN, the correct IP for "test" and "test.testdom.plyfoam.local" is 192.168.10.2. Which is wrong...

Thanks for helping me out.

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums