178 reputation
128
bio website stackoverflow.com/users/57630/…
location London, United Kingdom
age 42
visits member for 5 years
seen Jul 22 at 9:01

I am a total newbie when it comes to programming (been like that for the last 12 years!). I dabble a lot and have built websites and Windows apps, but I don't consider myself a programmer, as I don't really know whether I am doing it right. (but my applications and websites work, just don't know if I am using the best methods and techniques etc... example I once used a DataTable rather than a Generic.Dictionary - Newbie!!! - But don't worry I have fixed that now. ;))

Currently a Support Manager/IT Manager for an MIS software company.

Thoroughly enjoying MongoDB, Node.JS and Express at the moment.


May
17
awarded  Student
Apr
13
comment Office Communicator Crashes when opened
I am having the same issue but for me it appears to be as it tries to connect to Exchange on BPOS. Just constantly crashes. I have installed the hotfix you note, but it still does it.
Nov
15
awarded  Famous Question
May
11
awarded  Notable Question
Mar
6
awarded  Popular Question
Jan
7
comment Windows 7 VPN Error 619
harrymc, thanks for the time you have put in, the effort is appreciated.
Jan
5
awarded  Commentator
Jan
5
comment Windows 7 VPN Error 619
harrymc, not really. The client is definitely on a different range to us, in fact they were one of the reasons we changed from a 192.x.x.x range to a 10.x.x.x one. So if you are thinking that we might be having a range clash, then I don't think so... unless you are thinking of something else.
Dec
31
comment Windows 7 VPN Error 619
Yes, XP was also blocked from internal network (or external I guess technically, http and others do not work, ie GTalk, Web etc). It still is blocked after the IP Range change.
Dec
31
comment Windows 7 VPN Error 619
I have tried it both with Auto-Tuning disabled and set to normal, no difference unfortunately. I have also done some further testing with other clients and there are a couple of other VPNs that are no longer working. There also seems to be a common link between the ones that are working and the ones that aren't. The ones that aren't working, previously when connected to them you would lose your internal network functions, ie http etc. The ones that still work, you always had access to the internal network also. Not sure if that makes any difference to the possible solution though.
Dec
29
comment Windows 7 VPN Error 619
I agree with the logic, but am sure nothing changed on their end as they were all on holidays at the time. I still keep coming back to the fact that the XP machines are still working fine. I think there must be some sort of mapping or something (shouting out ideas only) like firewall rules etc that is causing this to happen. Thanks again harrymc.
Dec
29
comment Windows 7 VPN Error 619
It appears so yes. I have tried to replicate the settings of the ones that are working to the one that isn't but no luck.
Dec
29
comment Windows 7 VPN Error 619
Last gasp is how I feel about it also harrymc. Thanks for your efforts. The VPN Server I am trying to get to is Windows 2003 server. I think it supports MS-CHAP v2, but the key to this is that prior to the internal IP address change on my network, my Win7 machine could connect to it using the same settings. In fact my Win 7 machine at home can still connect to it so I think it must be linked to firewall, router or similar, but will try your suggestions also. "include Windows Logon Domain" was already unchecked.
Dec
29
revised Windows 7 VPN Error 619
added 374 characters in body; added 463 characters in body
Dec
29
awarded  Editor
Dec
29
revised Windows 7 VPN Error 619
added 415 characters in body
Dec
29
comment Windows 7 VPN Error 619
Harrymc, thanks for sticking with me on this. I have tried everything you have mentioned in your edit and still no difference unfortunately.
Dec
29
comment Windows 7 VPN Error 619
Yes the VPN is outside of our network. Yes the WIN 7 machine connects fine to everything else. I have tried this with all firewalls turned off as my google research suggested that it might have been a firewall problem. I am also having the same issue with Vista machines that worked fine prior to the IP address change, although I intermittently had issues with Vista on SP1.
Dec
27
comment Windows 7 VPN Error 619
Thanks for your reply harrymc. The internal network range changed from 192.x.x.x to 10.x.x.x. This was done on the entire Active Directory. All machines are running fine and the Windows XP machine, that works going to the same client VPN mentioned above is on the same network. Both the XP and the Win 7 machines are using DHCP served by the Domain Controller. The client domain is not performing any IP range checks/restrictions.
Dec
27
asked Windows 7 VPN Error 619