Have recently migrated a w2k3 sp2 fileserver to a new box that has a new name (again w2k3 sp2) so we can decomission the old box.
We transfered all the data across but because of the numbers of shortcuts in existance in the business we need to be able to make old paths still work.
OldBox 192.168.0.1
NewBox 192.168.0.2
To keep it simple we created an A host record for old box but changed the ip so that it points to 192.168.0.2. We then turned the oldbox off.
From any client PC's or other Win2k3 servers this works fine and typing in \\oldbox will show you all the available shares on newbox.
However if you log on to the console or launch an rdp session on New Box and type \\oldbox you recieve a request for authentication.
The authentication message has newbox.domain in the title bar which shows it is getting to the correct location but no credentials (even Domain Admin) will allow you to see the shares available on newbox.
Likewise if I try and run \\oldbox\C$ the same authentication problems exist.
I'm sure the problem is relatively easy to fix I just can't work out what needs changing. DNS is definately working as its getting to newbox to challenge for authentication and everyone else is able to view the shares. I keep thinking permissions located around the workstation service but can't see what or how.
For reference there is no firewall in place, no windows firewall, ip filtering isn't in operation and the servers were both on the same Win2k3 functional level domain at the same site.
Any ideas?
Thanks
We transfered all the data across but because of the numbers of shortcuts in existance in the business we need to be able to make old paths still work.
OldBox 192.168.0.1
NewBox 192.168.0.2
To keep it simple we created an A host record for old box but changed the ip so that it points to 192.168.0.2. We then turned the oldbox off.
From any client PC's or other Win2k3 servers this works fine and typing in \\oldbox will show you all the available shares on newbox.
However if you log on to the console or launch an rdp session on New Box and type \\oldbox you recieve a request for authentication.
The authentication message has newbox.domain in the title bar which shows it is getting to the correct location but no credentials (even Domain Admin) will allow you to see the shares available on newbox.
Likewise if I try and run \\oldbox\C$ the same authentication problems exist.
I'm sure the problem is relatively easy to fix I just can't work out what needs changing. DNS is definately working as its getting to newbox to challenge for authentication and everyone else is able to view the shares. I keep thinking permissions located around the workstation service but can't see what or how.
For reference there is no firewall in place, no windows firewall, ip filtering isn't in operation and the servers were both on the same Win2k3 functional level domain at the same site.
Any ideas?
Thanks
