Pathworks V6.0C - "Network path was not found" error

[Dan Kingsbury]

After trouble with a disk drive, we restored PWRK$ROOT from a backup tape, and have not been able to get the shared directories to work.

From my Windows 2000 machine, when I click on the shared folder in "My Network Places", I get an error message which says "\\Sales2\TRANSFER is not accessible. The network name cannot be found."

I can find no description of this error message in any of the Pathworks (Advanced Server) documentation.

We have licenses for newer versions of Pathworks (up to 7.2) and tried to install 7.2 but had trouble with it so reverted to the backup tape which was working up until last week. I inherited this system from someone else and do not know all that much about Pathworks.

But getting the Pathworks operational again *should* be easy - it worked for years and not much has changed (different disk drive, different system password).

Here's some displays of how the system is configured:

XDN\\SALES2> login administrator
Password:
The server \\XDN_SERVER1 successfully logged you on as Administrator.
Your privilege level on domain XDN is ADMIN.
The last time you logged on was 04/14/05 01:52 PM.

XDN\\SALES2> show computer

Computers in domain "XDN":

Computer Type Description
-------------------- --------------------------- ---------------------------------------------------------------------------------
[PD] XDN_SERVER1 Windows NT 4.0 Primary XDN PDC
[BD] SALES2 OpenVMS 3.51 Backup Pathworks 6.0 Advanced Server
[BD] SALES2_ALIAS OpenVMS 3.51 Backup PATHWORKS V6.0C for OpenVMS (Alias)
[ws] SALES_PC1 Windows NT Workstation or Server
[WS] SALES_PC1A Windows NT 5.0 Workstation
[WS] SUPPORT Windows NT 5.0 Workstation
(etc)

Total of 20 computers

XDN\\SALES2> show computer ndc_server1 /ful

Computers in domain "XDN":

Computer Type Description
-------------------- --------------------------- ---------------------------------------------------------------------------------
[PD] XDN_SERVER1 Windows NT 4.0 Primary XDN PDC
Sessions: 16 Open Files: 90 File Locks: 6 Open Named Pipes: 8

Total of 1 computer

XDN\\SALES2> show share transfer /full

Shared resources on server "SALES2":

Name Type Description
------------ --------- -------------------------------------------------------
TRANSFER Directory
Path: DATADISK:[PC_TRANSFER]
Connections: Current: 0, Maximum: No limit
RMS file format: Stream
Directory Permissions: System: RWED, Owner: RWED, Group: RWED, World: RE
File Permissions: System: RWD, Owner: RWD, Group: RWD, World: R
Share Permissions:
Everyone Full Control

Total of 1 share

XDN\\SALES2>
XDN\\SALES2> show file transfer
%PWRK-E-SEARCHFAIL, error searching for "\\SALES2\TRANSFER\"
-LM-E-ERROR_BAD_NET_N, this network name cannot be found

XDN\\SALES2> exit
$ dire DATADISK:[PC_TRANSFER]

Directory DATADISK:[PC_TRANSFER]

000811.DOC;1 1/9

Total of 1 file, 1/9 blocks.
$

I believe that the ERROR_BAD_NET_N message I get from the "ADMINISTER SHOW FILE" command is probably the equivalent of the "Network path was not found" error that I get from Windows 2000. This doesn't even have to go across the network and it can't find it. I'm running with full privileges and the protections on the share (DATADISK:[PC_TRANSFER] seem to be adequate.)

So what am I doing wrong?

I would gladly replace it all with Samba if that's easier, but I cannot seem to find any instructions on how to install and configure Samba for OpenVMS. I can convert hex to octal to decimal in my head, but I have trouble translating a unix-to-windows interface to a OpenVMS-to-windows interface.

Thanks,

Dan Kingsbury

[Andy Bustamante]

You said the disk had been restored from tape. I'm assuming that Pathworks was running and the disk was dismounted and remounted.

You can either stop and start Pathworks or try this in admin: set computer Node_name_goes_ here /autoshare_sync

This will pick up disks that have added since Pathworks was started.

[Dan Kingsbury]

> You said the disk had been restored from tape. I'm assuming that Pathworks
> was running and the disk was dismounted and remounted.

The backups were done while Pathworks was running. The system has been rebooted several times since then for AUTOGEN, etc. so the disk was implicitly dismounted and remounted each time. I've also invoked @SUS$STARTUP:PWRK$SHUTDOWN followed by @SYS$STARTUP:PWRK$STARTUP several times to see if that would make any difference (it didn't.)

