Hi,
I have discovered a weird issue with file services on Server 2008R2 64 bit datacentre [although it could be on any windows 2008 server]
We have a data server that is setup for home drives and staff folders. each user has a homedrive shared as firstname.lastname$ and the users workstations map drive P to \\server\firstname.lastname$
What I have noticed is that I can map a network drive to anything on that server regardless of whether it is a real share or not.
For example net use u: \\server\sharedoesntexist will actually map a drive U to nowhere. The U drive shows up as an 80Gb FAT partition but you can't save anything there. Now this normally wouldn't be a problem except that when staff logon they have their P drives mapped to \\server\firstname.lastname$. If for some reason this drive doesn't connect to the real location it connects to a virtual \\server\firstname.lastname$. The issue I have is that I redirect all users My Documents to this share and because it isn't physically connected to the right place it tells me everything is corrupt. I can usually fix it by removing the drive P and then remapping it again.
I have tried mapping a drive to another server that doesn't have file services installed net use \\server2\bogusshare and it correctly responds that this share doesn't exist. Any idea why file services allows users to connect to a bogus share?
Regards
I have discovered a weird issue with file services on Server 2008R2 64 bit datacentre [although it could be on any windows 2008 server]
We have a data server that is setup for home drives and staff folders. each user has a homedrive shared as firstname.lastname$ and the users workstations map drive P to \\server\firstname.lastname$
What I have noticed is that I can map a network drive to anything on that server regardless of whether it is a real share or not.
For example net use u: \\server\sharedoesntexist will actually map a drive U to nowhere. The U drive shows up as an 80Gb FAT partition but you can't save anything there. Now this normally wouldn't be a problem except that when staff logon they have their P drives mapped to \\server\firstname.lastname$. If for some reason this drive doesn't connect to the real location it connects to a virtual \\server\firstname.lastname$. The issue I have is that I redirect all users My Documents to this share and because it isn't physically connected to the right place it tells me everything is corrupt. I can usually fix it by removing the drive P and then remapping it again.
I have tried mapping a drive to another server that doesn't have file services installed net use \\server2\bogusshare and it correctly responds that this share doesn't exist. Any idea why file services allows users to connect to a bogus share?
Regards
