Thanks for responding. I mentioned most of what you asked for in the other thread I linked to, but here's the answers:
- I'm running Windows XP SP3, but it's not OS related (see below).
- I have no problem connecting to any other internet sites (except https://tificocs.symantec.com/ see below for more info)
- I am behind a router, but I've bypassed it for testing purposes and connected directly to my cable modem. I've also rebooted my modem.
- I have yet to run One Click Support successfully under NIS 2010. I have run it succesfully under NIS 2009 in the past, but the last time I did so was Aug 18, 2009 (it worked fine then).
More details:
I only have NIS 2010 installed on my laptop, so to test things I use a web browser to see if the "403 Forbidden" error shows up when I go to the OCS site manaully in the browser. If it shows up I know that the server responded. If I see nothing or a "page could not be displayed" error I know something is wrong.
Here's what I've determined by testing to see if manually connecting to the OCS site displayed "Forbidden" or timed out:
- It's not my router since I've bypassed the router and connected my laptop directly to my cable modem.
- It's not my laptop since I don't get a response from the OCS site manually on another PC I have (without NIS on it), nor do I get a response with my PS3's web browser.
- Using various proxies around the country gets me different results ("403 Forbidden" versus "page could not be displayed" error) when manually connecting the the OCS site. I don't know what the pattern is exactly, but I know I get "Forbidden" at my office, but a "page error" at home. Unfortunately One Click Support can't be run through a SSL proxy. The main difference here though is that in one case the server is returning an APPLICATION DATA SSL packet ("Forbidden") and in the other case it returns an ENCRYPTED ALERT SSL packet (no data). I haven't tried a public hot spot to see if that works.
- The server is returning some rather odd error packets, including DUP ACKs and ZeroWindow. The later in itself is indication of some kind of server problem.
The problem appears to affect some people, but not others.
People affected:
Me (at home)
Jimbo40
EsieB
csoyen (has screen shots of issue)
People not affected:
chatham
Here's the last few packets when try to connect to the OCS server when running OCS in NIS 2010. After the DUP ACK, the server seems to stop processing data and then simply closes the connection.:
No. Time Source Destination Protocol Info
224 59.078548 192.168.1.6 204.232.134.16 TCP [TCP segment of a reassembled PDU]
225 59.078600 192.168.1.6 204.232.134.16 TCP [TCP segment of a reassembled PDU]
226 59.078783 204.232.134.16 192.168.1.6 TCP https > btpp2sectrans [ACK] Seq=123 Ack=40541 Win=6768 Len=0
227 59.089992 204.232.134.16 192.168.1.6 TCP https > btpp2sectrans [ACK] Seq=123 Ack=43301 Win=4008 Len=0
228 59.115296 204.232.134.16 192.168.1.6 TCP https > btpp2sectrans [ACK] Seq=123 Ack=46061 Win=1248 Len=0
229 59.302378 204.232.134.16 192.168.1.6 TCP [TCP Dup ACK 228#1] https > btpp2sectrans [ACK] Seq=123 Ack=46061 Win=1248 Len=0
230 64.039600 192.168.1.6 204.232.134.16 TCP [TCP segment of a reassembled PDU]
231 64.303352 204.232.134.16 192.168.1.6 TCP [TCP ZeroWindow] https > btpp2sectrans [ACK] Seq=123 Ack=47309 Win=0 Len=0
234 65.146038 192.168.1.6 204.232.134.16 TCP [TCP ZeroWindowProbe] btpp2sectrans > https [ACK] Seq=47309 Ack=123 Win=65413 Len=1
235 65.168531 204.232.134.16 192.168.1.6 TCP [TCP ZeroWindowProbeAck] [TCP ZeroWindow] https > btpp2sectrans [ACK] Seq=123 Ack=47309 Win=0 Len=0
236 66.956667 192.168.1.6 204.232.134.16 TCP [TCP ZeroWindowProbe] [TCP segment of a reassembled PDU]
237 66.978946 204.232.134.16 192.168.1.6 TCP [TCP ZeroWindowProbeAck] [TCP ZeroWindow] https > btpp2sectrans [ACK] Seq=123 Ack=47309 Win=0 Len=0
240 70.577857 192.168.1.6 204.232.134.16 TCP [TCP ZeroWindowProbe] [TCP segment of a reassembled PDU]
241 70.600318 204.232.134.16 192.168.1.6 TCP [TCP ZeroWindowProbeAck] [TCP ZeroWindow] https > btpp2sectrans [ACK] Seq=123 Ack=47309 Win=0 Len=0
254 77.820027 192.168.1.6 204.232.134.16 TCP [TCP ZeroWindowProbe] [TCP segment of a reassembled PDU]
255 77.848946 204.232.134.16 192.168.1.6 TCP [TCP ZeroWindowProbeAck] [TCP ZeroWindow] https > btpp2sectrans [ACK] Seq=123 Ack=47309 Win=0 Len=0
267 88.754329 204.232.134.16 192.168.1.6 TLSv1 Encrypted Alert
268 88.754499 192.168.1.6 204.232.134.16 TCP btpp2sectrans > https [ACK] Seq=47309 Ack=147 Win=65390 Len=0
269 88.754620 204.232.134.16 192.168.1.6 TCP https > btpp2sectrans [RST, ACK] Seq=147 Ack=47309 Win=0 Len=0