High-availability of legacy 'netbios' name in a 2003 cluster

hello guys!

i'm trying sort out little problem , wondering if done in 'correct' way (other, of course, scrap , in 21 century technologies :)

i have bunch of ms-dos clients need connect network file shares, i'd have on 2003 server cluster.

the thing is, clients connect netbios, can't use 'cname'/'cluster network name resource' solutions. discovered if use legacy key 'optionalnames' in lanmanserver registry, clients can connect server.

now question - can suggest way automate fail-over in such nasty scheme? when resource group fail-overs, need to: remove registry key 'passive' node (assuming online), add same key node became active, and, troublesome - probably, have restart 'server' service, doesn't registry parameters after start.

so if will, say, 'net stop server || net start server' in generic application/generic script, create fail of other 'share' resources in group. sooo... have ideas? :)

---

http://about.me/bromi

yes, can test scenario creating generic script command. make sure add delay code in script check successful failover of other cluster resources, , fire script.

hth

---

- thestriver

Windows Server  >  High Availability (Clustering)