Hi
We found the cause for this problem - it had to do with the way they install the server (the use of Alteris software). We also found at way around this.
-Ib
"Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Posting the result of nslookup here may help.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Ib Tornøe" <(E-Mail Removed)> wrote in message news:677D379E-921A-440E-B903-(E-Mail Removed)...
I get the same answer as I do with a PING 10.1.1.1 - It does not do reverse
lookup.
It seems that the whole DNS resolver is just disabled. Personaly I don't
know a method to disable/enable DNS resolver.
Stopping the DNS Client just disables the caching.
REgards
Ib
"Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
news:Ol%(E-Mail Removed)...
Do a simple test. What do you receive if using ping -a ip?
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Ib Tornøe" <(E-Mail Removed)> wrote in message
news:703C1720-35F1-47C9-97AB-(E-Mail Removed)...
Hi
I have a W2K3SP1 server where the DNS resolver does not work.
Symptoms
- PING <IP address> .... This works
- PING name.domain.com ..... This does not work. I have installed WireShark
on the server and nothing is coming out of the interface.
- Configure e.g. name.domain.com in the HOST file loads the name in cache,
BUT still using PING name.domain.com does not work.. still nothing is
coming out of the NIC
- Using NSLOOKUP... Everything works just fine.
It seems that the DNS Name resolution is disabled.
Any suggestions
TIA
Ib
Similar Threads
Linear Mode