> You can either stop and start Pathworks or try this in admin:
> set computer Node_name_goes_ here /autoshare_sync
>
> This will pick up disks that have added since Pathworks was started.

Thanks for the suggestion. I just tried this, but I still get the same error:

XDN\\SALES2> set computer sales2 /autoshare_sync
%PWRK-S-AUTOSHRSYNCHED, autoshare synchronization was successful

XDN\\SALES2> show file transfer
%PWRK-E-SEARCHFAIL, error searching for "\\SALES2\TRANSFER\"
-LM-E-ERROR_BAD_NET_N, this network name cannot be found

[Karl Rohwedder]

How up-to-date was the backup tape? Were ther perhaps changes in e.g. LMHOSTS.?
Does SHOW EVENT/FULL/SINCE... show anything or ADMIN /ANALYZE?

regards Kalle

[Antoniov.]

Hi Dan,
sorry if I ask you for obvious stuff.
Your share transfer is
DATADISK:[PC_TRANSFER] where DATADISK is a logical name. Did you change some logical definition (e.g. new process definition)?
Also you can remove the share then insert again.

Antonio Vigliotti

[Anton van Ruitenbeek]

Pathworks is a pain in the as when it comes to configuration.
Yes I'm using it for more then 10 years and are very happy with it.
When something weard happens, almost do the first thing: @SYS$UPDATE:PWRK$CONFIG
Normaly it wil work after this.
As I recall you're comments, the system can be rebooted eny time (now), so I think this will be the first thing to do.
Other problem is probably the PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB. file.
You can rename this one (eg SHAREDB._20050415) and reconfig but don't start. Rename the new SHAREDB. to .NEW and ._20050415 to . Start AS again.

AvR

[Andy Bustamante]

Okay I read the error this time.

You're trying to do a show file on share.

If you try this:

XDN\\SALES2> show file \\sales2\transfer\000811.DOC /full

Do you get a report on the f ile. Can your client map the share offered?

[Bill Hall]

Its been a while since I've worked on your version of PW, but... I've always kept my PW servers in their own resource domains (and used trusts to true Windows only domains for user authentication). That said, my first thought was that you restored a backup that contained a snapshot of the SAM that is "old" and out of synch with the PDC's SAM. Try to synchronize the domain with either Server MAnager from the Windows side or from PW:

XDN\\SALES2>SET COMPUTER XDN_SERVER1 /ACCOUNT_SYNCHRONIZE

This might force the local copy of the SAM on SALES2 back into synch with XDN_SERVER1. I won't be suprised if you have to remove SALES2 from the domain and then add it back into the domain. I suspect that the computer account password for SALES2 in the SAM of SALES2 is out of synch with the SAM on the PDC.

[Dan Kingsbury]

to Rohwedder, Karl:

Wow! Lots of good suggestions. Let me address each one of them...

