Workspace Factory requirements

Hi

I've written an application to create some workspaces on a regular basis which uses the workspace factory. The app was working completely fine until their IT department decided to lock down the server using IPSEC. We have had multiple problems, and solved most of them by configuring port settings, etc., but I can't get the workspace factory to work.

Worksite Web is working fine, but the factory web service doesn't seem to be able to contact the Worksite Server. The error I am getting is as follows:

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable host
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at CLDIntegration2.WorkspaceFactory.Factory.CreateWorkspace(String database, String templateID, String name, String description, String category, imSecurityType defaultSecurity, AclItem[] aclItems, ProfileItem[] profileItems, Notification notification, ProfileError[]& profileErrors)
at CLDIntegration2.Program.CreateWorkspace(IntegrationItem ii, String WorkSiteDatabase, Factory f)

I have always thought of Worksite web and these webservices as just client applications (like FileSite), but this webservice is doing more than a client is usually able to do (eg using the templates to create workspaces), so perhaps they need more than just the standard ports open?

Any advice would be appreciated.

Gary

Find more posts tagged with

Comments

dabird

The error shows that you can't even open the request to the web service (at HttpRequest.GetRequestStream()). It doesn't have anything to do with the web service itself. Just a shot in the dark, but is this web service under SSL while WorkSite Web is not, or vice-versa? If so, then you probably need to open up port 443 or whatever is being used for SSL.

garymccl

Well, that is more confusing if in fact the problem is contacting the web server, rather than the communication between the web server and the WorkSite server.

Since I posted this message, we removed the IPSec filtering from the web server, but this did not correct the problem. We have now removed the filtering from the WorkSite server and this has corrected the problem. I would have thought that this points to a problem between the web server and the WorkSite server.

The state of the servers is not acceptable at the moment, we need to re-add the filtering to all of the servers. SSL is not [currently] in use here.

Thanks for the reply.

Gary