For some reason the IP stack on our Win2K machine's don't seem to be keeping statistics correctly, for example.
Client machine, ip configured staticly with the DNS server entry also staticly configured.
1. Open a command prompt
2. type nbtstat -r. resolved by broadcast = 104, resolved by name server = 0
3. type nbtstat -R enter ipconfig /flushdns enter
4. Start a sniffer trace
5. Ping a machine on a different subnet
4. Name is resolved, ping is sent and returned
5. Stop sniffer trace, which reveals that the DNS query was sent from the client machine and resolved, results sent back to client which allowed the ping packets to go to the machine being pinged
6. Go to command prompt on client machine type nbtstat -r, resolved by broadcast = 104, resolved by name server = 0
Ok, I know darn well that the DNS server resolved the name, why isn't it being reflected in the second nbtstat -r? Our NT4.0 machines are behaving as advertised but not the Win2K machines, both server and professional.
Client machine, ip configured staticly with the DNS server entry also staticly configured.
1. Open a command prompt
2. type nbtstat -r. resolved by broadcast = 104, resolved by name server = 0
3. type nbtstat -R enter ipconfig /flushdns enter
4. Start a sniffer trace
5. Ping a machine on a different subnet
4. Name is resolved, ping is sent and returned
5. Stop sniffer trace, which reveals that the DNS query was sent from the client machine and resolved, results sent back to client which allowed the ping packets to go to the machine being pinged
6. Go to command prompt on client machine type nbtstat -r, resolved by broadcast = 104, resolved by name server = 0
Ok, I know darn well that the DNS server resolved the name, why isn't it being reflected in the second nbtstat -r? Our NT4.0 machines are behaving as advertised but not the Win2K machines, both server and professional.