plexer Posted May 17, 2011 Posted May 17, 2011 I have a seperated network that my servers backup over. The servers which utilize it have a second nic and a 192.168.1.x ip address. The cdp server backs them up over this network to a terastation. On the cdp server there is an entry in the hosts file for 192.168.1.1 ts01. The cdp server is configured to backup the hosts to \\ts01\backup\cdp. I've recently copied all the data from ts01 to a new file storage server which is named cdpserver02. I changed the host entry to be 192.168.1.6 ts01, .6 being cdpserver02's ip. I can connect to \\192.168.1.6\backup\cdp but not \\ts01\backup\cdp. If I try to connect to \\ts01\backup\cdp I get an error telling me there is a duplicate name on the network and to go into control panel to change the computer name. Any ideas? Ben
pantscat Posted May 17, 2011 Posted May 17, 2011 Have you tried a nice simple "ipconfig /flushdns" - it may be that simple. Edit: ... and probably worth clearing your ARP cache too.
plexer Posted May 17, 2011 Author Posted May 17, 2011 Done a flushdns on it, rebooted the server in question as well. The reason I set it up like this in case anyone is wondering is that the cdp software doesn't provide a way to migrate the data store nicely from one host to another so I thought this would be a solution. Ben
AshEarl Posted May 17, 2011 Posted May 17, 2011 Do you have any dns servers set up in your network settings on the first nic? Does your ts01 have any other cards in it that could be registered in DNS elsewhere. I had a similar issue once....drove me mad till I realised what I had done!
plexer Posted May 17, 2011 Author Posted May 17, 2011 The original ts01 only had one nic and that just had the 192.168.1.1 address. Both cdpserver01 and cdpserver02 have other nics which are connected to our lan with dns setup. Ben
plexer Posted May 17, 2011 Author Posted May 17, 2011 Ok just double checked in dns and there was an old static entry in there for ts01 so removed that but still not joy. If on cdpserver01 I ping ts01 it pings 192.168.1.6 which is the correct ip address as per the hosts file but I cannot connect via unc using the name. Ben
mac_shinobi Posted May 17, 2011 Posted May 17, 2011 If you do an nslookup on ts01 does it resolve to the correct ip address and also is ts01 the name of the old server. If so I would use the hostname of the new server instead of relying on the host file pointing it to the 192.168.1.6
Marci Posted May 17, 2011 Posted May 17, 2011 Try putting a 3 part fqdn in hosts and use that instead of just machine name - don't think hosts file overrides netbios, which I suspect is your issue.
plexer Posted May 18, 2011 Author Posted May 18, 2011 If you do an nslookup on ts01 does it resolve to the correct ip address and also is ts01 the name of the old server. If so I would use the hostname of the new server instead of relying on the host file pointing it to the 192.168.1.6 The path that the cdp server is looking for is \\ts01\backup\cdp I need to replicate that on the new box or go back to the old terastation for storage still I was just trying to migrate my data to larger storage. Ben
plexer Posted May 18, 2011 Author Posted May 18, 2011 Try putting a 3 part fqdn in hosts and use that instead of just machine name - don't think hosts file overrides netbios, which I suspect is your issue. nope gives the same error. Ben
plexer Posted May 18, 2011 Author Posted May 18, 2011 Right ok looks like I've solved it it was down to the fact that because the remote servers real name is cdpserver02 and not ts01. I think I'll have to throw some dns into the mix to be able to use and an alias. For now I've renamed cdpserver02 to ts01 and can connect to the share with all the data intact from cdpserver01. Ben
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now