Windows keeps its connections in a buffer. Type "NET USE" at a command
line to see the list. When the password changes, the items in the list
are not maintained and won't work anymore. Use "NET USE ... /DELETE" to
drop the connection then "NET USE M: \\AS400Name\ShareName" with the new
user and password to restart the connection.
Also, make sure you have all the PTF's for NetServer on your i. The
default policies in the newer versions of Windows disallow NTLM. The
PTF's add support for the more secure authentication protocols.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gord Hutchinson
Sent: Wednesday, May 12, 2010 6:42 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Intermittent problem mapping Windows workstation to iSeries
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
