HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Advanced Server fails to start on TCP/IP

 
Jeremy Begg
Trusted Contributor

Advanced Server fails to start on TCP/IP

Hi,

I've been helping a site with a new configuration, an AlphaServer DS25 running OpenVMS V8.2, Advanced Server 7.3A-ECO4, TCP/IP Services V5.5-ECO1, and DECnet-IV.

They're unable to mount any file shares on this server from local PCs. Checking the Advanced Server logs I found this:

PWRK$KNBDAEMON_SB001.LOG
Sat Mar 25 14:01:51 2006 get_phys_addr: PWRK$KNBDAEMON_DEVICE is set to _EWA0:
Sat Mar 25 14:01:51 2006 get_phys_addr: _EW2: PH Address: AA-00-04-00-C9-04
Sat Mar 25 14:01:51 2006 get_ip_addr: PWRK$KNBDAEMON_IPADDR is 192.168.201.3
Sat Mar 25 14:01:51 2006 IP Address: 192.168.201.3
Sat Mar 25 14:01:51 2006 ip_brdcst_address : 192.168.201.255
Sat Mar 25 14:01:51 2006 bind_a_port: t_open failed: 29
Sat Mar 25 14:01:51 2006 Port binding failed

I checked the TCP/IP Services configuration, and PWIPDRIVER is loaded (and there is a PWIP0: device on the system).

Does anyone have any suggestions?

Thanks.
11 REPLIES
Sameer_Nirmal
Honored Contributor

Re: Advanced Server fails to start on TCP/IP

Hi Jeremy,

It seems that Pathworks IP (PWIP) driver is not loaded.
Check the PWIP startup com file in SYS$STARTUP
It driver could be started as e.g.
$ @SYS$STARTUP:TCPIP$PWIP_STARTUP.COM
Karl Rohwedder
Honored Contributor

Re: Advanced Server fails to start on TCP/IP

Just some wild guesses:
- is the portmapper running
- confirm the PWK$KNBxx logicals
- ADVSRV was installed after VMS upgrade
- PWRK$CONFIG has been run amd ADMIN/CONFIG was o.k.?
- I fear the NBSHOW utility will not show anything, if the startup failed?
- ADMIN/ANAL shows nothing?

regards Kalle
Jeremy Begg
Trusted Contributor

Re: Advanced Server fails to start on TCP/IP

I don't believe PORTMAPPER is relevant here, but I started it anyway and it made no difference.

The NBSHOW and ADMIN/ANAL output didn't seem to provide any significant information that I could see. However I did find a large log file containing the following message repeated over and over again:

PWRK$LOGS:NETBIOS_SB001.LOG
%NB-W-ERRSIGNAL, exceptional conditional detected at 26-MAR-2006 12:42:07.75
-NB-W-ETHERESTART, port shutdown and restarted, messages may have been lost

The message is repeated every two seconds.
Ian Miller.
Honored Contributor

Re: Advanced Server fails to start on TCP/IP

Does TCPIP SHOW DEVICE show any processes bound to the port numbers that pathworks is trying to use?
____________________
Purely Personal Opinion
Paul Nunez
Respected Contributor

Re: Advanced Server fails to start on TCP/IP

Hi Jeremy,

Error 29 is really error 129 - system-w-duplnam, indicating Advanced Server is unable to allocate TCP port 139.

See if there are any tcp/ip devices using port 139:

$ ucx sh dev/port=139

If any exist, disconnect them:

$ ucx disc dev

You should then be able to Advanced Server.

If there are no devices using port 139, sometimes restarting the pwip driver can clean things up:

$ @sys$startup:tcpip$pwip_shutdown
$ @sys$startup:tcpip$pwip_startup

If that doesn't clear it up, you'll need to reboot.

Regards,

Paul
Antoniov.
Honored Contributor

Re: Advanced Server fails to start on TCP/IP

Jeremy,
HP has not released any support on OpenVMS V8.2 but official VMS road map shows Samba instead.
I think you should try to mount with NetBeui protocol, just to see what does happen.

Antoniov
http://it.openvms.org
Antonio Maria Vigliotti
John Abbott_2
Esteemed Contributor

Re: Advanced Server fails to start on TCP/IP

Hi Jeremy,

Advanced Server 7.3A-ECO4 is supported on VMS 8.2 (according to the release notes)

A DS25 has two network ports and of course you can add extra interfaces cards to add more. Not knowing your set-up and that Adv svr binds to one network interface, could it be that it's binding to a network interface on a seperate network or unused/unconnected interface ?

You can force which network adaptor is used, example:

(LNM$SYSTEM_TABLE)

"PWRK$KNBDAEMON_DEVICE" = "EWC0:"
"PWRK$NBDAEMON_DEVICE" = "EWC0:"
"PWRK$NETBEUI_DEVICE" = "EWC0:"

Pathworks has to be restarted for it to take effect.

Hope this helps

Kind Regards
John.
Don't do what Donny Dont does

Re: Advanced Server fails to start on TCP/IP

Hi Jeremy,

If you haven't already done it, you need to enable the Bind service under TCP/IP. It's required for Advanced Server v7.3A, but wasn't with earlier versions.

Good luck!

Chris
Karl Rohwedder
Honored Contributor

Re: Advanced Server fails to start on TCP/IP

Chris,

I have BIND disabled/stopped and my Adv.Server is just running fine, See attached file with my enabled services.

regards Kalle
Jeremy Begg
Trusted Contributor

Re: Advanced Server fails to start on TCP/IP

I followed through all of your suggestions without much success, so in the end I was able to log a support call with HP.

Turned out that whoever configured this system (it wasn't me!) had configured both ethernet ports with the same IP address, but TCP/IP services was enabling only one port. The result was that TCPIP$INET_* logicals were not being defined.

After removing the second IP interface definition (for the unused ethernet port) and rebooting, Advanced Server started working.

Thanks to all.
Jeremy Begg
Trusted Contributor

Re: Advanced Server fails to start on TCP/IP

See above.