ETM_INC
asked on
How do I get a share named \\server\gis to show as \\gis\gis?
I am in the process of upgrading a couple file servers and would like to consolidate them.
Currently, people either access their files by going to \\gis\gis on one server or \\design\design on the other server. When I move the gis shared folder to the design server, I will still need to retain the ability for people to access it through the share name \\gis\gis. How do I do this?
I'm using Windows 2008 r2.
Currently, people either access their files by going to \\gis\gis on one server or \\design\design on the other server. When I move the gis shared folder to the design server, I will still need to retain the ability for people to access it through the share name \\gis\gis. How do I do this?
I'm using Windows 2008 r2.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
If your clients are XP, it also requires editing the registry on the server under the LanManServer service. I will look it up when I get to the office.
ASKER
I tested the CNAME route, but I can't seem to get it working. I have entered the cname in DNS, and am able to ping from a workstation (Windows 7) without a problem. However, when I try to access the share in Windows Explorer, I get a "Windows cannot access \\test" error.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
So to recap, you created a CNAME entry called 'TEST' and associated the IP address of your server named DESIGN. Correct?
If that is the case, and you can "PING TEST", and it resolves to the Ip address of DESIGN...then your CNAME entry is working correctly. You should then be able to \\TEST\GIS and it should map to \\DESIGN\GIS.
Is that not working?
If that is the case, and you can "PING TEST", and it resolves to the Ip address of DESIGN...then your CNAME entry is working correctly. You should then be able to \\TEST\GIS and it should map to \\DESIGN\GIS.
Is that not working?
ASKER
Brian,
That is correct. I can ping "Test" and it resolves to the correct address. However, I cannot use explorer to view the server or share. Both \\Design\GIS and \\"ip address"\GIS work fine, but \\Test\GIS gives me the error.
One thing about the CNAME entry: It won't let me associate to IP, only the FQDN.
That is correct. I can ping "Test" and it resolves to the correct address. However, I cannot use explorer to view the server or share. Both \\Design\GIS and \\"ip address"\GIS work fine, but \\Test\GIS gives me the error.
One thing about the CNAME entry: It won't let me associate to IP, only the FQDN.
ASKER
Kevin,
The link you sent was for Server 2003. Do you know if this applies to 2008 as well?
The link you sent was for Server 2003. Do you know if this applies to 2008 as well?
Works the same.
ASKER
I tested CNAME in my lab and it works fine. I'm able to see the shares as I would like them to see them. I don't understand why it doesn't work in my real environment.
The error that came up is "Multiple devices have the name "thiswontmatchanything"". I used this name because I know I have nothing on the network with the same name so I don't understand what else it could be seeing.
The error that came up is "Multiple devices have the name "thiswontmatchanything"". I used this name because I know I have nothing on the network with the same name so I don't understand what else it could be seeing.
Instead of a CNAME, try creating a HOST (A) record in your Forward Lookup Zone. Call it TEST4 (or whatever you want) and give it the same IP address that the DESIGN server uses.
Can you get to the new share via \\TEST4\GIS ?
That method should work just fine as well.
Note: you may need to do an IPCONFIG /FLUSHDNS on the client machine, just to be sure.
Can you get to the new share via \\TEST4\GIS ?
That method should work just fine as well.
Note: you may need to do an IPCONFIG /FLUSHDNS on the client machine, just to be sure.
ASKER
I receive the same error when creating an A record. The error code is 0x80004005.
I have tried accessing this share from both a Windows 2003 and a Windows 7 box with the same results. I also tried turning on Network Discovery on the Win7 box, but that didn't work either.
I also have tried the ipconfig /flushdns command and a reboot on the client machine.
In case this makes a difference: My network is currently a Windows 2003 domain, but I plan to upgrade to a Windows 2008 domain around the same time as I change the file servers. So I'm troubleshooting on the 2003 domain, and the 2008 domain (lab environment) works fine.
I have tried accessing this share from both a Windows 2003 and a Windows 7 box with the same results. I also tried turning on Network Discovery on the Win7 box, but that didn't work either.
I also have tried the ipconfig /flushdns command and a reboot on the client machine.
In case this makes a difference: My network is currently a Windows 2003 domain, but I plan to upgrade to a Windows 2008 domain around the same time as I change the file servers. So I'm troubleshooting on the 2003 domain, and the 2008 domain (lab environment) works fine.
Did you make the registry change and reboot the server?
ASKER
I haven't tested the DFS route yet because I figured the CNAME implementation would be the easier way to go. If I can't get CNAME to work in my environment, I'll test DFS. That will probably happen on Monday.
ASKER
Okay, I managed to get the CNAME issue working by editing the registry per Microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281308
Thanks everyone for your help!
http://support.microsoft.com/default.aspx?scid=kb;en-us;281308
Thanks everyone for your help!
http://technet.microsoft.com/en-us/library/cc772053.aspx