Server 2003 Name Alias

[BDawg]

We're currently looking to consolidate 2 file servers into 1. In order to not change installed printers, shares, etc, can we make one server respond to both names?

I set up a fake name in DNS that was a pointer back to server1. I can ping with the fake name, but if I try to do the following,

\\fakename\shared

I get the following error:

"You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again."

How do I set it up so I can accomplish the later task?

 

[bsobel]

This isn't a supported configuration, support for this was broken in Windows 2000 and has never been restored (from what I remember).

Sorry...

 

[RebateMonger]

Assuming you are using a Domain, why not assign file shares and printer shares via Group Policy? A Logon Script can delete all the old shares and add the new ones the first time the client computers boot.

 

[Smilin]

Yes, you can do it but you'll be disabling some security. What you are trying to do should only be done on a temporary basis (like make one server behave as another while the original is being repaired). If you are considering this as a long term solution to save your lazy ass from having to move printers and shares then you should reconsider (no offense)

If you want to do it the right way get the printer migration tool from MS (free download). You can also just grab the lanmanserver\shares regkey and move it from one box to the other provided the shares point to the same drive letter and all that. There are tons of KB articles on doing the migration you are trying to do.


k, now that soapbox stuff is out of the way, here is how you load the gun to shoot yourself:


First, kerberos is never going to work like this. You'll have to use NTLM.

Second, you'll need to make SMB ignore the fact that someone is asking for something with the wrong name.

Search at ms for the following registry key: DisableStrictnameChecking

Once strict name checking is disabled you can approach the server for an NTLM connection with any name and it will respond.

 

[bsobel]

Search at ms for the following registry key: DisableStrictnameChecking

I saw some posting that it got broke again on 2003 SP1, but I haven't verified that (Smilin, do you know?)

 

[Smilin]

I just did a quick repro and, yes it works with 2003 sp1.

 

[BDawg]

The fileshaing is easy to move since it is all done in active directory and in scripting. Printers were the concern. They're difficult to script since people rotate machines on a shift basis and different machines have different printers for the area.

 

[Smilin]

MS makes a printer migration tool.

If I recall correctly it takes the shares, permissions, necessary drivers and everything from one box and packs it into some cab file. You then go to the new box and the tool drops it all back in place.

 

[TG2]

Whatabout a DFS share, could that work ?

 

[kobymu]

Virtualization (in a limited way), virtual PC or VMware. Different OSs different addresses. A disadvantage could be from a performances POV, the same hardware will need to carry two OSs (two kernels, two I/O management and so on), it all depends on you hardware and needs (how many poeple, how many files and so on).

Never tried anything like that myself so this might be completly redundant but, maybe a secound NIC on the fileserver might help fooling/tricking the DNS (mapping different addresses to different IPs, in case you'r DNS is dymanic - different MAC addresses), may help solve the problem from the DNS side but from the fileserver side i think you will still run into some problems.

 

[Smilin]

second nic won't solve the problem and could add new ones.