RE: Mapping a drive to the IFS fails but works

Also, take a look to see if you have a host file on your workstation, host
files will override DNS.

-Jason

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jvoris@xxxxxxxxxxx
Sent: Tuesday, May 08, 2012 1:43 PM
To: midrange-l
Subject: Mapping a drive to the IFS fails but works

My guess is that the DOS command is relying on some *DIRSRV in STRHOSTSVR
or STRTCPSVR - and the port number that the AS400 Windows Network
Neighborhood is using is now being blocked by a firewall. But yes, the IP
address and the DNS not giving the same results is wierd. I would look
toward your network and the not System i.

message: 2
date: Tue, 8 May 2012 12:54:18 -0400
from: daparnin@xxxxxxxxxxxxxx
subject: Mapping a drive to the IFS fails but works

Here's a head-scratcher...

I've got a batch file on my PC that I haven't used in a long time that
maps a drive to the IFS. It used to work and now it doesn't. The
command to map the drive is:

net use w: \\as30\Root\ACH /user:DAPARNIN

The result is:

Enter the password for 'DAPARNIN' to connect to System error 86 has
occurred.

The specified network password is not correct.


My i password is not my network password. The i is at V5R4. The weird
thing is that if I replace the system name AS30 with the IP address, it
works. Our DNS should have the correct IP address because that is the
address that is returned when I ping AS30. Thoughts...?

Dave Parnin
--
Nishikawa Cooper, LLC
(formerly Nishikawa Standard Company)
324 Morrow Street
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxx

--
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.