I'm not sure if this is the correct place to post this issue.ÃÂ ÃÂ I'm hoping someone can help, we have beenÃÂ trying to solve this issue for months.
I am trying to solve a persistent IO problem when checking to see if a directory exists on a Windows 2003 R2 Enterprise Edition Clustered File Server (Active/Passive).ÃÂ This issue is not limited to .NET code.ÃÂ We are seeing itÃÂ when we do a Directory.Exists, we get false, but the directory does exists.ÃÂ When we go to create the directory, we get an error of "System.IO.IOException: The specified network name is no longer available."ÃÂ If this failed all of the time, then we would know it was a permissions issue, but it is successful some of the time (even for days at a time, all with the same user trying to make the connection).ÃÂ ÃÂ
File ServerÃÂ ÃÂ is Windows 2003 R2 Enterprise Edition Clustered (Active/Passive) sittingÃÂ behind a firewall.
IIS serversÃÂ 1/2ÃÂ areÃÂ Windows 2003 Standard EditionÃÂ servers using an F5 BIG-IP for load balancing thatÃÂ sits behind the firewall and creates customer directories if they do not already exist (followed by writing data to the existing directory).ÃÂ These servers also have WebMethods installed that write the data to the File Server.
IIS servers 3/4ÃÂ are Windows 2003 Standard Edition servers using an F5 BIG-IP for load balancing that sits in the DMZ and a
View Complete Post