Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Advanced Server 7.3B with MultiNet 5.2

Jeremy Begg
Trusted Contributor

Advanced Server 7.3B with MultiNet 5.2

Hi,

I have installed Advanced Server V7.3B from the Feb 2007 CD-ROM set onto a system running MultiNet V5.2 and OpenVMS Alpha V8.3.

When I try to start Advanced Server the only processes which start are PWRK$LICENSE_R and PWRK$MASTER. All the rest die almost immediately.

The file PWRK$LOGS:PWRK$KNBDAEMON_node.LOG contains this error message:

Mon Aug 20 16:43:43 2007 bind_a_port(137): t_bind failed: 5
Mon Aug 20 16:43:43 2007 Port binding failed

which on various older versions of Advanced Server and Multinet was fixed by a new version of PWRK$KNBDAEMON.EXE

Is there a fix for the versions I am running?

Thanks,

Jeremy Begg
3 REPLIES
Richard Whalen
Honored Contributor

Re: Advanced Server 7.3B with MultiNet 5.2

What are you using for a nameserver and what does a NSLOOKUP of LOCALHOST (without a terminal .) return?

We had a MultiNet 5.2 field test site that was using a name server that returned various wrong information for a LOCALHOST lookup that had similar problems.
Jeremy Begg
Trusted Contributor

Re: Advanced Server 7.3B with MultiNet 5.2

Interesting. Turns out that your suspicion was correct:

$ mu nsl localhost
Server: eric.vsm.com.au
Address: 150.101.13.5

*** eric.vsm.com.au can't find LOCALHOST: Non-existent host/domain

So I've fixed my nameserver ...

$ mu nsl localhost
Server: eric.vsm.com.au
Address: 150.101.13.5

Name: LOCALHOST
Address: 127.0.0.1

and then attempted to start Advanced Server again. However it's still not working:

Tue Aug 21 18:30:16 2007 bind_a_port(139): t_bind failed: 5
Tue Aug 21 18:30:16 2007 Port binding failed

I notice that the port number has changed from 137 to 139, so I suppose that's progress of a sort.

What to try next?

Thanks,

Jeremy Begg
Jeremy Begg
Trusted Contributor

Re: Advanced Server 7.3B with MultiNet 5.2

More news .... it's definitely something to do with MultiNet 5.2. I did a fresh install of MultiNet 5.1 on this server and now the PWRK$KNBDAEMON process starts.

Time to raise a support call with Process Software I think.