Discussion Locked

Mapped drives and passwords

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am integrating Windows 2000 doamin and AS/400 in a test environment. A mapped network drive (of a share on a stand alone server--outside the domain) often has a red "X" as if the drive is not mapped. However, if I double click on said share, I am right in. Within minutes, the red "X" will come back. Also, AS/400 drive mappings are terrible. I can map an AS/400 drive and enter the AS/400 password--no problem. However, if I log off and log back in, the password prompt calls for the appropriate password. If I enter my AS/400 password, I am denied. I cannot reconnect unless I kill all drive mappings and re-boot. Goal: I want to keep Windows passwords and As/400 passwords different/separate for security purposes. My guess is that passwords are being cached and not released...perhaps the kerberos authentication is a problem??? I have setup no group policies...these are all defaults. Please help if you can. All I wish to do is map a freaking network drive and have access to itsresources EVERY time I reboot. Good ol' MS...

7 replies

by steedy

Have you got Novell running?
To keep the mapping next time you logon just check the appropriate box. As for the kerberos, it works on a trusted third party idea and simply generates a session key (random number) if public and private keys are accepted - nothing to do with passwords as far as I recall. The red X is often neither use nor ornament but could signify that something aint quite right. Try disconnecting from the mapped drive and make a new mapping using a diff. drive letter.
Good luck. Any other details might help.

by legj1

There is no Novell running. If said Win2000 boxes are in a Workgroup, the As/400 netserver drive mappings come up fine. This problem only occurrs when logged into a domain. I am guessing that the RED X has something to do with my problem. It is as if the server is not releasing mapped drives for some reason. Or Win2000 periodically closes these connections to save bandwidth??? Any help is appreciated. Most people do not maintain constant As/400 constant drive mappings to a netserver....so finding an answer to this problem may be difficult. Any more help is appreciated!

by adeal

This is no solution. I'm just concurring. I have the same problem for any machine I map drives to that is outside of the domain.

by legj1

Another few facts: This is not simply an As/400 problem. If I map MULTIPLE shares to a stand alone win2k server, I get the same results. Mapping one share is fine. Map two and logoff...and you never get authenticated. If you match your domain password and the stand alone password, there are no problems. My actual question is: Are there any Domain Policy or security settings that are configurable to allow multiple stand-alone connections. Or am I just sh*t out of luck? I need to allow for multiple connections due to multiple shares on the As/400's netserver. Again, all help is appreciated. Hopefully, there is a solution.

This discussion is closed to new replies.