- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Advanced Server v7.3-A4 problem
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
тАО08-07-2007 11:03 PM
тАО08-07-2007 11:03 PM
Advanced Server v7.3-A4 problem
I have a domain win2003 active directory with n DC win2003 and 2 cluster OpenVms 7.3-1 with Advanced Server 7.3-A4.
The problem is:
when i use command line of Advanced Server (admin) return this messagge:
sho user
%PWRK-E-DCNOTFND, cannot find Primary Domain Controller for "USERDOMAIN"
What can i see or modify of configuration for resolve this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 12:00 AM
тАО08-08-2007 12:00 AM
Re: Advanced Server v7.3-A4 problem
Do you use LMHOSTS and/or WINS and are the configured correctly? Did it ever work?
Are messages in ADMIN SHO EVENT or in the logfiles?
We sometimes had similar problems and after long struggle it turns out to be a windows/network problem.
Btw, the current version is V7.3B and a Patch 5 kit.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 12:30 AM
тАО08-08-2007 12:30 AM
Re: Advanced Server v7.3-A4 problem
If i ping DC with role pdc emulator and other DC is ok.
if i want use lmhosts, how i configure this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 03:21 AM
тАО08-08-2007 03:21 AM
Re: Advanced Server v7.3-A4 problem
What's a Patch 5 kit?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 04:13 AM
тАО08-08-2007 04:13 AM
Re: Advanced Server v7.3-A4 problem
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 06:45 AM
тАО08-08-2007 06:45 AM
Re: Advanced Server v7.3-A4 problem
In Advanced Server's ADMIN/CONFIG, the LMHOSTS and WINS definitions are on the Transports page.
If that doesn't help;
The following has worked for me before to solve a problem like yours:
Remove the Advanced Server computer(s) from the 2003 DC/PDC.
Re-run @SYS$UPDATE:PWRK$CONFIG on the Alpha.
Change one of the values on the menu and change it back. Exit the menu.
When it asks if you want to "enter a new administrator's password now," do that (you can use the same password you have now.)
When finished it should rejoin the domain and the DC will assign a new ID.
If you're running the AS as BDC, you might consider changing its role to Member (see the documentation for a discussion of those concerns.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 08:19 AM
тАО08-08-2007 08:19 AM
Re: Advanced Server v7.3-A4 problem
Isn't AdvancedServer only supported as Memberserver in AD domains?
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 10:35 AM
тАО08-08-2007 10:35 AM
Re: Advanced Server v7.3-A4 problem
In which case the 2003 will run in 2000-Mixed or 2003-Interim mode, and the non-2003 servers will function like a BDC in a pre-AD domain (only 2003 can act as PDC.)
A member server can become part of the AD, but will not have DC server capability. e.g. it can offer local shares and some very limited domain services and it can't initiate changes to the AD.
My experience with using 2003's PDC emulation and leaving AS's as BDC has not been positive -- mostly replication problems, iirc -- so I always make them members. Then 2003 can run in "happy" mode (Windows Server 2003 functionality level.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2007 04:59 PM
тАО08-08-2007 04:59 PM
Re: Advanced Server v7.3-A4 problem
In my opinion.
1. Using wins is better than lmhosts.
2. Static records in wins only to be a AS cluster alias, and the rest DC, AS nodes will be registered dynamically. This is more correct.
3. Check
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 12:01 AM
тАО08-09-2007 12:01 AM
Re: Advanced Server v7.3-A4 problem
$ nbshow knbstatus
To search for the PDC of the domain ADOMAIN:
$ nbshow knbstatus adomain 1b
But due to a bug in NBSHOW, you have to verify the name you searched for is actually in the list of names returned because nbshow will fall back and search for
And I agree with earlier comments to avoid use of lmhosts and static WINS entries (except for the Advanced Server cluster alias name). Advanced Server will dynamically register its names, except the cluster alias name, as should the Windows systems.
Regards,
Paul