Netware 3.12 in VmWare

darth vedar January 27, 2009 at 10:07:09
Specs: NETWARE 3.12
Hi

I am trying to move my old netware 3.12 to vmware. So first I try to make a fresh netware install just so I could understand netware a bit, without messing the real server. But it doesn't work.

I followed the instructions in http://www.vmts.net/article/install... except 11, and 12 since I think I need to do them after the server works(?) by copying and patching to/on the SYS volume(?)

Anyway the server is loading without any errors. I can load monitor and look there. I don't know to do much else. I then use NwDsk (http://www.veder.com/nwdsk/) to connect to the server and it doesn't find it. I then installed netware client for XP, but that doesn't find the server either.

I don't know how to test/debug/fix it from this point.

Please help.
Notes:
* I used this instead of the instructions (I had to change the xxxx and the slot that was not accepted either.)
load c:\server.312\pcntnw slot=10001 BIND IPX TO pcntnw NET=345
* I have tried bridged network, and NAT network card in vmware.
* In NwDsk protocols I mark the first and the forth only, since I don't need tcp/ip.


See More: Netware 3.12 in VmWare

Report •

#1
January 30, 2009 at 10:28:56
Have you checked, whether the volume SYS is mounted correctly and network driver is loaded and configured for your needs.

Please send a reply, if you solved the problem !!!


Report •

#2
February 1, 2009 at 08:49:46
Hello,

The boot up messages pass very fast, but on the SERVERNAME: prompt if I write 'mount sys' I get a reply that SYS is already mounted. If I put there at the prompt 'load c:\server.312\pcntnw BIND IPX TO pcntnw NET=345' I get a message 'Do you want to add another frame type for a previously loaded board' If I answer yes, then I get a choice of Ethernet_II, Ethernet_SNAP, and 802.3. After I choose one of these I get a message 'Previously loaded module was used re-enterantly'. I loaded all three suggested frame types, and tried to connect, and failed again.


Report •

#3
February 1, 2009 at 19:14:57
On the WinXP machine, in the login screen, you have to choose bindery login, because Netware 3.12 only supports bindery login.

Please send a reply, if you solved the problem !!!


Report •

Related Solutions

#4
February 2, 2009 at 09:13:57
Thanks for the reply.

I installed on XP 'NovellClient 4.91 SP5' and I don't see anywhere in this client the word bindery.

Please direct me on setting bindery login. Maybe I missed the bindery option, and maybe I need a different client.

TIA


Report •

#5
February 2, 2009 at 17:09:43
When the Novell Client comes up and asks for username and password, at the bottom right corner, you should see the Advanced button.
Click on it.
Now you should get several tabs. One of it is named Bindery. Click at the Bindery tab and activate the bindery login.

Please send a reply, if you solved the problem !!!


Report •

#6
February 3, 2009 at 02:32:25
Hi,

I don't have a bindary tab.

I have only eDirectory, Script, Windows, Dialup, NMAS.


Report •

#7
February 3, 2009 at 10:19:13
Ok, so you have to rightclick on the Red N.
Choose Novell Client Properties.
Click on the "Locatiion Profile Tab".
Select the Location Profile "default" and click properties.
In the next screen again click on properties.
Now you should see several tabs like "Credentials | eDirectory | Bindery | Script | Windows | Dial-up | 802.1x"
Choose Bindery tab and activate it.
Choose Server by clicking on the button Servers.

Please send a reply, if you solved the problem !!!


Report •

#8
February 3, 2009 at 15:03:25

OK, It took me a while to find the red N, eventually I found it next to the clock, and I also found that from the 'local area network' properties I can access the same 'client properties' config window.

Now I have a bindery tab, but when I press servers there at the bindery tab, the servers window that gets opened is empty and I have no servers to choose from. If I manually write my server name and try to log in it complains that the tree server can not be found.

By the way, I need to write a user name and password at the client login, but I have not configured any yet. I am thinking that the configuration program is ran from within the server, and I couldn't get "in" yet. Am I right? Is there a default user that allows login in at first?

BTW, does having the NIC as NAT or bridged in VMWare have any consequence on this?


Report •

#9
February 3, 2009 at 20:50:19
There is always a standard user on a netware server.
On Netware 3.12 is should be supervisor.
You hopefully know the password, because there is no supervisor without password.

To get the connection to work, first configure the NIC in bridged mode.

