Using alias for server consolidation

[gcamp]

I don't know if this is the correct group or not but here
goes. We are doing a server consolidation by merging a
lightly used server into a another server (data files
only). We are attempting to create an alias (same name as
the source server) to connect to the destination server.
In testing, using a previously unknown name to the
network, we were able to point an alias to an existing
server and we were able to access it using the alias
name. When we attempted to do the same to our source
server we kept getting "Access Denied" when trying to
browse to new server using the alias.

Here are the steps that we performed:
1. backed up the source - restored on destination -
created shares.
2. took source off the network.
3. Added the alias name in the registry
(SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
)
4. Restarted Server service on destination
5. Added alias in DNS. We were able to ping the alias
name and receive the address of the destination server.

What are we missing? Is there a problem with the original
source entries being in the routing tables? Did we not
wait for the master browser to get the changes? Any help
would be greatly appreciated. Thanks in advance

 

[serverguy]

Most "access denied" errors poing to a permissions problem and it would help
if you clarify the operating systems involved, whether or not you have a
domain, use encryption, etc..

 

[gcamp]

The operating system envolved is Windows 2000. The
servers are part of a domain. We do not use encryption.
Once the original server was brought back online we were
able to connect to the source server without a problem.