Discussion Locked

WINS aliasing

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

omfg I can't believe I forgot how to do this or whether or not you even can.

I have a server that needs to be accessed via \\server as well as \\my-server. I added static entires for both in WINS and yet only the real server name can be resolved or accessed rather via \\my-server by clients even though a "nbtstat -c" yields the correct information.

I remember there being another step to this puzzle when I did it awhile back, now for the life of me I can't remember what it was.

7 replies

by netlion

You might also be confusing DNS with WINS. You can enter into DNS an alias name for an existing server so it will resolve to both. With Win2K and AD this is more the way to go. Although I keep WINS running I try to deal with it as little as possible.

by aaron_wurthmann

ROFL, no I know the diff between WINS and DNS.

Here is the situation. The host has a a record and a cname in DNS. You can ping either but you can access it via \\server-share. So that makes you think hmm what about WINS. Well WINS has static entires for both. Is that not the correct procedure?

And you are correct about WINS and Windows cept I have NT 4 clients and you have to have WINS for them.

by aaron_wurthmann

errr...

The host has a a record and a cname in DNS. You can ping either but you can [NOT] access it via \\server-share [USING THE CNAME].

by netlion

I meant no disrespect, I was answering the question exactly as it was written, and I can't assume the level of knowledge you have. I have never had to manually enter WINS entries and I have been dealing with NT for 10 years. DNS aliases usually work just fine and let clients reference either name to get to shares. Clients should also be set to enable DNS for windows resolution at this point. Unless there is something else about your network/servers that you haven't mentioned in your question.
Ed Isaacs, MCSE

by aaron_wurthmann

:) None taken, not a prob. Basically what I was dealing with here isn't a WINS or DNS problem per-say it is a modification that you have to make in order for a system to answer to different host name then it has registered for itself. Systems will answer to IP addresses aliased with them but they won't always answer to an aliased name, be it a c name or an alias in WINS. I dealt with this problem once before and found the fix in the forums. Anyway, the above link I posted addresses the problem or in my case I justed added the name to my cluster configuration.

-Aaron Wurthmann, MCSE, MCSA, CCNA, Server+
lol, pwnedkthxbye

This discussion is closed to new replies.