The backup tape was NOT recent - nearly a year old. It was thought that the system drive did not change much. The jury is still out on this one (as I still don't know if the changes that have caused this problem are on the Windows or OpenVMS end.)

Pardon my lack of Windows skills, I'm a VMS bigot. I don't know much about LMHOSTS, but the definition I found says its for wide area network name resolution. All these systems are on a LAN (or effectively via a VPN). The IP address of SALES2 is in the HOSTS file on the XDN_SERVER1 machine and I can PING from XDN_SERVER1 to SALES2 via its numeric IP address or via its symbolic name SALES2 which is defined in the Windows NT HOSTS file. Would it be better to define this in LMHOSTS instead (or in addition)????

All of the IP addresses are static and remain the same, as do the names. There may be an issue with DNS that I am having our network guy look into, but he's only in on the weekend. Briefly, we changed our firewall from a Windows NT server which I'm told was also providing DNS to a D-Link VPN Firewall which does not provide DNS. It was my thought that the HOSTS definition should suffice, but who knows? Would a LMHOSTS solve this?

SHOW/EVENT/FULL/SINCE shows nothing but multiple entries of "The Event log service was started." There are many years of entries from before the troubles occurred, and since then just the above plus several entries of the following format:

I 04/13/05 01:49:16 AM NETLOGON None 5715 N/A SALES2
NET5715: The partial synchronization replication of the SAM database from the
domain controller \\XDN_SERVER1 completed successfully. 11 delta(s) is(are)
applied to the database.

ADMIN/ANALYZE gives messages only of the following types:

Event: Master Process starting
Event: LANman Controller process
Event: PATHWORKS Monitor process starting

Thank you Kalle.

Dan Kingsbury

[Dan Kingsbury]

Antoniov,

Please, no applogies are necessary, you have asked logical questions (no pun intended).

DATADISK is an executive mode, concealed, system logical name...

$ show logical/full datadisk
"DATADISK" [exec] = "DKA600:" [concealed] (LNM$SYSTEM_TABLE)

As far as changing a process logical, I don't see how that would affect Pathworks which has its own processes, for which I have not changed any logicals (that I know of, anyway.)

I did try removing and then redefining the share, but it didn't help. I don't think the problem is in the area of the share definition from the nature of the error message, and since I also cannot access the other shares which Pathworks defines by default (Netlogon, Pwlic, Pwlicense, Pwutil, and Users) - and one would think that the software would install them correctly. When I try to access any of these, I get the same "Network path was not found" error.

Thank you Antonio. Any other ideas or suggestions would be appreciated.

Dan Kingsbury

[Dan Kingsbury]

reply to Anton van Ruitenbeek:

I certainly have to agree about Pathworks being a pain to configure.

I have run @SYS$UPDATE:PWRK$CONFIG a couple of times. First, to change the Administrator password which had changed on the NT machine, but not been used from the VMS system for a couple of years. When I first tried to use ADMIN LOGIN ADMINISTRATOR it didn't work, so I ran PWRK$CONFIG to update the password.

I also thought I had to update the number of clients etc to get Pathworks to start. (PWRK$STARTUP had been failing with "%PWRK-F-NOCLIENTS, insufficient resources to support any clients". This was because of an incompatibility between the number of clients in ADMIN/CONFIG and the value MIN_WSMAX in MODPARAMS.DAT, which had been restored from an old system tape. I found that the MIN_WSMAX value specified by PATHWORKS ADMIN/CONFIG was being overriddent by a much larger value from the earlier tape that was causing "insufficient resources". When the earlier MIN_WSMAX was deleted, and AUTOGEN was re-run, and the system rebooted, the problem resolved. Note that PPWRK$ROOT is not on the system disk that was restored.)

Here's what I get when I run PWRK$CONFIG:

PATHWORKS V6.0C for OpenVMS is presently configured to run as follows:

1. Run the license server: NO
2. Enable Timesource service: YES
3. Enable Alerter service: YES
3a. Alert user names: administrator,d_kingsbury
4. Enable Netlogon service: YES
5. Advanced Server domain: XDN
6. Advanced Server role: BACKUP
7. Advanced Server computer name: SALES2
7a. PATHWORKS OpenVMS cluster alias: SALES2_ALIAS
8. Server announce comment: Pathworks 6.0 Advanced Server
Enter item number, or RETURN to use these values [DONE]:

Is this what you were talking about, or should I have answered Yes to "Do you want to change the server configuration parameters now?"

Also, earlier it says...

SALES2 is currently configured to
+ support 25 PC clients
+ use the following transport(s): DECnet, TCP/IP

I know Netbeui can be added as well, but the above is the way its always been configured.

I'm not sure what to do with the SHAREDB. files...

Directory DKA600:[PWRK$ROOT.LANMAN.DATAFILES]

SHAREDB.;1 1440/1440 3-MAR-2000 18:26:59.35 [SYSTEM]
SHAREDB.NEW;1 1440/1440 18-AUG-2003 11:39:34.12 [SYSTEM]

Total of 2 files, 2880/2880 blocks.

Why is there a .NEW file, and should I be using it?

Thanks for your help Anton.

Dan Kingsbury

[Dan Kingsbury]

reply to Andy Bustamante's second message:

$ admin
XDN\\SALES2> login administrator
Password:
The server \\XDN_SERVER1 successfully logged you on as Administrator.
Your privilege level on domain XDN is ADMIN.
The last time you logged on was 04/15/05 04:26 PM.

XDN\\SALES2> show file \\sales2\transfer\000811.DOC /full
%PWRK-E-SEARCHFAIL, error searching for "\\SALES2\TRANSFER\000811.DOC"
-LM-E-ERROR_BAD_NET_N, this network name cannot be found

That's all it displays.

I used this example, because I thought it demonstrated that the same error occurs from the OpenVMS end of the connection as is displayed on the Windows end. That is, something to do with "Network Name" or "Network Path".

The client does not see any of the files in the share. When I try to open the share, it just gets one of these error messages. The share names are visible however (Netlogon, Pwlic, Pwlicense, Pwutil, TRANSFER, and Users) from any of the Windows-2000 or Win-XP machines on the LAN.

Thanks for your persistence in trying to help, Andy.

Dan Kingsbury

[Dan Kingsbury]

reply to Bill Hall:

Thanks for the suggestions.

I tried "SET COMPUTER XDN_SERVER1 /ACCOUNT_SYNCHRONIZE" but it didn't seem to help.

I thought it was the passwords at first, but the fact that I could LOGIN and do SHOW COMPUTER and SHOW USERS and see information from the NT Server convinced me that this wasn't the problem.

What was restored was not the PWRK$ROOT, just the operating system (which included SYS$SYSTEM:PWRK$*.EXE, SYS$STARTUP:PWRK$*.COM, and the all important SYS$MANAGER:PWRK$DEFINE_ROOT.COM file.)

Thanks again.

Dan Kingsbury

[Dan Kingsbury]

And now for the resolution:

I got to thinking about the lack of a DNS server causing a problem, and it didn't make all that much sense, since SALES2 is defined in HOSTS on XDN_SERVER1 and on my Windows 2000 machine and in PWRK$ROOT:[LANMAN]LMHOSTS, and although I'm not well read on Pathworks, I don't remember seeing anything about having to have a DNS server, and Pathworks worked for us for years before we had a DNS server, so I cancelled the visit this weekend by our local network expert.

I re-installed V6.0C of Pathworks, but it looks like all it did was add an extra version of most of the SYS$SYSTEM:PWRK$*.EXE and SYS$STARTUP:PWRK$*.COM files (there seem to be a few files in each directory that have only 1 version) so this didn't seem to help.

I renamed PWRK$ROOT.DIR and ran @SYS$UPDATE:PWRK$CONFIG.COM and answered the questions to get the same configuration as it had before. It created a new configuration directory tree. After Pathworks restarted, Windows was able to access the shares that Pathworks creates by default (netlogin, pwlic, pwlicense, pwutil and users) which could not be accessed before. But it won't let me add TRANSFER as a share. It gets the following error message:

XDN\\SALES2> add share/dir transfer DATADISK:[PC_TRANSFER]
%PWRK-E-ERRADDSHARE, error adding share "TRANSFER"
-LM-E-NERR_UNKNOWNDEV, the device or directory does not exist

I removed the ACE's from PC_TRANSFER.DIR in case they were messed up, by running SYS$SYSTEM:PWRK$DELETEACE, but that didn't help as I got the same error on trying to ADD SHARE. I also got the same error when specifying DKA600:[PC_TRANSFER] instead of DATADISK:[PC_TRANSFER].

I copied saved SHAREDB. from saved directory tree to PWRK$ROOT:[LANMAN.DATAFILES] and restarted with @SYS$STARTUP:PWRK$STARTUP. Now the TRANSFER folder shows up in "My Network Places" but when I click on TRANSFER, I still get the error...

\\Sales2\TRANSFER is not accessible. The network name cannot be found.

But, all of the other default share folders are still accessible.

I tried removing and re-adding TRANSFER...

XDN\\SALES2> remove share transfer
Do you really want to remove share "TRANSFER" [YES or NO] (YES) : y
%PWRK-S-SHAREREM, share "TRANSFER" removed from server "SALES2"
XDN\\SALES2> add share /dir transfer datadisk:[pc_transfer]
%PWRK-E-ERRADDSHARE, error adding share "TRANSFER"
-LM-E-NERR_UNKNOWNDEV, the device or directory does not exist

I tried using SALES2$DKA600: instead of DATADISK in the share directory specification and it worked...

XDN\\SALES2> add share transfer SALES2$DKA600:[PC_TRANSFER]

Apparently it doesn't like the logical name "DATADISK" in the share specification, even though that was what worked for the last 9 years.

When I restored the system disk, I enabled cluster support. After this change, Pathworks wouldn't work with DKA600: -- it needed to be SALES2$DKA600:.

I redefined the exec mode logical name as follows...

$ define/SYS/EXEC DATADISK SALES2$DKA600: /translation=conceal

And then the original share definition worked...

XDN\\SALES2> add share transfer datadisk:[pc_transfer]
%PWRK-S-SHAREADD, share "TRANSFER" added on server "SALES2"

I guess this is just a Pathworks thing, because I find that the following 2 commands produce the same results:

$ dire dka600:[pc_transfer]
$ dire sales2$dka600:[pc_transfer]

One last problem I encountered, was that Sales2alias worked OK whereas Sales2 did not -- it gets this error:

\\Sales2\TRANSFER is not accessible. The network resource type is not correct.

This is bizarre. This happens when I access \\Sales2\Transfer (fails), but not when I access \\Sales2alias\Transfer (works).

Tried the following....

XDN\\SALES2> set computer xdn_server1 /account_sync
Resynchronizing the "XDN" domain may take a few minutes.
Do you want to continue with the synchronization [YES or NO] (YES) :
%PWRK-S-ACCSYNCHED, account synchronization was successfully initiated

XDN\\SALES2> set computer sales2 /autoshare_sync
%PWRK-S-AUTOSHRSYNCHED, autoshare synchronization was successful

...but this didn't seem to help.

Removed SALES2 from PWRK$ROOT:[LANMAN]LMHOSTS. No change.

Re-ran @SYS$STARTUP:PWRK$STARTUP. Now both \\Sales2\Transfer and
\\Sales2alias\Transfer work. So apparently it was not necessary to have SALES2 in LMHOSTS, and the restart of Pathworks helped eliminate some condusion it had.

I also tried removing XDN_SERVER1 from LMHOSTS and got the errors...

\\Sales2\TRANSFER is not accessible. The network path was not found.
\\Sales2_alias\TRANSFER is not accessible. The remote computer is not available.

I restored XDN_SERVER1 definition to LMHOSTS and I can again access Sales2 and Sales2_alias from the Windows machine, along with all of the share folders defined on SALES2.

This has been a long process, and I've written it up as best I could (leaving out most of the nonsense, dead-ends that I ran into) in hopes that it may help someone else.

Best regards,

Dan Kingsbury

[Jan van den Ende]

Dan,

if I have interpreted your entire solition story correct, then there might be one more point:


I redefined the exec mode logical name as follows...

$ define/SYS/EXEC DATADISK SALES2$DKA600: /translation=conceal

And then the original share definition worked...


and


$ dire dka600:[pc_transfer]
$ dire sales2$dka600:[pc_transfer]


Obviously you have SYSGEN ALLOCLASS = 2

I would really suggest you re-define DATADISK to be $2$DKA600: instead of SALES2$DKA600:
That what ALLOCLASS was invented for!

Disclaimer: should it NOT work, it is your time I am spending, and there will be no compensation! :-(

-- reading back, the most surprising thing (to me at least) is that it DID work before with the unqualified DKAxxx definition!


Mayby [PC_TRANSFER] used to be located on a drive DKxyyy of which the entire cluster only contained ONE occurrence, but now your cluster contains more than one DKA600, so now you need qualification to get a unique specification?


Success!

Proost.

Have one on me.

Jan

[Dan Kingsbury]

reply to Jan van den Ende:

This computer had been used for testing in the past and at one point was clustered. Later clustering was disabled, and I just turned it back on so I could see if it will talk to the Itanium system we just got.

ALLOCLASS was set to 0, and there is no indication in any of the old MODPARAMS.DAT files (these haven't been purged since late 1997) that it was ever anything other than zero.

I don't find it surprising that it worked with "DKA600:" when it wasn't clustered and with ALLOCLASS=0. Why shuoldn't it?

Regarding your speculation, it could have happened that way, but it didn't. [PC_TRANSFER] was always on "DKA600:" and there is no indication in any of the older command files that it was ever referred to by "SALES2$DKA600:" or $2$DKA600 or anything else like that.

These were things I had not thuoght about (and might have to do so before completing the clustering of SALES2 (Alpha) with the Itanium), so thank you for bringing them to my attention, Jan.

Dan Kingsbury

P.S.

I guess what I'd like to see from the Pathworks development team (if they see this) is that Pathworks should be a little smarter about this type of situation. (Although they could probably say the same thing about me.:-)

I think Pathworks should recognize that something is missing and give a better, more explicit error message, or the message should be documented better. The only mention in the Pathworks manuals (or anywhere known to Google) about "NERR_UNKNOWNDEV" is regarding "Attempts to Share an ISO-9660 CD ROM", so one might say the manual is a little weak in this area.

[Anton van Ruitenbeek]

Dan,

I still think IT is confused. I had also sometimes problems when I moved toward and back from cluster, clustermember, single node without the clusterbit on.

Youre sure the logicals and devices are setup correctly before starting AS ?

Possible you get a good result if you rename/(re)move the LAN configuration info. (You know, the LSA. , ACL., BUILTIN., SHAREDB., .)
Make sure the logical DATADISK is correctly setup (before starting AS).
Execute the configuration again.
Try to add the share manualy. If it works, stop AS, moveback the needed old datafiles. Check again. If not anymore, I think de SHAREDB. file is corrupt. I never had seen this but everyting is possible.

AvR