windows domain server and dns server same machine?

  • Thread starter Thread starter Julie Smith
  • Start date Start date
J

Julie Smith

We are having serious problems connecting to our domain server with my
laptop. This is the situation. My laptop on windows xp pro normally connects
to the office lan without any problem. I have to put in my user name and
choose the office domain and hey presto I'm in and I see all my docs.
Problem happens when I'm at home. I try to link up to the server but the
message I keep getting is:

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain myserver.mydomain.com

- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.

I'm wondering is it because our dns server is on the same machine as the
domain server?

We are using as workstations Windows XP Pro
Static server address e.g. 192.168.0.2
gw = 192.168.0.1 (router)
dns = 192.168.0.2

Thanks very much guys ...... it's driving me mad
 
DNS on a Domain Controller is fairly common (we use it here). How are you
connecting from home (e.g. VPN)? Do you have a router at home? Does it work
from other remote sites?

One thought is if your Local Area Connection is using a static IP address
set for your office LAN without alternative networks set up, then it will not
connect to your home ISP.
 
This may have more to do with how you are getting to the office network from
home. Given that the DNS server and the Domain Controller have private IP
addresses, you must have a VPN somewhere in the mix. The settings for the
VPN component may be preventing you from accessing the server correctly.
Check on the VPN software to see if you are allowing the system to provide
the DNS and that you connection is using the remote gateway.

Now the only reason that the DNS SRV and A records would not match up is if
the servername is wrong. This is a common issue when you have a Windows
2000/2003 that was created by upgrading a Windows NT 4.0 PDC. The problem
is that the FQDN of the domain like mydomain.com doesn't match the FQDN of
the server like myserver.olddomain.com. The DC then will not properly
register it's name in DNS and thus systems cannot find it. The perplexing
thing in your particular case is that you indicate that the domain works
appropriate while you are in the office. This however, could be related to
other name resolution methods being available like WINS or broadcasts. At
any rate it would be good to rule this out as a probable cause. Easy
enough - just right click My Computer and then click properties. Finally
click on the Computer Name tab and see that the server FQDN matches the FQDN
of the domain.

Paul Hinsberg, MCSE
 
Maybe I have been looking in the wrong direction here. I assumed that with
using .netserver I did not need a vpn connection? I have assumed by using
NAT and the domain such as myserver.mydomain.com I could access my domain
server this way?

So I definatley need to use VPN?

Best of thanks
 
Julie Smith said:
Maybe I have been looking in the wrong direction here. I assumed that
with using .netserver I did not need a vpn connection? I have assumed
by using NAT and the domain such as myserver.mydomain.com I could
access my domain server this way?

So I definatley need to use VPN?
Click to expand...

Most definitely.
 
Back
Top