Cannot login anymore: The operation has timed out

[cooldad]

When I startup Betting Assistent, after entering user name and password, I receive the following error:

System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Betting_Assistant.betfair.BFGlobalService.login(LoginReq request)
at Betting_Assistant.Main.doLogon(Boolean loginAuto)

I´ve checked the BetFair API System Status, it is OK (Good Service)

Using a java sample application that uses the BetFair API, I can logon without any problems. I have disabled the firewall, even restarted my PC, without succes.

Any idea what this can be?

Thanks!

[cooldad]

Here´s some trace information, it seems it can connect to Betfair ok:


No. Time Source Destination Protocol Info
69 5.496017 9.142.105.47 130.103.134.78 HTTP GET http://www.gruss-software.co.uk/Betting ... essage.txt HTTP/1.1

Frame 69 (313 bytes on wire, 313 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-s (1433), Dst Port: http (80), Seq: 1, Ack: 1, Len: 259
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
70 5.496026 9.142.105.47 130.103.134.78 HTTP [TCP Out-Of-Order] GET http://www.gruss-software.co.uk/Betting ... essage.txt HTTP/1.1

Frame 70 (313 bytes on wire, 313 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-s (1433), Dst Port: http (80), Seq: 1, Ack: 1, Len: 259
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
74 5.557950 130.103.134.78 9.142.105.47 HTTP HTTP/1.1 200 OK (text/plain)

Frame 74 (466 bytes on wire, 466 bytes captured)
Ethernet II, Src: Cisco_75:e8:ff (00:0d:bd:75:e8:ff), Dst: Ibm_48:3c:0d (00:11:25:48:3c:0d)
Internet Protocol, Src: 130.103.134.78 (130.103.134.78), Dst: 9.142.105.47 (9.142.105.47)
Transmission Control Protocol, Src Port: http (80), Dst Port: ms-sql-s (1433), Seq: 1, Ack: 260, Len: 412
Hypertext Transfer Protocol
Line-based text data: text/plain

No. Time Source Destination Protocol Info
170 13.797837 9.142.105.47 130.103.134.78 HTTP CONNECT api.betfair.com:443 HTTP/1.1

Frame 170 (146 bytes on wire, 146 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-m (1434), Dst Port: http (80), Seq: 1, Ack: 1, Len: 92
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
171 13.797846 9.142.105.47 130.103.134.78 HTTP [TCP Out-Of-Order] CONNECT api.betfair.com:443 HTTP/1.1

Frame 171 (146 bytes on wire, 146 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-m (1434), Dst Port: http (80), Seq: 1, Ack: 1, Len: 92
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
173 13.811743 130.103.134.78 9.142.105.47 HTTP HTTP/1.0 200 Connection established

Frame 173 (93 bytes on wire, 93 bytes captured)
Ethernet II, Src: Cisco_75:e8:ff (00:0d:bd:75:e8:ff), Dst: Ibm_48:3c:0d (00:11:25:48:3c:0d)
Internet Protocol, Src: 130.103.134.78 (130.103.134.78), Dst: 9.142.105.47 (9.142.105.47)
Transmission Control Protocol, Src Port: http (80), Dst Port: ms-sql-m (1434), Seq: 1, Ack: 93, Len: 39
Hypertext Transfer Protocol

No. Time Source Destination Protocol Info
174 13.818790 9.142.105.47 130.103.134.78 SSL Client Hello

Frame 174 (124 bytes on wire, 124 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-m (1434), Dst Port: http (80), Seq: 93, Ack: 40, Len: 70
Hypertext Transfer Protocol
Secure Socket Layer

No. Time Source Destination Protocol Info
175 13.818809 9.142.105.47 130.103.134.78 SSL [TCP Out-Of-Order] Client Hello

Frame 175 (124 bytes on wire, 124 bytes captured)
Ethernet II, Src: Ibm_48:3c:0d (00:11:25:48:3c:0d), Dst: All-HSRP-routers_01 (00:00:0c:07:ac:01)
Internet Protocol, Src: 9.142.105.47 (9.142.105.47), Dst: 130.103.134.78 (130.103.134.78)
Transmission Control Protocol, Src Port: ms-sql-m (1434), Dst Port: http (80), Seq: 93, Ack: 40, Len: 70
Hypertext Transfer Protocol
Secure Socket Layer

No. Time Source Destination Protocol Info
176 13.829986 130.103.134.78 9.142.105.47 TCP http > ms-sql-m [ACK] Seq=40 Ack=163 Win=8122 Len=0

Frame 176 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: Cisco_75:e8:ff (00:0d:bd:75:e8:ff), Dst: Ibm_48:3c:0d (00:11:25:48:3c:0d)
Internet Protocol, Src: 130.103.134.78 (130.103.134.78), Dst: 9.142.105.47 (9.142.105.47)
Transmission Control Protocol, Src Port: http (80), Dst Port: ms-sql-m (1434), Seq: 40, Ack: 163, Len: 0

[GaryRussell]

Have you also tried rebooting your router?

[cooldad]

I've reset the cable modem, as wel as the router. I've uninstalled and installed Betting Assistant, I´ve even uninstalled and installed my network drivers. But it still doesn´t work. I have another PC in my network that doesn´t have a problem

This time, I am getting a different exception:

---------------------------
Betting Assistant
---------------------------
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Betting_Assistant.betfair.BFGlobalService.login(LoginReq request)
at Betting_Assistant.Main.doLogon(Boolean loginAuto)

Any other suggestions?

Thanks.

[GaryRussell]

Check your firewall settings, it may be blocking BA from making outgoing connections.

[cooldad]

I know it is difficult to believe, but it is definitely not the Firewall. I had allowed al traffic for Betting Assistant, but just to make sure, I had disabled the firewall. To be even more sure, I´ve removed all Symantec services from the startup sequence, so now Symantec Firewall doesn´t even start (as is confirmed by the missing icon in the task bar). But I still have the same problem (:-<)

I am really out of ideas here...

[GaryRussell]

Find the file named Betting Assistant.exe in the folder c:\program files\betting assistant beta and rename it to Betting Assistant1.exe. Run this program and see if it works, if it does it really does suggest that there is something on your PC blocking the program.

[cooldad]

Good news, it´s working again. In the network trace I made, I saw an IP address of a proxy server I configured in Internet Explored to access an Intranet application. In IE, I removed the proxy settings, and now everything is working again.

I did not realize that settings in IE did have this effect, but I am sure I will never forget this....

[GaryRussell]

Yes, it uses the proxy server you have configured in IE. Sorry, I didn't think to mention this as the error messages didn't suggest this was the problem.

[cooldad]

It´s ok, most important thing is, it´s working again. I guess we both learned something today