Having an odd behavior on a new install of wowza. I reboot the machine, try the content, it tells me connection can’t be established. I then disable the firewall, connect from a system and it plays. I then re-enable the firewall, try the content on a different system, and it plays now through the firewall. It’s almost like port 1935 won’t open until one system has made the connection.
I am running windows 2008, 64 bit, using echo360.
That is very odd behavior. I have not heard of this before. I assume you have TCP port 1935 open on your firewall.
Charlie
If you are using an RTSP/RTP, native RTP or MPEG-TS encoder then the UDP ports need to be opened incoming as well.
Charlie
Glad to hear you got this sorted out.
Charlie
No, that is the beauty of Java. It will take advantage of a 64-bit platform when run on a 64-bit platform.
Charlie
yes, port 1935 is open, I can see the systems connect with the firewall up once that first connection is made. It just seems to reject that intial connection. Wowza is up and running with a service account.
The udp ports are outgoing only right, they don’t need to be open incoming too?
windows 2008 (and vista) don’t support a range of ports in the gui. Only 1 port at a time. Any ideas on how to open all the udp ports via command line?
Thanks for all the help. We noticed the firewall acting oddly on several windows 2008 servers. It took command line work to get the firewall to open all the time.
Hi Charlie,
I have small query do we have any different version of wowza for 64 bit machine. I want to install wowza on a 64 bit machine now. Please can you answer my query ASAP.