| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
Customer has a VAX with OpenVMS 6.2 and PATHWORKS for OpenVMS 5.0D eco3 configured as a standalone server. Only protocol used is TCP/IP with Multinet 3.3 on the VMS server. PDC is a WNT V4.0 server reachable only through routed IP. She has used the articles we have for integration of PW/VMS servers and WNT PDC, and additionally set up according to the article: [PW-VMS]V5 Implementing WAN Domain Using TCP/IP LMHOSTS These articles have worked well for most customers, but when she tries to promote the PW server to BDC, she gets net 2453, unable to find PDC. Items we have checked: guest, admin, administrator, server accounts domain setting and every line in lanman.ini net error (none) event log (nothing) VAX lmhosts file Other info: PDC IP address is 198.174.10.77 Subnet mask is 255.255.255.0 VAX IP address is 204.221.0.2 Subnet mask is 255.255.255.0 Router IP addr is 204.221.0.1 PDC and VAX use DNS Ping between systems by name is no problem Net logon from VAX fails with "logged on standalone" Net view doesn't see PDC Net view \\PDC shows the shares on the PDC Connect to share from PDC gets "network path not found" with and without lmhosts file on PDC Any ideas? Lew
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4209.1 | CPEEDY::wells.lkg.dec.com::wells | Phil Wells | Tue Mar 18 1997 10:24 | 22 | |
The lmhost file should have one or more entries that look something like 102.54.94.97 rhino #PRE #DOM:networking #net group's DC where "102.54.94.97" equals the PDC address "rhino" equals the pdc (or bdc) name "networking" equals the domain name Get a lan trace. You should see a UDP datagram to the PDCs internet address and not a broadcast datagram (internet address ff.ff.ff.ff). You may see both which is ok. I think I understand that you are currently standalone server. Do have an admin account with the same password on both the PDC and the standalone server? Are you logged into this account when you change the role? Can you change role to member server? If so, does replication happen? | |||||
| 4209.2 | Thanks | VMSNET::L_GULICK | Lew Gulick | Tue Mar 18 1997 11:17 | 40 |
Phil, >The lmhost file should have one or more entries that look something >like > >102.54.94.97 rhino #PRE #DOM:networking #net group's DC > >where > >"102.54.94.97" equals the PDC address >"rhino" equals the pdc (or bdc) name >"networking" equals the domain name Checked this item-by-item with her (not logged in myself). It's clear there is something like this wrong. >Get a lan trace. You should see a UDP datagram to the PDCs internet >address and not a broadcast datagram (internet address ff.ff.ff.ff). >You may see both which is ok. This is the next step, but not easy at many sites. >I think I understand that you are currently standalone server. Do >have an admin account with the same password on both the PDC and the >standalone server? Are you logged into this account when you change >the role? Yes; logged in as admin, but only standalone, since it couldn't find the PDC. The message back for any role change is net2453 "Unable to find the domain controller for this domain". Member or backup is the same. Not being there to see the lmhosts, etc. myself, I can't say she's not overlooking something in there. I will try to log in to the site and then go for a LAN trace. Thanks, Lew | |||||