Pathworks on Windows XP

[Molly Peet]

I have an existing PC running Windows 2000 with a PWLMXXXCA07.02 license, an Alpha 400 running OpenVMS 6.2, Pathworks 5.*(y2K compliant patches) on the Alpha. I want to upgrade the PC with WIndows XP Service Pack 2. WIll the current licensing on the Alpha 400 support this? If not, is there a solution without upgrading the VMS on the Alpha?

[Karl Rohwedder]

Molly, check the pathworks pages here (http://h71000.www7.hp.com/pathworks/pw_win2000_stat.html) for more information. Pathworks V5 was only supported for VMS v5.5-2.
With a CA07.02 license you can run up to AdvancedServer V7.2,the current version is V7.3A-Eco4, which needs a CA07.03 license.
Beware that AdvancedServer will not be ported to IA64 and is end-of-life. It will be replaced with a supported SAMBA version (currently on fieldtest).

[Andy Bustamante]

Next question, which transport protocol are you using for Pathworks. If you're using TCP/IP, you can configure the XP PC for file sharing without loading the PW 32 client.

On the other hand, HP does provide upgrade licenses for Pathworks. You could make a business case by moving to the latest version of Advanced Server and release of VMS that's under support.


Andy

[Molly Peet]

Thanks for the replies. Unfortunately it is not possible for me to upgrade the Alpha so how do I go about configuring the XP PC for file sharing without loading the PW 32 client. We do have TCP/IP configured on the alpha server.

[Andy Bustamante · Accepted solution]

Under ADMIN/CONFIG you can follow the menu and select TCPIP as a transport, the run @sys$manager:tcpip$config look for "Optional Components." You want to find the PWIP Driver driver and enable it. Restart TCPIP and Pathworks.

You can enable both DECnet and TCPIP or select one protocol.

I believe UCX 4.2 supported this driver as well, but it's been a while since I've touched UCX.


Andy

[Molly Peet]

I have enabled the TCPIP transport, started the PWIP, configured through UCX and think that I have the Alpha ready to accept file mappings and when I try to map to the Alpha I get a message that the server cannot perform the specified action. On the Alpha sid it rejects the connection. Also when I browse the network I cannot see the Alpha on it. Any suggessions are welcome!

[Doug Phillips]

In the XP's Local Security Policy -> Local Policies -> Security Options,

Set:

Microsoft network client: Digitally sign communications (always) - Disabled

Microsoft network client: Send unencrypted password to third-party SMB servers - Enabled

and see if that helps.

You'd be better off at least upgrading PW to 6.0 if you can't go to Advanced Server and you can't upgrade VMS. If you can get a PWLMXXXCA07.03 license, VMS6.2 will run PW 6.1 which works better with XP.

[Molly Peet]

Thank you all for your input and help. I am still fighting to get the XP client to connect. It may be the managed CISCO switch between two different IP subnets or the parameters in XP. I had to turn off the Pathworks license server manager to get the shares working between matching subnets. Thanks again.

[Andy Bustamante]

>>> two different IP subnets

Please try adding LMHOSTS/HOST table entries in on the XP PC.

Andy