Interesting mapped drive problem

I am working on a simple peer to peer network that is using a W2k server and W2kworkstations both using NTFS file system. Problem is that one workstation is showing all mapped drives as being disconnected, but when you click on them they open right up. Doesn't sound like much of a problem, but a program that requires a specific mapped drive sees it as disconnected also and will only open until it querrys the mapped drive. I've tried remapping the drives....no effect. I've checked authentication on the server and it's seeing the workstation. I've mapped back to that workstation and it shows ok. When you go into network neighborhood and try to access the server, I get the error "the volume does not contain a recognized file system. Please make sure the file system drivers are loaded and that the volume is not corrupt". None of the other workstations have this problem so that tells me the problem is on that particular workstation. I've checked the MS knowledge base and it says something about the mapped drive as not showing the file system on the workstation from the server, but it shows correctly. I've checked ip and DNS and this 'station is setup exactly like the other 'stations. I'm open to suggestions and a good stiff :drink:

This is a feature but fixable

Thanks NooNooyou little Driver Terrier. :D

I'll try your suggestion, but I don't know if it'll work. I know.......I need to have faith in the suggestions and I appreciate it. I didn't mention that when you boot the computer it acts like it connects to the drives (you see the flash that it's connecting come up) but when you open My Computer the red x's are already there. When you have Windows check the status of the drives they show to be disconnected. I can't imagine that a user could have figured out how to set the timeout to 0, but then you can't underestimate the users.

NooNoo, I tried your suggested fix and, alas, it didn't work. I checked the timeouts on the server and on this workstation and increased both to the maximum. The drives still showed disconnected. If you try and un-map a drive it says unrecognized file system and will not let you disconnect. It will not let you map any drives either. If you go into network neighborhood, you can get as far as the workgroups name until you get the error "workgroup is not avaliable". It has retained the old mapped drives (that show to be disconnected) and you can go as far as to open Word, Excel, etc...documents on the local computer. When a program that requires permissions from the server tries to access the server, you get a "no mapped drives avaliable" error message. I've removed and reinstalled TCP/IP and the network adapter to the same results. If you check the error logs in administrative tools ther is one error that keeps coming up "could not load any transport". I'm tired of seeing red X's :confused: and I'm running out of ideas

OK the one error that keeps coming up, can you post the full details please?

Do all the workstations have passwords to logon to the server?

I guess you can close this one. The owner didn't really have anything saved to this computer. He was saving all vital data to the server and doing backups. That doesn't happen very often. I still don't know what the problem was, but it was fixed by fdisk, format and a fresh install of W2K. Things are working fine now. It should not have made a difference, but my "helper" had installed FAT32 instead of NTFS file system by mistake. That might, sort of, explane the unrecognized file system error message. Thanks for the help Noo. :thumbs: