Pathworks32 v7.3

[Helen Mauger]

We are currently running OpenVMS V7.2-1, Advanced Server 3.51 for OpenVMS
PATHWORKS V6.0D for OpenVMS (Advanced Server)
and an NT4 network.

My local area network specialist wants to upgrade to Windows 2003. Is Windows 2003 supported by the latest Pathworks version - I do not see it mentioned in any documentation.

Also the Domain name will be changing - my OpenVMS specialist is on annual leave - Am I correct in thinking that he will not be able to simply change (in the advanced server configuration) the domain name - ie will he need to do a re-install

Last question

in TCPIP I see
Local host: GNSYA2 Domain: name.ISPname.co.uk

What impact is there if we change this to some other more meaningful fully qualified name

[Paul Nunez]

Hi Helen,

First, you've mentioned both the PATHWORKS client software - PATHWORKS32 - and the PATHWORKS server software - PATHWORKS for OpenVMS v6.0D.

The client software, PATHWORKS32, provides Windows systems with DECnet, LAT, PowerTerm terminal emulator, eXcursion X-Windows server, and some other utilities. Note that PATHWORKS32 client software is NOT required in order for your Windows clients to utilize PATHWORKS servers. The Windows clients can use the native Microsoft Network Client and TCP/IP to map drives/printers to the PATHWORKS servers.

With that said, PATHWORKS32 v7.3 does NOT support Windows 2003 (but, again, PATHWORKS32 is not required unless you want the Windows system to have DECnet, LAT, etc.). Last I heard, PATHWORKS32 product management had decided to qualify PATHWORKS32 on Windows 2003 Server but if/when that will happen is unknown to me.

On the server side, PATHWORKS for OpenVMS V6.0D was, obviously, built before Windows 2003 existed; therefore, it doesn't support Windows 2003 either. In fact, there is no version of PATHWORKS nor Advanced Server for OpenVMS which supports Windows 2003 at this time. My own testing with Advanced Server for OpenVMS v7.3A ECO1 (the latest version) and Windows 2003 Server uncovered several problems with the ADMIN command line interface that Advanced Server for OpenVMS uses to manage the server(s) and domain. Most of these could be avoided by using Windows utilities to manage the Advanced Server. Rudumentary testing showed that client access to file/print shares was NOT affected, however. Also, Windows 2003 is more secure out-of-the-box than Windows 2000. We know of one particular security policy which, if disabled, will prevent the PATHWORKS server from communicating with Windows 2003 domain controllers. That policy is Network Access: Allow anonymous SID/Name Translation. It must be enabled if you have PATHWORKS servers in the Windows 2003 domain.

Also, since Windows 2003 is unsupported at this time, it may be difficult (if not impossible) to get engineering support.

As for changing the DNS domain name on the OpenVMS system, PATHWORKS doesn't care one bit because, unlike Windows 2000/2003, PATHWORKS doesn't primarily use DNS for name resolution. PATHWORKS is equivalent to a Windows NT server (I can't emphasize this enough - PATHWORKS plays by the same rules as Windows NT v4), which primarily uses NetBIOS name resolution.

Hope this helps,

Paul Nunez
HP Services

[Craig Hamon]

I have no requirement for managing a Windows Domain from OpenVMS. All that is required is that the system be a member of a doamin that is managed by a Windows Server 2003? Is this possible?

[Paul Nunez]

Hi Craig,

Officially, there's no Windows 2003 support as yet.

However, I did some testing using the latest version of Advanced Server for OpenVMS - v7.3A ECO1 - and was able to join a W2K3 domain as a member server and rudimentary client testing was successful.

In order for Advanced Server to join and function w/i the W2K3 domain the following security policy must be enabled on all domain controllers in the domain:

Network Access: Allow anonymous SID/name translation


HTH,

Paul Nunez
HP Services

[Craig Hamon]

Thanks Paul,


I'm the network specialist that Helen was talking about.

What is the minimum version of Advanced Server for OpenVMS that supports Windows 2000 domains?

As previously stated I only require my OpenVMS system to be a domain member and I have no requirement for managing a domain from OpenVMS.

Regards

Craig Hamon APS

[Paul Nunez]

Hi,

The latest version of Advanced Server for OpenVMS that supports Windows 2000 is v7.3A ECO1. Also, its sister product- PATHWORKS fo OpenVMS v6.1 - supports W2K.

See the SPD (covering both) at:

http://h18000.www1.hp.com/info/SP3050/SP3050PF.PDF

Paul Nunez