In addition for a small network with fixed IP's you can even use host files.
What appears to be the problem ?
I hope this helps !
Main Topics
Browse All TopicsIs there a WINS Server emulation program that can be installed on an XP Pro machine where there is no 2000 or 2003 server where a WINS server can be implemented.
Thanks!
Steve Parker
ABC Computing Services
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I have multiple networks linked through multiple firewalls, configured with VPN tunnels that can "see" one another. According to tech support from the firewall provider, Fortigate, WINS must be used to resolve systems, shares and devices, such as time clocks.
The problem is that not all of the sites have their own server, and I am not sure we can use WINS on one site to access a different site that does not have a WINS server. In fact, I cannot see how this can be done.
We have successfully accessed a static IP time clock through the proprietary software from one network to a different one, but the time clock is in a network with a 2003 server running WINS.
We'll likely need to install some kind of server, be it Unix, or 2003, but the full need cannot be fully explored as of yet, so I hesitate to shoot from the hip and take the chance of being way off!
Steve
WINS is IP based - you can have ONE WINS server serve the whole network. I used to manage a network with 2 major sites and about 40 subnets and we only used 2 wins servers - both in the same subnet.
And keep in mind, WINS is Windows Internet Name Server - it's a lookup method like DNS. One that, in Windows 2000/2003 is really only needed for Exchange. DNS handles everything else.
I would suggest you reevaluate why you think you need it and perhaps ask other questions regarding why the other programs aren't working then blindly blaming WINS.
I'm not blindly blaming WINS. This came from the techs at Fortinet. And once WINS was configured at the PC, it could "see" the remote site on the different network. But perhaps that one server can service the other networks ... I'll look at it from a different perspective. But I don't see how.
Site A is on, we'll say, 10.1.100.x, site B is 10.1.101.x, site C is 10.1.102.x, etc.
Because of the firewall setup, according to their technical support, WINS needs to be functioning for the VPN tunnels to fully function. We have a WINS server at 10.1.100.x, and so from 10.1.101.x we can see devices at 10.1.100.x.
Although we have not tested it as of yet, I am fairly certain that from 10.1 100.x we WILL NOT be able to see devices at 10.1.101.x because there is no WINS server on that end.
Got it? I am not "blaming" WINS, just looking for a solution short of installing a server of one flavor or another. Looks like I have my answer ... it does not exist.
Thanks!
It's clear from this description of WINS, you DO NOT need WINS on multiple networks:
http://technet2.microsoft.
So yes, if you DON'T want to try to resolve your Fortigate problem, then your answer is there is no WINS server for XP. If you DO want to resolve your problem, then please post some of your technical documentation saying the Fortigate requires WINS.
Maybe you're misinterpreting something or maybe we're misunderstanding something... the documentation may be able to clear things up.
And it's not unheard of to have a technician be WRONG or misinterpret/misdiagnose the problem.
Sounds to me like the application needs to use the browser service which is based on NetBIOS or is a NetBIOS enabled applcation. You need a good WINS solution if you want to do NetBIOS name resolution over this type of network. SysExpert is right about using files, but again if this is for NetBIOS, then the file is lmhosts. Also using lmhosts in this network is much more administrative work when compared to having a WINS solution since you have to ensure that the file is kept updated on each workstation and server. Look at the lmhosts.sam file for more information on using a central lmhosts file.
You don't need multiple WINS servers unless you want redundancy. Just install the service on a server in the network and have all clients and servers point their Network Properties to that IP for WINS. If you are using DHCP, just add the IP to the scope properties which is option 44 - NetBIOS Name Servers.
What we were trying to accomplish was VPN tunnelling to multiple sites, with one site acting as a "spoke" for the rest.
So the issue is that each site is on its own "network" and cannot see one another the way it is needed in order to connect to time clocks, for example, that were at opposite ends of the "spoke."
So we decided to use ONE server as the "designated" DNS server (which in our case was the server at the CENTER of the spoke) Then we plugged that Server;s IP into the Windows XP Pro systems as the DNS server at the "remote" sites, and allowed everything to "sync" up.
It works great!!!
The NAY Sayers just did not understand the problem! We figured it out on our own.
Hope this helps! Feel free to contact me back with any further questions.
Steve
sounds like we have very similar setups. We have 5 offices around Europe, one of which is the HQ and has the PDC (an SBS install) in place. Two of the "spokes have their own Win2K3 servers with DNS and WINS servers installed that sync to the HQ DNS and WINS servers. Both those in HQ and those at the other end of the spokes can see all computers in all offices in Network Neighbourhood. However the other two offices have only Win XP workstations as fileservers. They are pointed at HQ for DNS and WINS and they can see all the other offices and themselves in Network Neighbourhood. However, and here is the key issue/problem, those in the other offices cannot see the XP workstations in these "serverless" offices in network neighbourhood.
This causes problems when, for example, those in the remote offices save photos/documents on their local fileserver and refer to them to others working in the other offices, who then cannot access them.
All the office connections are site to site VPNs through Forinet 50b and 100a routers.
Installing WINS server in the two serverless offices would seem the answer, except there must be another way, surely? I posed this as a question to the experts exchange site back in October but got nothing concrete in response.
Still an issue - hmmm.
Gerry
Gerry,
Our configuration is different in some ways, in that not EVERY site has a server, and those that do have 2003 Standard, not SBS.
That said, we set up WINS on ONLY one server, the "spoke", and pointed the other computers to that server for WINS.
But the main issue was that the XP systems that on networks without servers could not "see" the other networks and did not seem to be negotiating the tunnels. So we configured WINS on those systems this way: From the "Advanced" button on the "General" Tab for TCP/IP properties, then the WINS TAB, and added the Central Server's IP address in here.
All I can tell you is that it worked for us. And I believe we were then able to see those computers from other networks at that point as well.
I'm not sure whether or not have multiple WINS server would be a good thing, or would confuse the situation. But I believe it should make no difference. I think if you add this to the workstations as well it will solve your problem. The XP "Servers" are not actually providing WINS for the network, just negotiating the tunnels themselves.
Steve
Business Accounts
Answer for Membership
by: chuckyhPosted on 2007-07-18 at 12:46:57ID: 19516705
I can't think of anything like that off the top of my head, I know SAMBA can do WINS, you can try running Linux in VMware on a XP box and do it that way.
Any particular reason why you need WINS? You can use NETBIOS over TCP/IP for name resolution, even Netbeui if you get desperate.