Can't browse computer via nlb cluster name

Posted by peg_leg on Server Fault See other posts from Server Fault or by peg_leg
Published on 2011-01-12T21:38:01Z Indexed on 2011/01/12 21:55 UTC
Read the original article Hit count: 198

Filed under:
|
|

I have a fileserver nlb cluster, currently set to single affinity, made up of 2 2008R2 servers. We switched the primary node today. Now our Windows XP workstations can't browse to the cluster name (i.e. \fileserver) but can browse to the cluster ip address (i.e. \192.168.1.1) and can browse the member server by name (i.e. \filesvr1). I remember having a similar issue when we had to change a registry setting to allow Windows XP boxes to see another file server that was in a failover cluster but had to be referred to by another name (\thisfileserver instead of \fileserver). Convoluted, for sure, but it helped to prevent any code changes from happening.

Well all of the programmers have their code on \fileserver and we can't have them switch their links every time \filesvr1 supercedes \filesvr2 or vice versa. I can't remember that registry setting that allowed the file server to ignore that it's being called by the wrong name. HELP!

© Server Fault or respective owner

Related posts about windows-xp

Related posts about nlb