WINS server...
I'm currently on a small network setup with about 6 computers, I think the network browsing is quite slow so I have WINS server on my computer, but it only registers my computer, I'm in my own domain and all the other computers are in a second one.
I'm currently on a small network setup with about 6 computers, I think the network browsing is quite slow so I have WINS server on my computer, but it only registers my computer, I'm in my own domain and all the other computers are in a second one...
The other computers won't even find my WINS server at all...
Anymone knows whats wrong??
The other computers won't even find my WINS server at all...
Anymone knows whats wrong??
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Do you have the IP of the WINS server in the TCP/IP properties of all the clients? If you are using DHCP (preferably NT/2K server based), do you have the IP of the WINS box in the assignment properties for the clients? Try IPCONFIG /all from the command line in NT/2K clients, and WINIPCFG from the run line in Win9X clients to see if your WINS server is showing up on the client's properties page.
------------------
Regards,
clutch
------------------
Regards,
clutch
We only have one domain and that's because my computer is running active directory, I'm at my friend's place right now and all their computers are in their own workgroup. They don't the IP of my WINS in their TCP/IP properties, but arent't they supposed to find it automatically, or is that only when they're being rebooted?
Another reason may be that they have disabled NetBIOS over TCP/IP...
Another reason may be that they have disabled NetBIOS over TCP/IP...
Nice way to splash back onto the board, sand.
As for the WINS server IP, workstations will NOT find WINS servers any better than they would find DNS servers on their own. You have to enter the WINS IP into the client's TCP/IP properties just like DNS entries. In addition, go ahead and re-enable NetBIOS over TCP/IP as that is part of name resolution in case the WINS box is down. Once you do these, you should not have to manually create LMHOSTS on the clients.
------------------
Regards,
clutch
As for the WINS server IP, workstations will NOT find WINS servers any better than they would find DNS servers on their own. You have to enter the WINS IP into the client's TCP/IP properties just like DNS entries. In addition, go ahead and re-enable NetBIOS over TCP/IP as that is part of name resolution in case the WINS box is down. Once you do these, you should not have to manually create LMHOSTS on the clients.
------------------
Regards,
clutch
Ok, but I think I heard once that it's not necessary to enter the WINS IP manually, but that was obviously wrong...
And another thing, if there is a computer with Internet connection sharing, is it necessary to have dynamic IP on the clients or is it enough to enter the IP of the ICS server as default gateway?
And another thing, if there is a computer with Internet connection sharing, is it necessary to have dynamic IP on the clients or is it enough to enter the IP of the ICS server as default gateway?
I have no idea what you are talking about, I do not use ICS. I am just referring to general IP setup, so I would "imagine" that the LAN adapter would have all of these settings (WINS, DNS, Gateway). If the client is getting its proxy info from the "internet adapter", then I would imagine it needs gateway info as well. I would suggest reading the help file for that issue.
------------------
Regards,
clutch
------------------
Regards,
clutch
