- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Pathworks V6.1 with Windows 2003
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
Forums
Discussions
Discussions
Discussions
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
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
06-27-2005 05:39 AM
06-27-2005 05:39 AM
Rich Wingate
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2005 08:32 PM
06-27-2005 08:32 PM
Re: Pathworks V6.1 with Windows 2003
Rob.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2005 10:22 PM
06-27-2005 10:22 PM
Re: Pathworks V6.1 with Windows 2003
not sure if you are running an VAX or Alpha (you tell about Pathworks and Advanced Server). If on an Alpha, pls. upgrade to AdvancedServer V7.3A-Eco4, the licenses are the same not sure,
if Pathworks is supported with W2003.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2005 03:13 AM
06-28-2005 03:13 AM
Re: Pathworks V6.1 with Windows 2003
The SAM doesn't propogate to a member server. With admin, you log into the domain and are validated by a DC.
Is your W2K3 password possibly longer than the 14 character max allowed by Pathworks?
-Doug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 12:33 AM
06-29-2005 12:33 AM
Re: Pathworks V6.1 with Windows 2003
I have come across a couple references that state that PW61 is not officially certified with 2003 but that people have made it work. Unfortunately, I have not found any details. The SPD indicates that it will work with 2003, but the release notes never mention 2003. For right now, I am pretty much stuck with the software and licenses that I have, therefore no upgrades at this time.
I am running Alpha v7.1-2 in a cluster.
In response to Doug,
My validation failure occurs when I try to log onto the domain (from pathworks side). I found that I can use active directory to set up a share on the pathworks computer but then I cannot add users or groups to it. 2003 responds with a message that it cannot determine if the computer is joined to the domain.
My password is less than 14 characters.
Thanks Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 02:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 07:34 AM
06-29-2005 07:34 AM
Re: Pathworks V6.1 with Windows 2003
Do you know how I need to go about this? I thought this should be working by default. As of yet, I haven't found anything useful on the internet.
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 08:34 AM
06-29-2005 08:34 AM
Re: Pathworks V6.1 with Windows 2003
As I recall, you have to run REGEDIT32 and change the data of value
EnablePlainTextPassword to 1. Naturally, back up the registry before you do this;-)
I think it's in the H_KEY_LOCAL_MACHINE\SYSTEM\... key path in a couple of places so you can use ->Find to locate it. Please don't change the registry until you're sure this is what you need to do.
You might want to google for that key value, and check MSKB, too.
I am hoping maybe one of the HP guys will jump in.
-Doug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 06:54 PM
06-29-2005 06:54 PM
Re: Pathworks V6.1 with Windows 2003
The mainly trouble of pw and win2k/2k3/xp is login process. PW uses NT3/NT4 style while win 2k3 uses crypted password.
I don't know exact path in win2k3 so I can just give you some clue.
You have to open Control Panel, Administration tools, protection criteria and change enable server uncrypted password.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 04:02 AM
06-30-2005 04:02 AM
Re: Pathworks V6.1 with Windows 2003
Local Security Policy -> Local Policies -> Security Options -> Network Security: LAN Manager authentication level:
The default is LM & NTLM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 08:49 AM
06-30-2005 08:49 AM
Re: Pathworks V6.1 with Windows 2003
Thanks. I have it in the domain now. It boiled down to certain policies. I will document and post details tomorrow for future reference. Going home now.
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2005 02:15 AM
07-01-2005 02:15 AM
Re: Pathworks V6.1 with Windows 2003
1. Add "Everyone" groupt to the built-in "Pre-windows 2000 compatible access". I tried it. In the end it made no difference.
2. Group Policies:
Domain member: Digitally encrypt or sign secure channel data (always) - Enabled. I tried disabling, made no difference.
Microsoft network client: Digitally sign communications (always) - Enabled. I tried disabling, made no difference.
Microsoft network client: Send unencrypted password to third-party SMB servers - Disabled. I tried enabling, made no difference.
Microsoft network server: Digitally sign communications (always) - Disabled. This was the one. Disabling this allowed pathworks to authenticate in my domain.
Network access: Do not allow anonymous enumeration of SAM accounts - Disabled. Without this disabled, the pathworks server could not find the domain controller.
Network access: Do not allow anonymous enumeration of SAM accounts and shares - Disabled. Without this disabled, the pathworks server could not find the domain controller.
Network access: Let Everyone permissions apply to anonymous users - Disabled. This did not need to be enabled.
Network security: LAN Manager authentication level - Send NTLM resonse only. I tried setting to LM and NTLM, made no difference.
3. Useful research material:
MIT IS&T: Windows Server Platforms: Athentication and Security
KB 281648 Error Message: The Account is not Authorized to Login from This Station
KB 289655 HOW TO: Enable Null Session Shares on a Windows 2000-Based Computer
OpenVMS Technical Journal - Advanced Server for OpenVMS
Wizard - PATHWORKS COMERR domain name resolution
Wizard - PATHWORKS and Windows Server 2003
I hope this information will be useful to someone else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2005 02:16 AM
07-01-2005 02:16 AM