I assume, you've installed IPX protocol at the workstation, using the correct frame type (802.2 or 802.3).

Please send a reply, if you solved the problem !!!


Report •

#10
February 4, 2009 at 17:22:58
"You hopefully know the password, because there is no supervisor without password."
-- It is a new installation here, so if there is a password , it is probably set at some prompt at the setup procedure. I do not remember setting it up. I could re-install and see.

I set all the NICs at bridged mode (My workstations are in VMWare too, on the same computer)

"I assume, you've installed IPX protocol at the workstation, using the correct frame type (802.2 or 802.3)."
-- On XP, I thought that the netware client handles it, but it didn't so I added it up. On NwDSK it should be OK.

I tried again with all the above suggestions - bridged, IPX - and still no servers appear when I press the servers button on XP, and NwDSK also doesn't find the server.


Report •

#11
February 4, 2009 at 17:38:58
I guess the netware installation has not been completed.
At the server console type in config and press enter.
You should get a list of configured NICs.
There should also be listed:
File server name
IPX internal network number

If not, the installations hasn't finished.

You can try the following at the server console prompt.
file server name <enter>
ipx internal network <enter>

See what is shown up to you.

Please send a reply, if you solved the problem !!!


Report •

#12
February 5, 2009 at 13:44:41
I get as follows:

MYSERVER:config
File server name: MYSERVER
IPX internalnetwork number: 00000343

AMD PCNTNW
Version 4.14 June 26, 1998
Hardware setting: Slot 10001, I/O Port 2000h to 201Fh, Interrupt Ah
Node Address: 000C2999693C
Frame type: ETHERNET_802.2
No board name defined
No LAN protocols are bound to this LAN board

If I do
load c:\server.312\pcntnw slot=10001 BIND IPX TO pcntnw NET=343

Three time more to load more frame types, then at the prompt the following config command shows the last 7 lines again and again 3 more times, where the only difference is in the 5th line "Frame type: X" where X is etherenet_II, etherenet_802.3, and etherenet_snap. The rest is identical.


Report •

#13
February 5, 2009 at 19:07:57
You can not bind IPX to the internal network number.
Try this
load c:\server.312\pcntnw NAME=NIC1 slot=10001 FRAME=Ethernet_802.2
BIND IPX TO NIC1 net=8022

Please send a reply, if you solved the problem !!!


Report •

#14
February 6, 2009 at 11:59:50
Hi,

I tried it and there is no change :(


Report •

#15
February 6, 2009 at 14:52:43
Have you already checked the error log files?

Are the windows clients also in VMware?
Are the NICs of the clients also in bridged mode?

Please send a reply, if you solved the problem !!!


Report •

#16
February 6, 2009 at 16:19:58
Hi,

I tried it and there is no change :(


Report •

#17
February 6, 2009 at 17:00:05
Did you alway try to find the server from a virtual windows machine or did you also try a physical computer to connect to the netware server?

Please send a reply, if you solved the problem !!!


Report •

#18
February 7, 2009 at 15:21:33
Everything I did was in vmware server. The netware server , the XP client, and the nwdsk client.

Report •

#19
February 8, 2009 at 09:44:40
Generally the server should be accessable now.
Try to bind tcp/ip to the servers NIC and give it a ip address of your network range.
Then try to ping the server from one of your workstations.

Please send a reply, if you solved the problem !!!


Report •

#20
March 3, 2009 at 11:50:59
Hi friends, I am having the same problem in my company. After the configuration of TCP / IP, I am PING, but didnĀ“t have comunication between nwclient and novell server. I believe the path to the solution is actually on the configuration of the network card of VMware.

Report •

#21
March 3, 2009 at 12:58:10
Yes, and in this case I suggested to first switch the NICs in VMware in bridge mode.
So the IP addresses of the guest OS are not translated, filtered or whatever and you can first bring your system to work.
After that, you can play around with the VMware NIC settings, if you want.

Please send a reply, if you solved the problem !!!


Report •

#22
March 4, 2009 at 07:24:47
It worked, exactly as spoken. Disable all NICs except for communication with VMware (VMnet1 - host only) and also disable the VMware bridge protocol. Thank you very much.

Report •

#23
November 1, 2010 at 15:01:53
Hello. You can also use this tutorial. I've created it to simplify things.
http://cerbulescubogdan.blogspot.co...

Report •

Ask Question