bobhminimum6characters
Bit poster
Hi folks, I have a weird setup, so please follow along.
I have a Guest 2008 r2 server install at 192.168.1.75, hardcoded ip, that runs DNS server.
I have a HOST win 7 64 with a hardcoded IP and DNS.
Running Bridged, with Default Adapter selected.
Build 6.0.13976
If I drop to dos prompt and PING 192.168.1.75, it works just fine.
If, from that same dos prompt, i run nslookup, then do "server 192.168.1.75" and try to look up ANYTHING, I get dns timeouts.
WTH have I done wrong, and how do I go about fixing it?
Other points:
EVERY other machine in the 192.168.1.x network can get to .75 for DNS and DHCP.
Yes, I can resolve the host machine, by name, from all other hosts, using .75 as the server.
(FYI, i have it set up like this as my real DC was dying. I was able to get a virtual DC running from the old one, and transfer everything over. Everything works fine EXCEPT DNS.
I can even put
\\192.168.1.75\c$
into explorer and it works just fine. )
I have a Guest 2008 r2 server install at 192.168.1.75, hardcoded ip, that runs DNS server.
I have a HOST win 7 64 with a hardcoded IP and DNS.
Running Bridged, with Default Adapter selected.
Build 6.0.13976
If I drop to dos prompt and PING 192.168.1.75, it works just fine.
If, from that same dos prompt, i run nslookup, then do "server 192.168.1.75" and try to look up ANYTHING, I get dns timeouts.
WTH have I done wrong, and how do I go about fixing it?
Other points:
EVERY other machine in the 192.168.1.x network can get to .75 for DNS and DHCP.
Yes, I can resolve the host machine, by name, from all other hosts, using .75 as the server.
(FYI, i have it set up like this as my real DC was dying. I was able to get a virtual DC running from the old one, and transfer everything over. Everything works fine EXCEPT DNS.
I can even put
\\192.168.1.75\c$
into explorer and it works just fine. )