| Title: | Digital PATHWORKS 32 |
| Moderator: | SPELNK::curless |
| Created: | Fri Nov 01 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 337 |
| Total number of notes: | 1612 |
Hello, on one side: windows NT 4.0 server standalone Intel pw32 on the other side: vax/vms v6.1 + decnet osi or vax/vms 5.5-2 + decnet phase 4 On the NTNODE i just install windows NT and PW32, then i create a user CANDIDE and grant " logon as a batch " to this user. Then from the VMSNODE i use DIR commande, the first time it's work fine, the second time i got SYSTEM-F-REJECT I stop and start SPAWN32 service, then i got the same result 1st time ok the other not. extract from the Pathworks event log: 18:25:53 SPAW0001S: spawner (spawner) Version 1, 0, 0, 2 Loaded. 18:26:00 SPAW9999N: Command D:\PW32\FAL32.EXE -use 2 -access 3 executed! nothing in the event log Thank's for help Michel BERNEUIL French CSC VMSNODE => VMSNODE =>dir NTNODE"candide candide"::"c:\" Directory NTNODE"candide password":: "c:\AUTOEXEC.BAT" "c:\BOOT.BAK" "c:\CONFIG.SYS" "c:\IO.SYS" "c:\MSDOS.SYS" "c:\NTDETECT.COM" "c:\PPP123PP" "c:\PTW525" "c:\PWSETUP.LOG" "c:\SMSSETUP.LOG" "c:\Temp" "c:\boot.ini" "c:\ffastun.ffa" "c:\ffastun.ffl" "c:\ffastun.ffo" "c:\ffastun0.ffx" "c:\ntldr" Total of 17 files. VMSNODE => VMSNODE =>dir NTNODE"candide candide"::"c:\" %DIRECT-E-OPENIN, error opening 63647"candide password"::"c:\" as input -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-F-REJECT, connect to network object rejected VMSNODE =>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 303.1 | bug fixed in 7.0A | JAMIN::RUZICH | PATHWORKS Client Engineering | Mon May 19 1997 12:53 | 21 |
>On the NTNODE i just install windows NT and PW32, then i create a user CANDIDE >and grant " logon as a batch " to this user. > >Then from the VMSNODE i use DIR commande, the first time it's work fine, >the second time i got SYSTEM-F-REJECT You did everything properly. However, there was a bug, which has been fixed in the spawner for 7.0A. In the meantime, you could work around it by defining a username / password with... NCP DEFINE ACCESS USER xxx PASSWORD xxx access-type ... where 'access-type' is, for example READ or ALL. For an NT user account, the spawner validates the user name in the NT user account database, then it 'impersonates' the user before executing FAL32, so that FAL32 will then have the user's level of privilege. The problem was that the spawner needed to reset itself back to its initial high level of privilege for the second access. Without the reset, the spawner did not have enough privilege to validate the user name from the second request, so it failed. -Steve | |||||