Trying to virtualise a Windows Server 2000 running Lotus Domino Server 5.0

Lotus Domino
Lotus Domino Server 5.x
Server virtualization
Windows Server 2000

Our organisation has a very old legacy app running under Domino 5.0 on a Dell Server on Windows 2000 Server. It is totally read-only, and just has to be there for cross-reference. Ideal solution is to virtualise onto our Vsphere platform. Made several attempts using VMware Standalone Converter 4.x and 3.03. Conversion always successful, but when the virtual server comes up and the Domino Server starts, we get the following message in the console, and none of the clients can connect.

[strong]10/08/2011 17:17:11 Server started on Physical Node XXXXXX[/strong]

[strong]10/08/2011 17:17:11 error on listen function: NETBIOS unit/lana number specified in NOTES.INI is not valid on this system or a network is not started[/strong]

Message repeats a number of times, then

[strong]10/08/2011 17:17:11  Listener task for port LAN0ip is suepending for 20 seconds due to listen errors[/strong]

[strong]10/08/2011 17:17:11  Router: Unable to obtain Internet Host and domain names [/strong]

The startup completes , but the users are unable to connect.

We have no Notes/Domino expertise on site, but we do have Windows/VMware/networking skills .We are guessing it is related to the network hardware changing and that Notes/Domino needs to be told somehow (NOTES.INI ?) . Please can anyone help with some simple troubleshooting steps/best way forward. each time we have done this we have had to roll back to the physical server, most frustrating !!

Thanks & Regards


Software/Hardware used:
Lotus Domino Server 5.0

Answer Wiki

Thanks. We'll let you know when a new response is added.

Notesini – Is the Domino configuration file stored on the server – c:\lotus\domino\Notes.ini (I think this is default location for 5).

Open the Notes.ini and check for the following lines. I am guessing that the Domino server is trying to configure itself to an IP that is not assigned to the Virtual machine.

TCPIP=TCP, 0, 15, 0


The Domino server needs to connect to itself for every thing to run as expected. If you can get console access from the Console on the server try running a

TRACE <servername>

You will find it will not connect…. then try a

Trace <ip address of server> this might connect.

If it does connect the AMGR will now work for a short time and so will other things…. because it will cache the IP. If this is the case you need to either remove the IP address from the Notes.ini or remove it and use DNS…..

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Gabe9527
    Did this work????
    11,095 pointsBadges:
  • Jammydodger9999
    Hello, sorry for the long silence. I have been away for over a week, but I am back now. Thanks very much for the response. We actually reverted to the physical server, but I kept the virtual machine file. I will crank it up and have a look and let you know in next day or so.. Regards JammyDodger9999
    15 pointsBadges:
  • Ledlincoln
    Another option: It isn't difficult to do a new install of Domino server. You could set up a new Windows server, install Domino under the old server's name, copy the legacy app to it.
    1,620 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: