Windows Thread, Same share name on more than one server in Technical; This is going back a while but I seem to remember a few years back having an issue when I ...
27th July 2009, 08:53 AM #1
Same share name on more than one server
This is going back a while but I seem to remember a few years back having an issue when I had share with the same name on two servers e.g Server1\Shared and Server2\Shared, I seem to remember getting all sorts of odd issues when mapping drives and explorer on certain PC's opening the wrong share.
I'm about to migrate some GPO applications so i'd like to have two shares e.g Server1\Apps and Server2\Apps and i'm wondering if i'll see any odd issues.
I have a share called Users on more than one server without issue so i'm pretty sure it will be ok it's just this niggling feeling i've got about that problem in the past.
Anyone else had an issue with identical share names?
I'm considering using DFS to share the MSI's but i've read about many odd issues in the past is this situation improved in server 2008?
Last edited by cookie_monster; 27th July 2009 at 08:57 AM.
27th July 2009, 04:21 PM #2
I'm interested to learn that you have experienced problems. I don't see why it should cause a problem. The server names are different so, the mapping (whether via <net use x: \\Server1\shared> or otherwise) should find the correct server and then the shared folder on that server.
27th July 2009, 05:42 PM #3
Why can't you just share them out slightly differently ie
Originally Posted by cookie_monster
27th July 2009, 05:56 PM #4
There should be no problem with this kind of arrangement (ie, servers with the same share names) unless there's some DFS hackery in place.
27th July 2009, 06:00 PM #5
I have not had any issues with identical share names and have not heard of it as a problem. I do have to recommend going with DFS though, it is not difficult to setup and if you are only reffering to one share source for your installer files even the basic 2003 implementation will handle it fine and will prevent you spending hours redeploying packages when you have to change it again at a later date.
27th July 2009, 06:06 PM #6
If you have been deploying an application with GP from \\Server1\Share and change the policy to \\Server2\Share there should not be a problem.
As is the way with things though, sometimes the application will reinstall when the client machine next updates it's policy. Theoretically being the same application MSI in both locations should be recognised - but it isn't always.
DFS is probably the way forward for you. It is fairly reliable in 2003 but much better with 2008. 2008 also adds many more redundancy options for your file shares.
27th July 2009, 06:27 PM #7
I've published all my network shares using DFS on my new network. Not sure how it's going to cope yet, but we'll see. The main idea of this was to prevent certain students seeing the server names - now they only see the domain name for published shares and it also gives me the flexibility to move shares around between servers, but not have to make any changes to logon scripts etc. So far with a handful of staff on it it's working quite well.
Originally Posted by SYNACK
27th July 2009, 06:56 PM #8
Having the same sharename on two different servers should be absolutely fine. Shares should be locked down properly with permissions. As for hiding shares, ABE is what you should be using.
I don't think hiding the servername makes much of a difference to be honest. Even when mapping network drives it will say Share on 'SERVER' ( H: ) in explorer.
27th July 2009, 07:12 PM #9
I have a VB script which changes the Drive descriptions to hide that information. Very handy, also means I can rename N:\ to "My Documents" to try and get the message to staff that they are actually the same place on our system!
Originally Posted by Michael
27th July 2009, 07:36 PM #10
Care to share? How does it work exactly?
I have a VB script which changes the Drive descriptions
27th July 2009, 07:48 PM #11
A bit like this
Originally Posted by Michael
I have it run as part of my logon script.
Set objShell = CreateObject("Shell.Application")
objShell.NameSpace("N:").Self.Name = "My Documents"
objShell.NameSpace("P:").Self.Name = "Public"
objShell.NameSpace("S:").Self.Name = "Sims"
3 Thanks to maniac:
john (27th July 2009), mac_shinobi (27th July 2009), Michael (27th July 2009)
27th July 2009, 07:55 PM #12
Anyway to do it how I map network drives? For example....
net time \\SERVERNAME /set /yes
net use X: /delete
net use Y: /delete
net use Z: /delete
net use X: \\SERVERNAME\Share1
net use Y: \\SERVERNAME\Share2
net use Z: \\SERVERNAME\Share3
27th July 2009, 08:01 PM #13
Mapping drives in VBS is easy as well. You could map the drives with VBS instead and have them given a custom name as well?
Scripting is far more powerful with VBS than with a standard batch file.
27th July 2009, 08:02 PM #14
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive "X:" , "\\Server1\Share"
27th July 2009, 08:02 PM #15
I probably could convert them to VBS but I'm being lazy...
By fedail in forum Windows Server 2008
Last Post: 22nd November 2008, 07:02 AM
By crc-ict in forum Windows Server 2000/2003
Last Post: 18th August 2008, 08:40 PM
By tech_guy in forum General Chat
Last Post: 26th August 2007, 06:23 PM
Last Post: 16th July 2007, 12:21 PM
By ChrisH in forum Windows
Last Post: 29th March 2006, 08:16 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)