From: Beaverton, OR, US
I have a vpn setup successfully. I can connect to the VPN and get to machines inside just fine. I cannot get to any HTTP addresses that are on those same boxes however. I have a rule setup to allow access from vpn clients to the internal network and allows all protocols to all users. Any suggestions?
From: Beaverton, OR, US
Hello Tom. I can ping for instance a server by name ie.. Ping server1 and I get a response resolving the IP. Then I try to connect to say http://server1/whateverpage and I get denied with an odd error. Something like error 532 the pipe is being closed. I can remotely manage that same server and connect to file shares on it and so on. Just no HTTP. Same thing for other servers internally as well.
Posting as an unregistered user because I can't seem to get registered. I keep getting the "sorry...username taken..." error message, even when using random characters for a username. Something's broken.
Anyway, I too am experiencing this "pipe closed" issue with VPN clients. Not all VPN clients though. Only some. Here is a message I sent the support people for our firewall appliance:
"Re: error message = Error Code: 500 Internal Server Error. The pipe is being closed (232)
Either one of you have any idea what this error message means? I guess I have several VPN clients that are getting this message when they are connected to our VPN and trying to open websites in a browser. I can duplicate the problem, but only when I log into the VPN connection using their credentials. In AD, under Dial-In, we're all set to "Control through Remote Access Policy". There are several accounts that the connection works fine on, many others it shows the error message below when using IE. I've tried connecting with user accounts that have no administrative privys in AD and some exhibit this behavior, some don't. Some administrator accounts exhibit the behavior, some don't. It's very random it appears, except for in the sense that for those users that get this error message, they get it on any computer, and for those that don't get the message, they don't get it on any computer. On a given computer, an account that does not get this message never does, even when on the same computer an account that does get this message always does. It doesn't appear to be computer related, firewall related or AD group membership or dial-in related. I'm really at a loss. When I look at the firewall monitoring, the traffic for those users who get this message looks nearly identical to the traffic for users who do not get the message. The only difference is usually the "Incoming Port". I've got log files I can share, etc. I would greatly appreciate your help on this one. I've troubleshooted this problem for two days and have gotten nowhere."
This only happens with HTPP. These clients can access HTTPS sites fine. Very odd. Any help would be greatly appreciated. TIA.
PS - I'll keep trying to get registered and if I'm successful I'll come back to post my contact info
I'm getting exactly the same problem with my VPN clients. Routing and name resolution are fine but when I try to access an internal web server I get a reply from the web server saying "Error Code: 500 Internal Server Error. The pipe is being closed. (232). I can access external web servers fine. I can access internal file and email servers fine. A workaround I discovered is to use the Firewall Client in which case I can access the internal Web Servers. There is nothing in the firewall log except for some warnings about spoofed packets from the VPN client but these do not seem to have any ill effects - they do not occur when the web server problem occurs.