I've been asked by our Network Admin to post this query. Last time we had
this happen (Several months ago) I made sure "Allow authentication with LAN
Manager password hash" was set to Yes. Monday morning almost all the PCs we
checked could not map drives to any of our 3 iSeries. On Friday everything
was mapping OK.



Anyhow, in the Network dialect...



"Intermittent problem mapping Windows workstation to IFS



Windows and iSeries ID/passwords match

Reboot Windows workstation whenever password has changed



On Monday this week only a few people could connect. The solution seemed to
be having the rest use the IP address of the iSeries as a prefix to the
userid instead of the iSeries system name as the prefix even though the name
is resolving ok



What follows is something I noticed in Wireshark - I'm not sure if this is
consistent



SMB packet from Windows to iSeries negotiating password encryption protocol



SMB Negotiate Protocol Request

Requested Dialects

Dialect: PC NETWORK PROGRAM 1.0

Dialect: LANMAN1.0

Dialect: Windows for Workgroups 3.1a

Dialect: LM1.2X002

Dialect: LANMAN2.1

Dialect: NT LM 0.12



On a work station that still isn't working the response from the iSeries is:



SMB Negotiate Protocol Response

Word Count (WCT): 17

Dialect Index: 5: NT LM 0.12



So it seems that the iSeries is requesting NTLM as the protocol - I don't
know if it will use v1 or v2. On a workstation where the mapping worked I
noticed a different response from the iSeries "greater than LANMAN2.1" - how
is Windows to interpret that? Perhaps it uses LANMAN2.1. Maybe this fails
when the iSeries decides to use NTLM.



Any input appreciated."



Thanks,





Gord










This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.