| Stefan Richter 2006-01-08, 7:45 am |
| Wow those connection times are pretty big...
I definitely recommend letting port 1935 pass. If your server is not set up
to allow connections on other ports apart from 1935 then that's why you are
failing to connect.
You may have port 1935 blocked locally but your client has not, therefore
the client can connect ok (using 1935) and you can't.
Flash Player will try other ports and my server (the one you were testing
against) has other ports bound too (80 and 443).
Without access to your server config I don't think I'll be able to help any
further from here. Looking at your server config should make the problem
should be easy to solve. At least you'd then know where the connection is
being blocked, right now I would guess that your server runs fine but only
allows port 1935 which is probably blocked locally at your end (but not at
your client's end).
Stefan
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Karina Steffens
> Sent: 08 January 2006 12:24
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] Failure to connect to FlashComm
> serverwithFlashPlayer8
>
> Hi Stefan, the test returns this:
>
> WIN 8,0,22,0
>
> RMTP Default Success 23.4s
> RMTP Port 1935 Failed 23.5s
> RMTP Port 80 Success 2.6s
> RMTP Port 443 Success 3.4s
> RMTPT (Tunneling) Default Success 5.4s
> RMTPT (Tunneling) Port 80 Success 6.1s
> RMTPT (Tunneling) Port 443 Success 5.7s RMTPT (Tunneling)
> Port 1935 Failed 21.7s
>
> Hmm... Isn't 1935 the default port for flashComm? I guess
> that's just a question of opening the port.
>
> A - that's what threw me at first, you see there were two
> different problems which I thought were one. First of all, I
> had a failure to connect to the localhost from IE-F8 but not
> from Firefox-7 and standalone, but I solved that with the settings.
>
> The failure to connect to the client's site I tought was the
> same thing, so I wasn't even thinking firewalls or ports, but
> it wasn't. I only tried to connect to it from IE, because the
> online version had another bug that made firefox impossible
> to use (that is, using 100% scale, Firefox displayed it too
> small to even log in. I'm fixing it in the next version).
> After making a new test version that was firefox friendly, I
> couldn't connect with either.
>
> Karina
>
>
>
> Behalf Of <a />
> could connect
> client had no
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf
> FlashComm
> remotely from
> trouble with
> connection path
> server from
> http://www.figleaf.com
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
> the archive:
> =-----------------------------------------------------------
> =-----------------------------------------------------------
> =-----------------------------------------------------------
> =-----------------------------------------------------------
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|