Pathworks Directory Shares nolonger available

[Rick Watts_1]

Not sure what has changed but we are having issues with all the pathwork shares.

Alpha DS20E, OpenVMS 7.2-1
Pathworks Ver 6.0D

This configuration was setup with Digital/Compaq's help about 2 1/2 yrs ago. The last few days, the shares on the Alpha were losing connection esp when copying larger files to PC work stations.

Now, none of the shares on the Alpha will work. If you try to map a new drive on a PC (windows 2k or XP), the PC brings up a log on box. I can't get any user/pwd combination to work.

TIA

[Karl Rohwedder]

- are all PWRK processes up and running?
(@SYS$MANAGER:PWRK$DEFINE:COMMANDS and PWSHO)
- are entries in the errorlogs?
- has the Alpha lost connection to the PDC e.g.?
- does a restart pathworks help?
- anything interesting in the logfiles in PWRK$LOGS and PWRK$LMLOGS?

[Willem Grooters]

Just a hint....

[quote]
... If you try to map a new drive on a PC (windows 2k or XP), the PC brings up a log on box....
[/quote]

It might have been addressed in patches but this may be your problem. Has it worked before with Win2K and XP?

[Antoniov.]

Hi Rick,
on AXP (with sys priv):
1)ADMIN SHOW SERVICE
Service server is started?
2)ADMIN SHOW SHARE
Can you see shared directory?
3)ADMIN/LICENSE
If you have client based license, select View and then Client License; do you see the client in list?
If you are server based, select View and then Group; in server-based have you any license avaiable?
4)ADMIN/ANALYZE/SINCE=date
What error message do you see?
5)ADMIN SHOW EVENT/SINCE=date
What event do you see?

On client PC:
Click on start, all programs, Pathwork32, view event log.

After this investigation you could understand what does happen.
Post new info form more help.

Bye
Antoniov

[Ian Miller.]

What has changed? Have you upgraded your pc recently with patches. Windows 2000 service patches have been known to introduce incompatabiities.

[Paul Nunez]

Hi,

If the other suggestions don't pan out, this could also be due to SAM corruption.

When you can, try this and let us know if any errors are reported:

$ @sys$startup:pwrk$define_commands
$ pwstop
$ samcheck -s

How you recover from a corrupted SAM depends on the server role; is it a PDC or BDC? If a BDC, see the attached document for rebuilding the SAM...

[Brad McCusker]

I'm thinking along the same lines as Paul - SAM corruption.

If the SAMCHECK comes up OK, The log files would be the next place to look - PWRK$LMLOGS, PWRK$LOGS

I also wish to point out that V6.0D is rather old, and, as you start to add modern clients to your network, you might see more problems (e.g. Win2K, WinXP, Win2K3 are not supported on V6.0D).

You should be thinking about getting it upgraded (but, that won't resolve the immediate problem).

[Rick Watts_1]

Thanks for all the suggestions:

The basic attempts I have made are:
1. stop & restart pathworks services by the following commands:
@sys$update:pwrk$shutdown
&
@sys$update:pwrk$startup

2. Reboot the Alpha

3. Checked the SAMS database as suggested -

SAMS check showed no corruption -
----------------------------------------
$ @sys$startup:pwrk$define_commands
$ pwstop
Shutting down the currently running server(s)...
$ samcheck -s

No corruption was detected in the SAM database.
$ pwstart
PATHWORKS file server will use DECnet, TCP/IP.
PATHWORKS mail notification will use DECnet.
Process NETBIOS created with identification 00003E42
Process PWRK$KNBDAEMON created with identification 00003846
Process PWRK$LICENSE_R created with identification 00003C49
The PATHWORKS V6.0D server is configured to support 100 PC clients.
Process PWRK$MASTER created with identification 0000324E
The master process will now start all other PATHWORKS processes.
----------------------------------------

Here's the screen text from an pathworks Admin-Show Computers/full

EMPIREPW\\SABER> show computers /full

Computers in domain "EMPIREPW":

Computer Type Description
-------------------- --------------------------- -----------------------------
[PD] SABER OpenVMS 3.51 Primary PATHWORKS V6.0D for OpenVMS
(Advanced Server)
Sessions: 1 Open Files: 0 File Locks: 0 Open Named Pipes: 0

Total of 1 computer

EMPIREPW\\SABER>
------------------------------------------

Alpha's node name = SABER. It's on it's own domain as a PDC. Our Windows Servers are in a Domain EMPIREDIST.

Will look into the other suggestions.
Thanks Again for all the input.

[Antoniov.]

Hi Rick,
your network has already worked fine with winxp? I don't know V6.0D (because I've tried only V6.0C) but I think you can't work using client xp.
My customer cannot work using winxp so I have to upgrade to A/S V7.3.
Also you are running pathwork V6.0D instead A/S V7.x, so your server don't have registry and have some other limitation.

Your configuration is right, no error I can see. Read event and message using ADMIN/ANALYZE as ADMIN SHOW EVENT

Bye
Antoniov

[Paul Nunez]

Hi,

Sounds like the clients are logging into domain empiredist and the PATHWORKS domain empirepw trusts empiredist??

If so, then the trust is likely "broken" or the PATHWORKS PDC is no longer able to "find" a domain controller in empiredist. Event log messages on PDCs of both domains should provide a big clue...

Paul

[Paul Nunez]

Hello again...

Regarding the suggestions to upgrade, be sure you have the proper license first.

PATHWORKS v6.1 and Advanced Server v7.3 (and later, which includes 7.3a variants) require the license pak pwlmxxxca07.03.

There is an "upgrade" license you can purchase (can provide pointer if needed).


Paul

[Rick Watts_1]

I'll look into the trust. I think the trust was 1 way only because of the Win2K servers having Active Directory.

Paul, may take you up on the pointer to the upgrade. If we go the upgrade route, we will also purchase couple of days of consulting time. Since this Alpha Server is running in a "live" production enviornment, I would feel more comfortable having support on-site.

This is what we did when we upgraded from a 2100 to the DS20E.

In fact, I believe it may have been Paul Nunez that was our consultant. (BTW, Great Job on the migration. New server has been running fine without any problems until this issue with pathworks)

[Paul Nunez]

Well, of course - now I remember. How've you been Rick? I remember that upgrade - was a pleasure working with you.

I look forward to the opportunity again.

Feel free to contact me directly at paul.nunez@hp.com

[Rick Watts_1]

For those following this thread. Thanks to software support, we have this issue resolved.

Something (someone?) changed the SAMS database so the trust between the Windows-2k Servers and the Alpha Server nolonger existed.

HP support walked me through saving off the network share databases, running the pathworks config procedures, establish the trust, and finally resotoring the shares.