Ok, at my job we have a huge active directory structure. The domain is titled state.md.us
-a couple hundred OUs to cover all of our divisions
-We have a DC at every site, as well as DHCP and DNS server at every site.
-The ip scheme is 172.xx.xx.xx/24
-we don't use roaming profiles. All the users information (my documents, favorites etc) are stored on the file server(s) at each site. We run script logic to map the drives every time they login.
I was recently appointed the task of copying a user's documents over. The user had just moved from one division (in another part of the state), to my building (lateral transfer). I was given the address \fileserver1\mjones$ as the location of the users drive on the old file server. I was instructed to go there and copy the files over to our local file server here. When I popped \fileserver1\mjones$ in my browser, I got an error. "cannot find location" or something like that. The funny thing was, I could ping fileserver1 no problem
I tried the ip: \172.25.22.5\mjones$ and it still didnt work.
So I decided to try \fileserver1.state.md.us\mjones$ and it worked. I was able to copy the files over.
Why did it work when I included the domain in the address? Seems like entering the fully qualified domain name was the only thing that worked.
NOTE: I think this may be a proxy server thing? We are running a proxy server. Maybe since I'm trying to access this share from my browser, it is going through the proxy srever? I have "bypass proxy server for local addresses" checked. Anyone?