Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migration Wizard problem: can't log in to source

Status
Not open for further replies.

jwgrahamjr

Programmer
Dec 12, 2002
28
US
I am migrating a NW3.12 server to NW6 SP1.

I am using Migration Wizard 6.0 on a client machine...I created my project and am in the process of verifying it. I only get one critical error and no other errors:

Source Server PCS: Source Server PCS: MAP3XIDS.NLM on server 'PUBCERT' could not log in to the source server 'PCS'. Be sure that login is enabled on the source server. Be sure that the destination server can see the source server using the Display Servers command.

--- Error caused by a NetWare API error ---
An unknown error has occurred.
(Error code: 0X894f Function Name: NWLoginToFileServer)

Here is the config of both servers (migrating an existing server to new server hardware):

configuration on destination server (NW6 SP1):

3COM Etherllink PCI
Version 5.44 June 10, 2002
Hardware Setting: Slot 5, I/O Ports E800h to E83fh, Memory E1003000h to E100307Fh, Interrupt Ah
Node address: 000475A1ED21
Frame Type: Ethernet_802.2
Board Name: PCS1_E82
LAN protocol: IPX network 00000002

3COM Etherlink PCI
Version 5.44
Hardware Setting: Slot 6, I/O Ports EC00h to EC3fh, Memory E1004000h to E100407Fh, Interrupt Bh
Node Address 000475ABBB2D
Frame Type: Ethernet_II
Board Name: PCS2_EII
LAN Protocol: ARP
LAN Protocol: IP Addr: 192.168.1.6 Mask: 255.255.255.0

ServerID: 12345678



Source Server (Novell 3.12):

File Server Name: PCS
IPX Internal Network Number 00000008

Intel ExterExpress Pro PCI Adapter
Version 3.23 November 5, 1997
Hardware Setting: Slot 100006, I/O Port B000h to B81Fh, Memory E3000000h to E30000FFh, Interrupt Ah
Node Address: 00E018902F7
Frame Type: Ethernet_802.2
Board Name: NIC1
LAN Protocol: IPX Network 00000002

Netgear FA310TX Fast Ethernet PCI Adapter Driver
Version 2.25 February 12, 1999
Hardware Setting: Slot 1, I/O Port B400h to B40Fh, Interrupt Bh
Node address: 00A0CCDA8F7C
Frame Type: Ethernet_II
Board Name: NIC2
LAN Protocol: IP Addr: 192.168.1.100 Mask: 255.255.255.0

3.12 doesn't seem to use a serverid.

Running client 4.83 SP1 on Windows XP
Connected to source server using IPX
Connected to destination using IPX (tried IP also)

I made sure login was enabled on the source server...it was.
I did a "Display Servers" on the console of both servers. They *could* see each other.

Any ideas as to why the migration wizard would be giving this error? Both servers are using the same frame type. Both use IPX network 00000002.

Thanks...






 
Hello jwgrahamjr -

Prior your migration, did you patch your 3.12 server? I remember when we migrated, we had to run patch after patch just to get it to a "migratable" state. And that was migrating from 5.x - 6

As far as your error code goes, this link should help you:

Good Luck.
 
Yes, I did patch the 3.12 server. I used SYSCON and set "Limit Concurrent Connections" to "No" but I am still getting the problem.

I'll keep trying.

John
 
Success at last....well, partial success at least.
I gave up on trying to get the NW6 server to log in to the NW3.12 server.

I got a CNE friend of mine to come over and we tried some other things to correct the problem, including:

1. Removing the extra NICs/bindings in borth servers.
2. Verifying each patched module file date.
3. Using the (slightly older) .NLMs that come with the wizard for both servers.
4. verifying duplex/speed settings were the same on all systems.
5. trying differing versions of the client and wizard
6. making sure there were equivalent usernames on both machines

After spending a large amount of time on the problem, we finally decided that it would be easier and faster to just copy the data to the new server and set up the users & login scripts from scratch. Actually, as painful as this was, it gave me a chance to clean out the old garbage accounts that were lingering around on the old server.

My advice...don't waste too much time trying to upgrade a 3.12 server to 6 using the migration wizard 6...with 25 users or less, it is easier to do by hand that to wrestle with the migration wizard.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top