We have a network of W95 PCs and an NT server. An ISDN router connects us to the Internet.
We only use the TCP/IP protocol, and allocate IP addresses using DHCP.
The DHCP server and a WINS server are installed on the NT box.
All PCs need to browse the Internet so we have set up DHCP to allocate the following entries:-
Router: (IP address of ISDN router)
WINS/NBNS Server: (IP address of NT server listed twice for primary and secondary)
WINS/NBT Node Type: 0x8
DNS Servers: (IP address of ISP's DNS server)
Domain Name: (i.e mycompany.co.uk)
Whenever we start the Exchange client on a PC, the ISDN router makes a call as if it is trying to resolve the name of the server via DNS...
We have done some tests, such as trying to ping the local server from a PC. When I type "ping servername", the router makes a call as if it is attempting to resolve the name via our ISP's DNS server. After a few seconds the IP number is resolved and we receive ping responses from the server.
Why does the PC seem to use DNS resolution instead of WINS resolution?
The ISP's DNS doesn't have an entry for our server, so I would assume the final resolution is being done by WINS anyway!
If I remove the DNS server entries from the DHCP scope the PCs resolve immediately using the WINS server, and don't force the router to make a call.
If I set up a W95 PC to have a fixed IP address instead of DHCP the problem remains... The router makes a call before the IP number is resolved.
If I disconnect the ISDN line from the router so it can't call, the ping command takes an absolute age to respond before it eventually resolves the IP address. Is this DNS timing out, and then attempting to resolve using WINS?
So - WHY doesn't the PC use WINS in preference to DNS? Every document I can find says that this is the way it should work!