Discussion Locked

sbs 2000 to 2003 migration

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

Hi, I am migrating from win2k server to Small Business Server 2003 with the
Active Directory Migration Toll (ADMT) and I am getting this error during
migration. "Network path Not Found (Error code=53,Domain=Ourdomain).
I have followed the exact procedure from the Microsoft document:
Migrating from Small Business Server 2000 or Windows 2000 Server to Windows
Small Business Server 2003. The names of my domains are entered correctly in my source and destination server entry box. DHCP is disconnected from both destination and source servers.
I can ping my source and destination server.
I?m an admitted rookie with servers but supposed to have this done by Monday?YIKES!!! Help if GREATLY appreciated. THANKS! 

5 replies

by cg it

they both have to be on the same subnet, the domain names [netBIOS]can not be the same.

by len

I'll have to check it tomorrow morning when I go back into the office . They definately have different netbios names. But I'll have to double check the subnets. They are usually always the same 255.255.255.0 or something similar.

Thanks for the quick post!

by cg it

I've used ADMT on SBS for migration from a W2K SBS server to a W2003 SBS server. Basically they both have to run on the same network and you its best to use the same admin account [the admin account on the old SBS is the same admin account on the new SBS [change it afterwards]. They both can not have the same NetBIOS name as the ADMT will not will not be able to distinguish between the 2 DCs if they are.

by len

Still not working. Both computers are on the same network, different ip's, same subnet. Both can access ojects in the network independently of one another. If you are familiar with the Microsoft procedure 'Migrating from Small Business Server 2000 or Windows 2000 Server to Windows
Small Business Server 2003'I have followed its instructions. Destination and source servers use the same admin names and passwords. Everything checks out. I still get the error code listed above. A post in another support group for the same problem said that person needed WINS. That was all they said and no answer was given if it had worked and I'm not sure what that entails.

Note...the source server has never handled DHCP since we have let our router do that in the past and now our Firewall is doing it.

This discussion is closed to new replies.