[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
4258.0. "Upgraded personal share is seen as FAT ?" by VMSNET::ALLERTON (Episode d'Azur) Fri Apr 11 1997 13:33
This is strange, and I was wondering if anyone has encountered anything
like it before:
- User upgrades single PWV4 server in cluster (with directory services
on cluster-mounted devices) to V5.0E (Alpha). Upgrade proceeds
normally
- Following upgrade, user on WNT 4.0/PW-32 client connects to his
personal share. Any files that exceed 8.3 naming convention aren't
visible (The files in question, mostly command procedures, were
VMS-generated). LAN Man only security in place, permissions
properly set, no ACLs on any of the files in the share directory
- User examines properties for network drive icon for personal share
connection in NT (My Computer->Net Drive icon->General), and the
File System type shows to be ***** FAT *****.
- The device in question is mounted with an assigned logical name (trans=
(concealed, terminal)) that is the same as the device's volume
label.
I had him delete the share. A net share command didn't list an autoshare
for the cluster-shared disk, so I had him do $ net share /sync, and readd
the share, mapped to the device's newly-acquired autshare reference.
Properties for the associated share device volume from NT 4.0 then
correctly showed up as ODS-2, and all files were visible.
Steve
T.R | Title | User | Personal Name | Date | Lines
|
---|