11-02-2013 8:58 AM
I tried to connect to VPN servers via AGN client. However, all the VPN servers assigned to my account/userid did not work, and I always met "Error 243 SSL protocol negotiation failed" since last week. Before that, my connection was well, and I did nothing to any of the configuration of my computer, network and AGN client.
One of my friends tried his account/userid on my computer, it went well. The only difference was his account/userid was HHKK/HD016985, but mine is HKUS/HU999360. The successful connecting of his account identified that there was nothing wrong with the network, and my ISP. Please help to check what happened to my account/userid and the VPN servers assigned to me as following.
1) 126.96.36.199 SSL H=0x54 P=0x07 AGN SIG AGNS AGN Managed
2) 188.8.131.52 SSL H=0x54 P=0x07 AGN SIG AGNS AGN Managed
3) 184.108.40.206 SSL H=0x54 P=0x07 AGN SIG AGNS AGN Managed
4) 220.127.116.11 SSL H=0x54 P=0x07 AGN SIG AGNS AGN Managed
Attached is the log file for your reference. Thanks
Solved by: Go to Solution.
11-05-2013 6:14 AM
I see in the logs that you are trying to connect SSL. Can you please switch to IPSec and try the connection again?
I would like to see if IPSec connections are working.
Open the AT&T Global Network Client, click on Settings and then Login Properties. On the General tab under Network Services click on Configure and click Next until you get to the Network Screen. In the drop down box switch from SSL to IPSec and try the connection again.
Please let me know if you get an error with IPSec.
11-05-2013 8:21 PM
The attached is the log for IPSec. My account HKUS.HU999360 failed to work yet.
My friend also tried his account HHKK.HD919648 on IPSec on my computer, his account worked well.
So, there is no problem about my home network and ISP. Something must be wrong at the server side or the VPN assignment for my account. Please help to check.
11-06-2013 12:58 PM
We found a configuration issue on your ID. It has been corrected. Please try the connection again and let me know if you see any errors.
01-29-2014 10:56 AM
I tried to connect to VPN servers via AT&T client. However, all the VPN servers assigned to my account/userid did not work, and I always met "Error 243 SSL protocol negotiation failed" since last week and I observed this after moving to Win7 from Win XP.
All of friends are able to connect with out any issues. Please let me know how do I correct configuration issue as you did for one of the posting here. Please let me know.
01-29-2014 11:18 AM
Please attach the support logs to this post.
Open the AT&T Global Network Client, click Help and select Create Support Log.
03-04-2014 12:20 PM
Hi I am an employee of IBM India and now in Belgium, there are two more IBM India employees with me and rest of the team is from belgium. Since I have migrated to windows7 my I am not able to connect AT&T VPN getting attached error and it happens only when I try to connect from client internet connection. Only we three are facing this issue rest of the team is able to connect with client internet and with windows7. We tried very hard but no sucess.
I am attaching here long file you will fine there are some sucessfull connection which is using my home internet connectiona and some failed connection which I tried with client internet connection.
AT&T Version 18.104.22.16803
Account/User ID =[edited for privacy]
Moderator: Your post has been edited due to personal information. Please follow all guidelines when participating in the Business Community. The Community Guidelines can be found HERE.
03-05-2014 7:19 AM
Hello, it looks like something may be blocking VPN access. In AGNC check to see if Use Ephemeral source ports for IPSec is checked on. You can do this by clicking on Settings, Login Properties, Preferences Tab. Then click on Override defaults and scrool down to VPN details section, and ensure this is checked on. Exit AGNC and launch and try again.
Also, below is a link to the admin document which lists in "Appendix C" on the requirements for the local Firewall/Network to allow VPN traffic. You may need to check with the loca IT Staff to ensure this is allowed.
05-06-2014 3:19 PM
Hi, I started getting the 243 SSL Protocol Negotiation Failed message two weeks ago when trying to connect from a client site that uses a proxy server. I don't believe I changed anything, worked on a Friday, not on Monday. HTTP and HTTPS are both pointed at the same proxy ports. Works fine from locations that are not behind a proxy.
05-07-2014 12:52 PM
If it was previously working from that location and you didn't change anything, maybe something at the client site changed.
Can you ask the Proxy Administrator at that location to check their logs to see what is happening to your connection?
05-07-2014 2:07 PM
I can ask. I'm at a customer location so have limited access to the administrators. fwiw, there are other users of AGNC at the same location who are having no issues getting through the same proxy and a few who are getting the 243 error.
07-24-2014 4:34 AM
I am trying to connect AT&T but getting error "!Error 243 SSL protocol negotiation failed."
I switch to IPSec also but it doesn't work
Here is my System log detail.
Could you please help
07-24-2014 4:38 AM
Can you please help me to get resolve the issue :
I am not able to connect to At&T network at client place some setting is being missing .
It's being working fine for my other colligue so it's not related to client network issue ,
I switch to IPSecfrom SSL doesn;t help
Pls find enclosed the log
12-10-2014 11:17 AM
I'm an employee of IBM India and located in City of Kolkata. I used to connect through AT&T vpn client to my company network Tata Teleservices broadband connection. Since last Saturday I started getting "243 SSL Protocol Negotiation Failed". I have retried after resetting my ADSL modem however the problem is consistently appearing and unable to connect to my organization's network. However, when I connect using my mobile phone (Samsung Galaxy S4) as a hotspot, I'm not getting the error and can connect successfully. Can you please help resolve my problem? Thanks in advance. Attached the support log.