Advanced Server 7.3-A4 Browser Service problem

[Onno Welling]

Advanced Server Browser Service problem

Hi,
We have a situation with the Browser service on an OVMS (V7.2-2) Advanced server (AS) 7.3-A4. The browser service remains "Start Pending" on node1.

The AS is configured as a Member server in an NT4 domain.
The browser service on another AS (node2) in the same domain and subnet (same configuration, same versions) starts normally.
However, if we issue a pwstop on both node1 and node2 and a consecutive pwstart on both nodes, the browser service only starts on the FIRST node on wich the pwstart command is issued.

Further observations:
- The (NT4) PDC of the domain is on another subnet;
- Both AS (node1 and node2) do not show in the network neigborhood on the PDC;
- Both AS (node1 and node2) can be found using find computer in Network Neiborhood on the PDC;
- All shares on both AS nodes are normally accessible. Users have no trouble;
- NO errors are reported in pwrk$logs:*.log on both node1 and node2;
- NO errors in the event logs of both AS;
- $nbshow knbstatus node1 AND $nbshow knbstatus node1 AND $nbshow knbstatus PDC reveal that only the PDC is registered as the Master Browser on the network;
- From a pc: C:\nbtstat -a node1, C:\nbtstat -a node2 and C:\nbtstat -a PDC reveal that only the PDC is registered as the Master Browser on the network;
- Viewing the domain using BROWMON (from MS recourse kit) reveals the master browser as "Unknown" for the NT4 domain.

We would like to have the BROWSER service properly started on BOTH AS (node1 and node2).
Does anybody have any idea as to how we achieve that?


Help greatly appreciated.

[Bill Hall]

Onno,

The following url should give you some basic information on Windows Browsing that may help you determine what is and what is not happening on your network: http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html You should be able to find other MS TechNet articles as well.

I assume that the only network protocol you are using on Advanced Server is tcpip. Do you have a WINS server(s) configered somewhere on your network? Do you use lmhost files. These will affect browsing.

With multiple subnets browse master elections can get confused if you have just one Windows pc with an incorrect subnet mask, especially true if it happens to be running Windows 9x.

The Browser service should start on all servers, whether or not it is elected as a master. Are node1 and node2 in a cluster or are they standalone systems?

P.S.
IIRC it was sometimes helpful to have BROWMON running on a pc in each tcpip subnet.

Bill

[Paul Nunez]

Hi,

The Browser service in Start Pending state in a cluster is a known problem.

There's a patch available; if you have a support contract, contact the support center. If not, v7.3B will be release soon and contains the fix. v7.3b will be on the next quarterly software library due to ship in Oct.

You can avoid the problem by:

1. Waiting a few minutes after starting Advanced Server on one cluster member before starting it on the 2nd.

2. Disable the Browser service. If there are other domain members on the same subnet, especially Windows systems, let them do the Browser "stuff". To disable the browser service:

$ regutl set param * maintainserverlist no

You can stop the currently running service by doing $ admin stop service browser.

HTH,

Paul

[Onno Welling]

Hi All,

Thanks for the replies so far.
Here is some extra information. And a workaround!

First, both node1 and node2 are not in a cluster. Both are seperate VMS systems. Both are configured as Member servers. Both are on the same subnet.

The workaround; it worked for us. However, we are a little puzzled: Issue a PWSTOP on the node where the Browser service won't start (node1). Issue a view $ admin show computers/users/sessions - commands on the other node (node2). Now on node1 issue PWSTART. Now the browser service started like it should.

We will probably get the new version V7.3B pretty soon.

I'll leave the thread open for a while for anyone to comment.

Onno.

[Paul Nunez]

Hi Onno,

Ok, it's the same problem I was referring to. We were just under the impression in occurred in clusters. But after reading the details of the problem, I can see how it would affect two (or more) standalone Advanced Server systems on the same subnet.

The 2nd node is trying to establish an anonymous session to the first node but the first node, due to a bug, won't let it.

As you noted, executing an ADMIN command on the first node that causes the ADMIN interface to establish a session to the server gets around the problem.

This is fixed in v7.3B which is officially released (got the email about an hour ago :O).

$ ftp hprc.external.hp.com
Username: ionet
Password: ionet-pw

ftp> bin
ftp> get ASV73B.AXP1
ftp> get ASV73B.AXP2
ftp> quit

$ run asv73b.axp1 !Compressed PCSI Kit
$ run asv73b.axp2 !Manifest file

$ product install advancedserver


Let the upgrades begin!

Cheers,

Paul