Troubleshooting Network Drive Connectivity:
Step 1 – Identify if the device is University owned or personal.
University Owned
Step 2 – Are they on a University Network or VPN?
Step 3 – What network drive are they trying to access?
Step 4 – Confirm in AD that they have access to the requested 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 the steps above.
Step 7 – Confirm with the drive owner of drive that they should have access if they do not.
...
Personal
Step 2 – Are they on a 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 the requested drive they are requesting.
Step 5 – Assist with mapping the drive according to the table below:
Drive | Path | Targeting | Notes | |||
|---|---|---|---|---|---|---|
X:\ | \\floridapoly.org\root\CrossDept | Q:\ | \\floridapoly.org\fpudfs\IT | Technology Services Resources | ||
U:\ | \\floridapoly.org\root\users\%username% | U:\ | \\FIPR-002\users$\%username% | FIPR-Home Drive | This overrides the standard U:\drive mapping | |
M:\ | \\floridapoly.org\fpudfs\Academics | ACADEMICAFFAIRSACADEMIC AFFAIRS-RW | ||||
N:\ | \\floridapoly.org\fpudfs\Advancement | ADVANCEMENT-RW | ||||
P:\ | \\floridapoly.org\fpudfs\Finance | FINANCE-RW | ||||
O:\ | \\floridapoly.org\fpudfs\Executives | EXECUTIVES-RW | ||||
R:\ | \\floridapoly.org\fpudfs\FIPR | FIPR-RW |