I have a W2K server with Proxy 2.0 loaded. I can use the Proxy server for accessing the Web fine. However, I cannot get the Winsock service to work properly, I am trying to talk to an Exchange server connected to the internet but can never access it. If I ping the exchange server, it returns its IP address but the PING fails with a 'destination host unreachable' message. I can PING it from the actual proxy server fine. The permissions for the winsock service are set to enable access control with unlimited access. If anyone can help with this please let me know. Thanks Ryan Note: I have also posted this in the W2K area as I was not sure where the problem may be, i.e. OS or Network.

Ryan, it sounds like you've only got the first half of the winsock services set up. The second part is that you have to install a patch on the client. By default, it's in a share on the proxy server. You should be able to browse to it through your network neighborhood. I haven't seen that particular program running for over a year, so I can't recall the share name. It should be pretty obvious, though. You may have to tweak the proxy to allow certain protocols through, but by default, it only passes TCP based communication, and a ping is UDP based. Now, for the second part of your question: Exchange Server operates in a way unlike many applications. The client sends a conversation request to the server, and the server replies as in a normal TCP/IP conversation. That's about the end of normality, though. The server tells the client what port to use for communication, and initiates the conversations after that. You can set the server to communicate on set ports, though. The article is at: http://support.microsoft.com/support/kb/articles/Q155/8/31.asp Good luck, Chase

thanks Chase, most useful. I will try these out, have managed to use RRAS to do what I was trying to achieve anyhow but would still like to crack this one! once agian thanks for the response. Ryan

Application [spoolsv.exe]. The application was started while the service manager was locked and NtLmSsp wasn't running. If the application will try to remote via WinSock Proxy it can cause a deadlock with the service manager. For this reason the remoting is disabled. If the application is a service, and you want it to be able to remote, make it dependent on NtLmSsp. This is the error I am getting in EVent Viewer when I tried to connect my Windows XP with NT server.I couldnt find out the name of the service which runs WinSock Proxy Client.I tried to edit registry key but that didnt help.Can anyone tell me what should i do to avoid this problem.Thanks