Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Troubleshooting Network Drive Connectivity:
Step 1 – Identify if university the device is University owned or personal.


University Owned

Step 2 – Are they on University Network or VPN?
Step 3 – What network drive are they trying to access?
Step 4 – Confirm in AD that they have access to drive they are requesting
Step 5 – Restart and then GPU update
Step 6 – Assign to Administrative Computing if they have access but are not connecting by completing steps above.
Step 7 – Confirm with owner of drive that they should have access if they do not.


Personal


Step 2 – Are they on University Network or VPN?
Step 2a – Assist with installing VPN if required
Step 3 – What network drive are they trying to access?
Step 4 – Confirm in AD that they have access to drive they are requesting
Step 5 – Assist with mapping drive according to table below:





DrivePathTargetingNotes
X:\\\floridapoly.org\root\CrossDept

Q:\\\floridapoly.org\fpudfs\ITTechnology Services Resources
U:\\\floridapoly.org\root\users\%username%

U:\

\\FIPR-002\users$\%username%

FIPR-Home DriveThis overrides the standard U:\drive mapping
M:\\\floridapoly.org\fpudfs\AcademicsACADEMICAFFAIRS-RW
N:\\\floridapoly.org\fpudfs\AdvancementADVANCEMENT-RW
P:

...

\\\floridapoly.org\fpudfs\FinanceFINANCE-RW
O:\

\\floridapoly.org\fpudfs\Executives

EXECUTIVES-RW
R:\\\floridapoly.org\fpudfs\FIPRFIPR-RW