| Title: | PATHWORKS for OSF/1 |
| Notice: | see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX |
| Moderator: | CPEEDY::LONG |
| Created: | Thu Apr 22 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1874 |
| Total number of notes: | 6870 |
Hi,
Cust has a problem with pw osf v5.0f. (I have already sent out the
5.0g eco 2 patch) The cust system has started showing a problem with
syncronizing with his nt PDC. the system will not start netlogon.
Upon trying to start this the message
net error 53
The network path was not found, or the local server is not running.
Can anybody throw any light on this error as the users can still
connect to the server which has now been put into standalone (and tried
net account /role:backup). The server has been restarted several times
and the accounts database has been re-built and the server has still
not started netlogon.
PWRKSETUP CONFIG has also been run to re-config the server and still no
joy. Has anyone seen this or found a way round it as previous notes on
this seem to end inconclusivly.
Trev UK CSC.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1835.1 | Try re-adding the server to the domain | CPEEDY::GARDE | Tue Apr 29 1997 14:29 | 16 | |
It sounds like the v5.0f server is not able to communicate to the NT
server properly. One thing you can try is to make the v5.0f system a
PDC of its own domain. On the NT, remove the 5.0f system from the
domain using server manager.
Make sure that netlogon comes up ok when the v5.0f server is a PDC, and
if so, then change it to standalone again and have it rejoin the NT
domain. My guess is that the PATHWORKS server is out of synch with the
NT and cannot authenticate itself. Deleting and re-adding the server
will reset the server account.
- Ces
| |||||
| 1835.2 | Now working again. | KERNEL::BURNST | Wed Apr 30 1997 11:09 | 11 | |
Hi,
Thanks for the info. After trying that the unix box came up OK but the
net view commad works to sho the unix server. net view \\ntserver
came up again with a error 53.
The upshot of this was that there was a problem with the NT server and
seemed to get screwed up using netbuei whele not saying it had netbeui
loaded in the contol panel. Setting up netbeui again fixed the problem
so now all is working OK.
Trev.
| |||||