I am trying to get my computer to connect to an Adobe Connect server but I have had no luck. The error that Adobe is telling me is “ERROR: FMS Server did not return correctly!” and have done some narrowing down to figure out what the problem is…
- I know that its not a router issue because it still doesnt work when I bypass it, also Adobe Connect works fine on all my other computers in my network
- I have disabled the Windows Firewall (every which way) and that doesn’t do anything
- It is something to do with trying to connect to port 1935 on the server because I can connect to port 80 fine but not port 1935
- I have a VirtualBox and Virtual PC network driver installed and I disabled those with no success
- I had used a TCP optimizer and trying restoring the settings with no success
- The furthest the connection to port 1935 will go in netstat is to SYN_SENT so for some reason the server isn’t sending a ACK back
- It doesn’t work in Firefox, Chrome, or Internet Explorer (Yes, I made sure SSL and TLS are enabled)
I am wondering if this might be some sort of firewall problem but the thing is, I have Windows Firewall totally disabled and there are no other firewalls (that I know of) running. I thought this might be because I had Norton 360 installed but that wasn’t the problem. Any ideas?
UPDATE:
Here is the traceroute and nmap scan from the computer that CAN connect:
Tracing route to connect.bowvalleycollege.ca [199.185.132.114] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.1.1 2 36 ms 36 ms 37 ms d198-53-240-1.abhsia.telus.net [198.53.240.1] 3 44 ms 39 ms 38 ms 173.182.202.193 4 36 ms 36 ms 36 ms CLGRAB31GR01.bb.telus.com [154.11.10.170] 5 37 ms 35 ms 37 ms 154.11.2.218 6 49 ms 48 ms 48 ms core4-calgaryqa_gi6-0-0.net.bell.ca [64.230.77.252] 7 50 ms 50 ms 58 ms core4-calgary68_ge5-1-0.net.bell.ca [64.230.77.222] 8 48 ms 50 ms 48 ms core4-vancouver_pos11-1-0.net.bell.ca [64.230.77.207] 9 48 ms 49 ms 48 ms core1-vancouver_pos0-2-0.net.bell.ca [64.230.183.33] 10 49 ms 86 ms 48 ms bx2-vancouver_POS1-0.net.bell.ca [64.230.248.58] 11 99 ms 49 ms 48 ms 204.101.4.90 12 53 ms 51 ms 52 ms static-67-226-180-101.ptr.terago.net [67.226.180.101] 13 52 ms 53 ms 53 ms static-67-226-180-142.ptr.terago.net [67.226.180.142] 14 * * * Request timed out. 15 53 ms 51 ms 51 ms reddog.bowvalleycollege.ca [199.185.132.4] 16 53 ms 53 ms 53 ms vpn.bowvalleycollege.ca [199.185.132.9] 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Starting Nmap 6.01 ( http://nmap.org ) at 2012-09-29 12:14 Mountain Daylight Time Nmap scan report for connect.bowvalleycollege.ca (199.185.132.114) Host is up (0.057s latency). Not shown: 995 filtered ports PORT STATE SERVICE 80/tcp open http 113/tcp closed ident 443/tcp closed https 1433/tcp open ms-sql-s 1935/tcp open rtmp Nmap done: 1 IP address (1 host up) scanned in 13.23 secondsHere is the traceroute and nmap scan from the computer that CANT connect:
Tracing route to connect.bowvalleycollege.ca [199.185.132.114] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 38 ms 35 ms 36 ms d198-53-240-1.abhsia.telus.net [198.53.240.1] 3 42 ms 37 ms 37 ms 173.182.202.193 4 37 ms 37 ms 37 ms CLGRAB31GR01.bb.telus.com [154.11.10.170] 5 37 ms 37 ms 37 ms 154.11.2.218 6 48 ms 48 ms 48 ms core4-calgaryqa_gi6-0-0.net.bell.ca [64.230.77.252] 7 48 ms 47 ms 48 ms core4-calgary68_ge5-1-0.net.bell.ca [64.230.77.222] 8 49 ms 48 ms 48 ms core4-vancouver_pos11-1-0.net.bell.ca [64.230.77.207] 9 48 ms 48 ms 48 ms core1-vancouver_pos0-2-0.net.bell.ca [64.230.183.33] 10 47 ms 48 ms 47 ms bx2-vancouver_POS1-0.net.bell.ca [64.230.248.58] 11 47 ms 48 ms 46 ms 204.101.4.90 12 51 ms 52 ms 52 ms static-67-226-180-101.ptr.terago.net [67.226.180.101] 13 51 ms 52 ms 52 ms static-67-226-180-142.ptr.terago.net [67.226.180.142] 14 * * * Request timed out. 15 50 ms 49 ms 50 ms reddog.bowvalleycollege.ca [199.185.132.4] 16 52 ms 52 ms 52 ms vpn.bowvalleycollege.ca [199.185.132.9] 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Starting Nmap 6.01 ( http://nmap.org ) at 2012-09-29 12:27 Mountain Daylight Time Nmap scan report for connect.bowvalleycollege.ca (199.185.132.114) Host is up (0.054s latency). Not shown: 995 filtered ports PORT STATE SERVICE 80/tcp open http 113/tcp closed ident 443/tcp closed https 1433/tcp open ms-sql-s 1935/tcp open rtmp Nmap done: 1 IP address (1 host up) scanned in 18.50 secondsI think you will see by comparing these scans that they are the same. I have no control over
connect.bowvalleycollege.caso whatever the problem is should be able to be fixed on my end.
Answer
After a few months of not being able to connect, I tried again one day to connect and it worked no problem. I’m guessing the problem was something to do with Adobe Connect because it was updated a few days before. I seem to recall trying to contact Adobe about this issue and they said it was something to do with my computer or network configuration.
Attribution
Source : Link , Question Author : ub3rst4r , Answer Author : ub3rst4r
