Troubleshooting network drive mappings

Troubleshooting network drive mappings

Document number: 55060

If you log onto the network properly, certain drives should map for you automatically. The N: drive is essential for using certain applications, and the P: drive is essential for loading applications from the Software Library and receiving PeopleNet Updates.

Click on the drive with which you are having a problem.

M: drive - see Eureka! document 55003
N: or P: drive
Other drive

N: or P: drives not mapping

When you connect to the network properly, a PeopleSoft logon script should run and your N: and P: drives should automatically map for you.

RAS: The PeopleSoft logon script does not run when you log onto the local machine first and then RAS in. The logon script is what maps your N: and P: drives. You should RAS in by checking the Dial-Up Networking box on the Windows logon screen.
- Note: When you do RAS in properly, you may need to wait a minute or two for the drives to map - the process is not instantaneous, particularly if you are far away from the server.
VPN: These drives don't map if you log onto the PeopleSoft network via VPN. You will need to map the drive you need manually. See Eureka! document 50003 — How to map a drive letter.

Make sure your PeopleSoft logon scripts are running properly: The N: and P: drives map via the use of a customized PeopleSoft logon script. When the drives properly map, you should hear a "chew! chew!" sound from your machine. If your drives do not map even when you are properly RASed in or directly connected to the PeopleSoft network, you may need to reload your logon script files. For instructions on replacing your logon script files, see Eureka! document 55021 — Reload network logon scripts using PNU Control.

Click here to go back to the beginning of this document.

Other drive letter (assuming that a particular server is not currently down)

If you were not connected to the network the last time you booted up the machine, you may have received a message that the drive was not available. If you did choose to reconnect the drive at the next logon, the next time you log onto the network, this drive letter will not map. To solve this, map the drive manually. For more information how to map a network drive, see Eureka! document 50003 — How to map a drive letter. This time, make sure to check the Reconnect at Logon box.
When you RAS in and the logon scripts run, the drive letters appear in a dialog box as they are mapping. If the you click the Cancel button while the drives are mapping, the drive may not map during the current RAS session. To solve this, map the drive manually (or reboot; the problem will go away). For more information how to map a network drive, see Eureka! document 50003 — How to map a drive letter.
Like the M: drive, if a particular server was down the last time you logged on and you did not choose to reconnect the drive letter the next session, that drive will not map during future sessions. To solve this, map the drive manually. For more information how to map a network drive, see Eureka! document 50003 — How to map a drive letter. Make sure to check the Reconnect at Logon box.

Click here to go back to the beginning of this document.