My apologies if this is posted twice (or more). The first time I sent it I received a message back stating that the mailbox was full and to resend it. The second time I sent it I received a message stating that it had already been posted. Again, sorry if this is the third one you see! Since I have received very much useful information from this list I wish to contribute some suggestions which may be helpful to someone else. This is a problem Quest, the Hewlett-Packard Response Center (HPRC) and I worked on and off for months with. I must first say that I have to hand it to both Quest and the HPRC for their diligent and patient help with this problem. PROBLEM: To configure a second LAN on two HP3000 systems to allow Netbase/Shareplex to use this second LAN so as not to bottle neck traffic on the primary LAN which contains the two HP3000's, the DTC's, the DTC manager PC and a Novell server. This second LAN would be both a physically and logically different network. It would have a totally different set of IP addresses. Each HP3000 would contain 2 network cards. The two HP3000's are in the same room and connected via two thinlan connections (one for each LAN). The secondary LAN would be for Netbase/Shareplex use exclusively. SOLUTION: Besides the obvious purchase and install another LAN card in each system there are other steps that need to be taken. Since I am not an expert at installing LAN cards nor configuring them in the system I will not attempt to post the instructions here. The installation and configuration was done by HP. In NBCTRL in the configuration subsystem modify both nodes and change the node name (not the system name) to the new node name. Then shutdown and restart NETBASE/SHAREPLEX. This is very straight forward and simple BUT there are a few things that one should be double checked. THINGS TO DOUBLE CHECK: All of the following apply to both systems unless specifically stated otherwise. When configuring the node names in the network directory in NMMGR make sure of a few things. 1. Any of the node names configured in the NMMGR Network Directory Select Node Name screen (#9) do NOT match the LOCAL HP3000 Node Name as configured in the NMMGR Main screen (#2). The node names should be different. Believe me, having duplicate names caused significant problems for us. Even though using the Local HP3000 Node Name will work with NETBASE/SHAREPLEX on the primary LAN I still would recommend using a name setup in the Network Directory even if there is only one LAN. 2. The Name Search Methods and Order parameters in the Global Transport Configuration Screen (#86) should be 2,3,1. The second area to double check is the HOSTS.NET.SYS file. In the HOSTS.NET.SYS file the node names and corresponding IP address should be configured identically to the network directory. Do not place the Local HP3000 node name in the HOSTS.NET.SYS file. Also very important is to NOT using leading zeros in the IP address. Using leading zeros causes the HOSTS.NET.SYS file to interpret the following numbers as octal not decimal. Example: The IP address should be 111.222.33.4 NOT 111.222.033.004. NOTE: THIS ONLY APPLIES TO THE HOSTS.NET.SYS FILE. This is far from an all inclusive list of suggestions on how to configure a second lan card for use with Netbase and these notes may cause problems in a different situation. These are the problems and solutions experience by Gulf South Health Plans. I am only posting this in the hopes that it may give ideas to someone else who is experiencing the similar problems. I STRONGLY recommend calling the HPRC before implementing any of these suggestions. I am NEITHER an HP employee NOR a Quest employee. I am neither a network nor NETBASE/SHAREPLEX expert. Again, these are just suggestions and most definitely should not be taken as definite solutions to any problems. Again I must thank Quest and the HPRC for their assistance in this matter. Hope this helps someone..... --------------------------------------------------------------- Barry Durand "The opinions expressed in this Systems Engineer II email are not necessarily the Gulf South Health Plans opinions of my employer" [log in to unmask] ---------------------------------------------------------------