Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Path too deep" through VPN while uploading

Status
Not open for further replies.

jhindman35

Vendor
Sep 2, 2003
9
US
We have had a VPN that two employees have used for several years when working from remote locations. Up until recently, they have worked fine. Now one employee cannot upload big files to the server and gets the 'path too deep' message, while the other employee can upload the same file with no problem. I have checked their permissions and they are identical. Does anyone have any ideas why this would effect one and not the other, and most importantly, how do I fix it?
Thanks for any help in advance,
Johnna
 
Generally, the path to the source file or the destination file can't be over 256 characters. The file size should have no bearing, only the total length of the path.

NT 4.0 would sometimes throw this error when there was a problem with permissions, but that was fixed for 2K on up.

 
Neither the path or destination file are over 256 characters. Plus if that was the case, why would it work for one employee and not the other? Any other suggestions?
Thanks
 
Hi Guys

We have exatly the same problem ,suddenly within the last month users get Path too deep messages when transferrring files over VPN link. It seems to be a combination of things, a dos transfer will give a semaphore timeout error , an XP explorer transfer will give a path too deep error. In all cases it appears that the network card/driver is faulty [integrated Intel Pro 100 in a Compaq 510]. The only other change to our systems in teh last month has been ISP "upgrades" to our cisco router after problems they experienced with the nachii and blaster virus. Has anyone got any updated info on this error?

Thanks
 
Our problem isn't the network cards, they have tested fine and the drivers have been updated. There has to be a solution to this problem.
 
Maybe a recent Windows update patch which brough a new bug with it?

just a suggestion.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top