- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: PATHWORKS V6.1 fails to talk over IP (t_bind t...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2008 05:16 AM
тАО12-15-2008 05:16 AM
While both the IP stack (telnet, ftp) and PATHWORKS (via DECnet and NetBEUI) work fine, I could net get PATHWORKS to talk to the client PCs via IP.
KNBDAEMON fails with:
bind_a_port(137): t_bind failed: 8
The PWIP ACP logs this message each time KNBDAEMON tries to start:
bindReq : *** IO$_SETMODE set tcp options (NODELAY) call failed *** : 20
(I attach the contents of both logfiles for reference)
What I tried so far:
- define logical names PWRK$KNBDAEMON_DEVICE and _IPADDR
- defined TCPIP$INET_* logical names identically to the existing UCX$INET_* logical names (just in case...)
- checked that port 137 (and 139) are not used by something else ($ UCX SHO DEV only shows two devices - one for port 23 [telnet] and one for port 21 [ftp])
- tried suggestions found elsewhere like shutting down PATHWORKS, restarting the PWIP ACP and starting PATHWORKS again.
I *suspect* that the root cause is in UCX because of the message in the PWIPACP log file. Status code 20 (decimal) would be %SYSTEM-F-BADPARAM. On the other hand, the NODELAY option for the tcp protocol is listed in UCX HELP SET PROTOCOL so it should be known...
I've collected quite some troubleshooting material over the years but am unable to come up with anything useful in this case.
Any ideas (beyond moving to OpenVMS V7.3 and the latest and greatest IP stack - this is not an option)?
Thanks for all and any help,
Hans.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2008 09:38 AM
тАО12-15-2008 09:38 AM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
Andy Bustamante
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2008 02:32 PM
тАО12-15-2008 02:32 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
> There's an optional component to run Pathworks over tcp/ip that needs to be
> enabled. Did you enable this service?
Yes, that's the PWIP ACP. It is running and produces the bindReq error message I mentioned in the UCX$PWIPACP_XXXXX.LOG log file.
Hans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2008 02:38 PM
тАО12-15-2008 02:38 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
Andy Bustamante
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2008 03:50 PM
тАО12-15-2008 03:50 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
> Did you use ADMIN/CONFIG to enable TCPIP as a network transport in the
> Pathworks configuration?
Yes, I did (see the KNBDAEMON error).
Any more ideas?
Thanks,
Hans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2008 10:53 AM
тАО12-16-2008 10:53 AM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
The SPD http://docs.hp.com/en/12831/Advancedserver.pdf for Pathworks 6.1 shows VMS 7.3-2 as the minimum supported version. That doesn't mean it won't run, but you're having issues and this isn't a supported configuration.
You could revert back to PW 5.0c or a 5.1 version. These should both work with UCX. Another thing would be to check ftp.itrc.hp.com and make sure the UCX eco is the most current.
Good luck,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2008 10:58 AM
тАО12-16-2008 10:58 AM
SolutionFound some history on this in notes and the workaround is to replace the sys$common:[sys$ldr]ucx$pwipdriver.exe and sys$common:[sysexe]ucx$pwipacp.exe images with the same images from the ucx 4.2 eco4 kit.
It was elevated to UCX engineering so I suspect a fix is available...somewhere.
HTH,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2008 01:00 PM
тАО12-16-2008 01:00 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
> The SPD http://docs.hp.com/en/12831/Advancedserver.pdf
> for Pathworks 6.1 shows VMS 7.3-2 as the minimum supported version.
this is true for Advanced Server V7.3B. PATHWORKS V6.1, however, is also supported on OpenVMS 6.2 VAX and Alpha (look a bit further down in the SPD). Also, UCX V4.2 is listed as the appropriate version for OpenVMS V6.2 (Table 3, page 32).
In the meantime, Paul has posted the solution for the problem, see his explanations.
Thanks & regards,
Hans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2008 01:15 PM
тАО12-16-2008 01:15 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
you definitely made my day/week/month! :-)
> ...the workaround is to replace the sys$common:[sys$ldr]ucx$pwipdriver.exe
> and sys$common:[sysexe]ucx$pwipacp.exe images with the same images
> from the ucx 4.2 eco4 kit.
Fortunately, I still had an ECO 4 kit spinning around on an RZ40 disk :-)
I extracted the images you mentioned, put them into place, rebooted and... voila!
E:\Hans>dir \\10.0.0.31\pwutil
Datentr├Г┬дger in Laufwerk \\10.0.0.31\pwutil: ist VAXVMS062
Volumeseriennummer: 0000-0001
Verzeichnis von \\10.0.0.31\pwutil
14.12.2008 02:34
14.12.2008 02:34 431 README.TXT
14.12.2008 02:34
1 Datei(en) 1.967 Bytes
2 Verzeichnis(se), 989.749.248 Bytes frei
E:\Hans>
I still get a "Connect Request failed" error with a 556 status (device timeout) logged in the PWIPACP log file, but this doesn't seem to impact access to the PATHWORKS shares over IP.
Thanks much for your help!
Best regards,
Hans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2008 01:18 PM
тАО12-16-2008 01:18 PM
Re: PATHWORKS V6.1 fails to talk over IP (t_bind to port 137 failed)
Many thanks & best regards from Austria,
Hans.