Sysadmins help!

Chuckles · 01-03-2011, 20:49

Consider this scenario

You have 2 file servers on 2 different sites.

Site A is the main production site and houses ServerA
Site B is a remote office and houses ServerB

The file store for images/PDF's etc is duplicated in the following locations

Site A - \\ServerA\Data\
Site B - \\ServerB\Data\

When users in each site work in Quark, inDesign etc their images are all linked in through their local server as the WAN between the 2 is ****.

That all works fine but you've got a script running in site A on ServerC that polls a folder for "Completed" documents and saves out an EPS.

For files on Site A, this is fine because it's only ever looking locally, but the links are hardcoded (and can't be changed) into the documents, so when Site B submits, they are being pulled in across the WAN and taking an age to build.

I thought a quick and simple fix would be to use an entry in the host file on Server C to map the netbios name of server B to the IP address of Server A.

It doesn't work because if you try and access the shares from Server C you get "Access Denied the Target name of the server is incorrect".

I assume this is because Server A knows not to listen clients trying to access shares under the netbios name of Server B

Is there a way to achieve this?

Thanks

01-03-2011, 20:49	#1
Chuckles '09 sexual conquests: 4.5 Join Date: Sep 2007 Posts: 1,075	Sysadmins help! Consider this scenario You have 2 file servers on 2 different sites. Site A is the main production site and houses ServerA Site B is a remote office and houses ServerB The file store for images/PDF's etc is duplicated in the following locations Site A - \\ServerA\Data\ Site B - \\ServerB\Data\ When users in each site work in Quark, inDesign etc their images are all linked in through their local server as the WAN between the 2 is ****. That all works fine but you've got a script running in site A on ServerC that polls a folder for "Completed" documents and saves out an EPS. For files on Site A, this is fine because it's only ever looking locally, but the links are hardcoded (and can't be changed) into the documents, so when Site B submits, they are being pulled in across the WAN and taking an age to build. I thought a quick and simple fix would be to use an entry in the host file on Server C to map the netbios name of server B to the IP address of Server A. It doesn't work because if you try and access the shares from Server C you get "Access Denied the Target name of the server is incorrect". I assume this is because Server A knows not to listen clients trying to access shares under the netbios name of Server B Is there a way to achieve this? Thanks __________________