Question: I have someone trying to VPN into our Network. She is using Windows XP Pro, we are running an NT 4.0 server . PPTP is the tunneling protocol. She receives error 619. I have other users using XP Pro and they can access via dialup. All my other users use 2000. So no issues there. Any ideas what her problem might be. I also had her disable her Black Ice firewall and the service that it runs as. I'm open for any ideas! Thanks. Ps. We are not running active directory at this time, although we have the mix of W2K and NT 4.0 servers.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
XP VPN to NT 4.0 Server via Comcast cable
- Thread starter stempert
- Start date
- Thread starter
- #2
John Lewis
Programmer
Well, not a real common problem. Couldn't resist, had to dig around a bit. I found null. Almost. Microsoft says that error 619 indicates 'The port is disconnected'. Says a lot, don't it.
Only other KB reference is here:
Doesn't sound exaclty applicable, but it does give some clue. It indicates to me that error is thrown after the initial link is made but before or during the process of authenticating the connection. I think this eliminates firewall/routing problems. I would check the appropriate settings on the client that control the way the authentication info is sent. In particular, W2K client has a box that says 'Include Windows logon domain.' I don't have a XP box in front of me right now, but I am thinking it is there as well.
Failing that, have you turned on logging? Should be something in the link configuration portion that would shed some light. Good luck!
Only other KB reference is here:
Doesn't sound exaclty applicable, but it does give some clue. It indicates to me that error is thrown after the initial link is made but before or during the process of authenticating the connection. I think this eliminates firewall/routing problems. I would check the appropriate settings on the client that control the way the authentication info is sent. In particular, W2K client has a box that says 'Include Windows logon domain.' I don't have a XP box in front of me right now, but I am thinking it is there as well.
Failing that, have you turned on logging? Should be something in the link configuration portion that would shed some light. Good luck!
- Thread starter
- #4
Thanks for the efforts. I found the same info. I check the event log on the server and it shows no attempts of that particular client trying to connect. I already had the client using the domain option. I had her try a few more items in the firewall settings built into XP. If that doesn't work I will make her set all the tcpip choices such as gateway dns wins and such. I'll let you know what we find Thanks again!
Does that VPN connection work over dial-up using an ISP? I've a similar problem. Win2K client can connect fine with VPN over dial-up ISP. And, connects just fine going through Comcast cable with Motorola cable modem. But, when I put a D-Link 614+ router between the cable modem and the Win2K client PC, get the same Error 619. Therefore, I assume it has something to do with the router. Good luck to us both!
many of the cable/DSL companies are nixing VPN tunnels these days, they are not happy about the loss of revenue stream when a business users use their "home" connection to tunnel into "work", they somehow nix the connection, most of the time requiring users to upgrade to a "business"
connection at a higher rate to be able to VPN.
maybe your problem, maybe not. just a thought.
connection at a higher rate to be able to VPN.
maybe your problem, maybe not. just a thought.
- Status
Similar threads
- Locked
- Question