Discussion Locked

"\\192.168.12.254" use WINS or not ?

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm still confuse about the problem that i faced today. I try to browse HQ LAN from remote using \\192.168.12.254 but can't seen any. But if i ping the ip 192.168.12.254 the server can reply.

On the other hand from HQ mapping to remote using \\10.10.10.200\something can do.

is this a problem of name resolution or what ?

9 replies

by uwe.stammler-gesiehn

All operations using \\ will look up wins but windows will additional use the complemetary service (in this case the DNS) to resolve the name. If WINS don?t found the entry in his database, he will look up the dns. If DNS don?t found, ....
It?s a Microsoft-feature.

by dcassat

It is a name resolution problem. You may easily troubleshoot this by adding an entry for the server on the remote workstation in the lmhosts file. If this solves the problem, you can then determine if you want to use a more elaborate method of name resolution.

by joshg

Go to start then Find then computers, type in the IP of the machine. If it shows up you can browse the shares. Then try the NetBIOS name of the PC. If it doesn't show up you have a name resolution problem. You can enter the entry into DNS, WINS or LMHOSTS. Try entering the IP and NetBIOS name in the LMHOSTS, reboot the search again. If you find it you are okay. Then you need to decide if other PC's will need to get to the NetBIOS name of the PC. If so then create WINS, if the server is on a different subnet then you will have some work to do. WINS will resolve the names and make updates as IP and names change so you won't have to go to each machine and update LMHOSTS all the time.

by bigjedi20

We've the same type of setup. 172 local and 192 off of the T1 lines. Without Wins Server Address in offsite workstation, they can't resolve. Once we put Wins IP, no problems.

This discussion is closed to new replies.