Troubleshooting steps:
Run Wowza from a CMD prompt using [Wowza]/bin/startup.bat. Then post the console output here so we can see if Wowza is binding to port 8086.
Configure logging: file:///D:/Program Files (x86)/Wowza Media Systems/Wowza Media Server 3.0.5/conf/log4j.properties
INFO server server-start Wowza Media Server 3 Trial Edition (Expires: Mar 31, 2012) 3.0.5 build1220 -
INFO server comment - Server License Key: SVRT3-XXXXX-XXXXX-XXXXX-XXXXX-jDRUh
INFO server comment - Maximum Connections: Unlimited
INFO server comment - Transcoder Streams Available: Unlimited
INFO server comment - Transcoder Watermark: Yes
INFO server comment - nDVR Available: Yes
INFO server comment - DRM Available: Yes
INFO server comment - Hardware Available Processors: 8
INFO server comment - Hardware Physical Memory: 15070MB/16373MB
INFO server comment - Hardware Swap Space: 31153MB/32745MB
INFO server comment - Max File Descriptor Count: Unlimited
INFO server comment - OS Name: Windows Server 2008 R2
INFO server comment - OS Version: 6.1
INFO server comment - OS Architecture: amd64
INFO server comment - OS CPU: amd64
INFO server comment - Java Name: Java HotSpot(TM) 64-Bit Server VM
INFO server comment - Java Vendor: Oracle Corporation
INFO server comment - Java Version: 1.7.0_03
INFO server comment - Java VM Version: 22.1-b02
INFO server comment - Java Spec Version: 1.7
INFO server comment - Java Home: D:\Program Files\Java\jdk1.7.0_03\jre
INFO server comment - Java Max Heap Size: 682MB
INFO server comment - Java Architecture: 64
INFO server comment - Java Locale[user.language]: en
INFO server comment - Java Locale[user.country]: US
INFO server comment - Java Locale[user.variant]:
INFO server comment - Java Locale[file.encoding]: Cp1252
INFO server comment - Java Args[0]: -Xmx768M
INFO server comment - Java Args[1]: -Dcom.sun.management.jmxremote=true
INFO server comment - Java Args[2]: -Dcom.wowza.wms.runmode=standalone
INFO server comment - Java Args[3]: -Dcom.wowza.wms.native.base=win
INFO server comment - Java Args[4]: -Dcom.wowza.wms.ConfigURL=
INFO server comment - Server runmode: standalone
INFO server comment - Server native.platform: win
INFO server comment - Server threads[h/t]: 10/10
INFO server comment - CMDInterface now listening: [any]:8083
INFO vhost vhost-start _defaultVHost_ -
INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:D:/Program Files (
x86)/Wowza Media Systems/Wowza Media Server 3.0.5
INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
INFO server comment - Wowza Media Server is started!
I’m seeing “INFO vhost comment defaultVHost Bind attempt ([any]:8086:1)” and “INFO vhost comment defaultVHost Bind successful ([any]:8086)”, so I guess it’s binding and that’s not the problem.
If it is, then test that you can connect from the server computer using a web browser. You can use a command-line browser like links or lynx. Then turn off your firewall and test from a remote computer.
I can’t connect to the server at all using a web browser. I’m working under somebody on this, and I know the server does NOT have IIS set up. He thinks that it isn’t needed and that WMS is capable of serving HTTP on it’s own. Is this really the case?? I’m almost 100% certain not having IIS is the problem here. So…
Does WMS3 need IIS to serve the stream manager? WMS3 is NOT able to serve http on it’s own, correct?
Thanks again for reading and for replying Richard and Randall!