bbud Posted August 10, 2010 Posted August 10, 2010 (edited) I have seen several posts within this forum that seem to be similar to my issue, what makes matters worse, this subject matter is not my domain of expertise. I am merely posting here to see if I can get a simple answer to help me help my IT support. The following is information that will help all you smart people: Hardware / OS This is a Windows virtual server, not a physical server Windows 2008 R2 Standard Server 64-bit with Application services, File Services, IIS roles installed 2GB RAM Host server is running a Xeon Quad Core 2.5 Ghz CPU Applications Filemaker Server 11 and default software Sophos Endpoint Security and Control version 9 This is a dedicated Filemaker server so there is no other software installed Through trial and error, I have gotten beyond the simple path not valid error, and I am now getting the following message when trying to get to a file that I know is on the server: The file "abc123.fp7" could not be opened. Either the host is not available, or the file is not available on the host. The latter part of this warning I believe to be untrue since I can see it when I am logged in to the admin console. Any and all suggestions, not matter how simple are welcome. Other information. The server is sitting on a box remote to me. I am trying to hit it using a Webpass connection on a Mac, and have also tried using a VPN Client (Cisco) using my pc, both obviously with the same results. Thanks in advance for any help you can provide. Edited August 11, 2010 by Guest
bbud Posted August 11, 2010 Author Posted August 11, 2010 All the views and no responses... I know, you were all there with me in spirit. I am happy to say, problem solved.
Newbies terryt Posted August 19, 2010 Newbies Posted August 19, 2010 Hi - I seem to be having a similar problem. Can you please tell me how you solved it? Thanks! Terry
bbud Posted August 20, 2010 Author Posted August 20, 2010 @terryt - my problem was I accepted the answers I received from the IT folks helping me. I ended up logging on to the server myself and double checking settings. My problem was solved by turning off the Windows Firewall. Of course, this may cause some concern, but given that the box is sitting on our company network requiring login authentication, I am not too concerned. Let me know if this helps.
Recommended Posts
This topic is 5209 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now