- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Advanced server 7.3A/B can't find domain controlle...
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-28-2006 11:35 PM
тАО12-28-2006 11:35 PM
Advanced server 7.3A/B can't find domain controller
$ Admin show users
gives "%PWRK-E-DCNOTFND, cannot find Primary Domain Controller for "CSPWRK01" "
although the server itself has been set up as PDC for that domain.
I updated Advanced server to V7.3B and also reconfigured it, but that didn't suceed.
The pathworks-logfiles do not give any special error-message, all required processes are running.
Only workaround is in the moment that users who want to connect to any share have to use the username administrator (and the password of course).
Any hints where I can search ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2006 12:04 AM
тАО12-30-2006 12:04 AM
Re: Advanced server 7.3A/B can't find domain controller
IIRC, Pathworks can only be a member server, not a Domain Controller, in an XP/W2k3 domain.
Something to do with Ms moving the goal posts and not telling anyone where they were moved to.
JT:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2007 01:44 AM
тАО01-02-2007 01:44 AM
Re: Advanced server 7.3A/B can't find domain controller
thanks for your answer.
The pathworks-domain structure we are using is a very simple one : the pathworks-server is set up as PDC for CSPWRK01 (no BDC exists for that domain), there are no other domain members. The XP-clients which want to map a share on this server are member of another domain.
This configuration worked fine before I made the system updates last week.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2007 03:12 AM
тАО01-05-2007 03:12 AM
Re: Advanced server 7.3A/B can't find domain controller
You didn't add or modify any hardware in this update period, do you ?
There is also no modification made to the netwerk ?
AvR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2007 11:38 PM
тАО01-07-2007 11:38 PM
Re: Advanced server 7.3A/B can't find domain controller
your guess is right, besides the software-updates (VMS-patches) I also installed new network-cards to use LAN failover. The new cards are defined as LLA-0, this has also been modified in the logicals which advanced server uses (PWRK$NBDAEMON_DEVICE and PWRK$KNBDAEMON_DEVICE) to point to LLA0 instead of EIA0 (the KNBDAEMON-process seems to work fine with these settings). This change was also one of my guesses which could have influenced the problem, therefore I have modified it back test-wise, but that didn't succeed.
In my whole paper documentation about pathworks problems I found an old article about a similar problem (but with an external Windows NT server as domain controller) where the solution was to add a LMHOSTS entry for the PDC. I will try this the next time when I'm able to restart Pathworks (it is used in a 7x24 production area here). In the moment, I can still live with the mentioned workaround.