• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't access resources at remote site

imported_JFG

Senior member
I have a users workstation that accesses resources at a remote site. Basically we have a file server here on sight and one at our disaster site. We failed over to our disaster site and ran the necessary scripts to kick off our failover software, so basically the users service went uninterupted. All workstations have a persistent route to the machines at the disaster site. Everything is working fine except for one workstation. This workstation can't find the resource (or anything at the disaster site). If we give the user a DCHP leased address they can access resources at the disaster site. If you do a tracert by hostname it fails (host not found), but it works with the IP address. Everything is a class B subnet. On site our addresses are 10.1.100.*, the DCHP leased addresses are 10.1.4.*, the Disaster site adresses are 10.2.*.* .

Any ideas why this workstation is having this problem with the hard coded address (and leaving it at DHCP is not an option---has to do with direct connection to certain financial institutions)...

Thanks
 
Back
Top