i5/OS NetServer

Logon Server — Conflict Message CPIB687

CPIB687 Informational Message text

For reason codes 1, 3 and 4, see the Recovery text in the message.

For reason code 2, see the additional information below.

Reason code 2

Message cause text:

A Logon Server or Domain Master Browser service already running on conflicts with the i5/OS NetServer.

Message recovery text:

The IP address of the conflicting machine is . The i5/OS NetServer is configured as the Domain Logon Server, however, an attempt to bind to the unique NETBIOS name failed. The NETBIOS name is composed of the domain name followed by a service identifier. If the service identifier is 1B, then the Logon Service will not be fully functional. If the service identifier is 1D then the Master Browser Service will not be fully functional. See this page for recovery options.

What it means

• A system on the local network segment is already providing Master Browser or Logon services for the domain
• A system on a remote network segment is providing Master Browser or Logon services for the domain and it along with i5/OS NetServer are both configured for the same name server (i.e. WINS).

In the error message, a logon server conflict is indicated by a domain<1B> name (also known as a domain master browser conflict). A segment master browser conflict is indicated by a domain<1D> name. The following sections deal with the resolution of these conflicts in more detail.

Note: Another conflict that is not specifically addressed by the message in V5R1 is indicated by a domain<00> name. If you see this name in the message, it is most likely caused by the conflicting machine in the network having a host name that is the same as the domain name that i5/OS NetServer is configured for.

Logon Server conflict

The first thing to determine is whether the systems in conflict are members of the correct domain. Because you can have only one logon server per domain, the domain of one of the logon servers may be incorrect.

To change the domain for the conflicting system, perform the following steps:

1. Open Control Panel-->Networks and click the Network Identification tab.
2. Enter the correct domain name or workgroup and click OK.
3. Click OK on the Networks panel and you will be asked to reboot.

1. Open Control Panel-->System and click the Network Identification tab.
2. Click Properties and enter the correct domain name or workgroup.
3. Click OK and you will be asked to reboot.

1. In Operations Navigator, select Network-->Servers-->TCP/IP.
2. Right-click i5/OS NetServer and select Properties.
3. Click Next Start on the General tab and enter the correct domain name.
4. Click OK and OK again on the properties panel.
5. End and restart i5/OS NetServer for the property change to take effect.

After changing the domain on the conflicting system, end and restart i5/OS NetServer on the system receiving the conflict message.

You might determine that the conflicting system is a member of the correct domain, however, it should no longer be a logon server. In this case, the appropriate service(s) need to be disabled.

1. Disable the Service on the conflicting system. For Windows NT Server:
   1. Open Control Panel-->Services.
   2. Select the Server service and click Stop.
   3. OPTIONAL: To disable the service the next time the computer boots, click Startup. On the pop-up panel, change the Startup Type to Disabled and click OK.
   For Windows 2000/XP:
   1. Open Start-->Administrative Tools-->Services.
   2. Right-click the Server service and select Stop.
   3. OPTIONAL: To disable the service the next time the computer boots, right-click the Server service and select Properties. On the pop-up panel, change the Startup Type to Disabled and click OK.
   For iSeries:
   1. In Operations Navigator, select Network-->Servers-->TCP/IP.
   2. Right-click i5/OS NetServer and select Properties.
   3. Click Next Start on the General tab and change the Logon server role to None.
   4. Click OK and OK again on the properties panel.
   5. End and restart i5/OS NetServer for the property change to take effect.
2. Verify that the service has been disabled.
   1. Open a command prompt window on the conflicting computer or other PC on the network.
   2. Type: nbtstat -a Where is the name of the conflicting computer.
   3. Verify that an entry for domain_name <1B> does not exist, where domain_name is the name of the domain the logon server is servicing.
3. End and restart i5/OS NetServer. When i5/OS NetServer initializes, it is now able to start the logon service as well.

Segment Master Browser conflict

If the logon server and an existing master browser are in the same network segment, normally, the logon server is allowed to acquire the segment master name when it starts up. The old segment master browser sees the new segment master browser, initiates an election process (because there can be only one master browser per segment), and releases its 1D name (demotes itself) if it loses the election. However, if WINS is being used to manage the name service across segments and a segment master browser has registered itself with WINS (not all PCs do so to allow multiple domain segments), you will see this message. Also, if the conflicting master browser is another iSeries, then you are likely to see this message.

This conflict usually does not prevent a user from logging onto the domain. However, if the client machine is in a remote network segment and is relying on browse lists to find the presence of the logon server, the conflict may affect the client machine's ability to resolve to the logon server.

To allow i5/OS NetServer to register the service properly, either change the domain of the conflicting system or disable the master browser service on the conflicting system. If the domain needs to be changed, then follow the domain change steps in the Logon Server conflict section above.

Note: Changing to a new domain means the computer will no longer maintain a browse list for the old domain.

1. Disable the service on the conflicting system. You need to determine whether the service should be only temporarily disabled or permanently disabled as well.

   If the conflicting system is on the same network segment as the logon server you are trying to start, then it should be permanently disabled. If the system is in a remote network segment, the system can still function as a master browser if it is not another iSeries logon server.

   For Windows 9x:

   Determine whether the Win9x system really needs to be a file or print server. It will not try to become a master browser if it is not configured to share files or printers. If the system does not need to share files or printers, perform the following:

   1. In the Control Panel, open Networks.
   2. Click the File and Print Sharing button underneath the Client for Microsoft Networks drop down box.
   3. Uncheck both the file and printer sharing boxes and click OK. This removes the File and Printer Sharing for Microsoft Networks component and the computer will no longer act as a master browser.
   4. Click OK to save the configuration and you will be asked to reboot.
   If the system does need to share files or printers and you want to permanently disable the master browser service, perform the following steps:
   1. Select the service File and Printer Sharing for Microsoft Networks.
   2. Open the Properties panel, and click on the Advanced tab.
   3. Select the Browse Master property and change the value to Disabled.
   4. Click OK and OK again on the Network properties panel. You will be asked to reboot.
   If the service needs to be temporarily disabled, shutdown the PC, but do not restart it yet. For Windows NT:
   1. Open Control Panel-->Services and select the Computer Browser service.
   2. To tempararily disable the service: click Stop.
   3. [Optional] To permanently disable the service as well: click Startup. On the pop-up panel, change the Startup Type to Disabled and click OK.
   For Windows 2000/XP:
   1. Open Start-->Administrative Tools-->Services.
   2. Right-click the Computer Browser service and select Stop.
   3. [Optional] To permanently disable the service as well: right-click the Computer Browser service and select Properties. On the pop-up panel, change the Startup Type to Disabled and click OK.
   For iSeries:
   1. In Operations Navigator, select Network-->Servers-->TCP/IP
   2. Right-click i5/OS NetServer and select Properties
   3. Click Next Start on the General tab and change the Logon server role to None
   4. Click OK and OK again on the properties panel
   5. End and restart i5/OS NetServer for the property change to take effect
2. Verify that the service has been disabled.
   1. Open a command prompt window on the conflicting computer or other PC on the network.
   2. Type: nbtstat -a Where is the name of the conflicting computer.
   3. Verify that an entry for domain_name <1D> does not exist, where domain_name is the name of the domain the logon server is servicing.
3. End and restart i5/OS NetServer on the system that received the conflict message. When i5/OS NetServer initializes, it is now able to start the Master Browser service as well.
4. If the conflicting system was shutdown in order to disable its master browser service, you can now boot the system.

	Microsoft Windows NT Browser white paper
	Troubleshooting the Microsoft Computer Browser Service