Hi- This is my problem. I am trying to connect shockwave to a java app running on our ISP on port 35005. I have never had a problem before. However about ~1 year ago the company I work for upgraded their LAN from Windows -> Linux and since then I have not been able to connect with the java.
I am probably mixing the technical stuff around so I hope this makes sense.
If I open the shockwave in safari it cannot communicate with the java. The shockwave initiates the communication but the server - from the logs - never receives anything. That means the data never leaves my computer. The new sysadmin swears he has re-opened all the ports on the LAN - or proxy or firewall, whichever it is - and the confusing thing is that other computers on the network here have no problem running the shockwave and communicating with the java.
That leaves me wondering if maybe with some osx upgrade or security patch that followed sometime in the past year that has closed the port and that is the problem now. I have run network utility and of course port 35005 is not open - but why would it be, and does that necessarily mean that it wouldn't be opened when the shockwave was running?
I still am not sure whether the problem lies on my computer specifically - ie the data from the shockwave is refused _leaving_ my computer on port 35005?! - or if it's getting cut off at our LAN (firewall, proxy or whichever)?! eitherway it's not reaching the server when the shockwave is run on my computer specifically.
SO - how the heck do i test for this? how can i open ports - or force open ports via root - or otherwise know at exactly which point along the chain the data is getting stopped?! from my perspective running the shockwave it's as if the java is completely dead - no response at all, and like i said the data never even reaches the server - but on another PC in the office it works just fine!?
Please PLEASE help. This is my setup if it helps.
G4 running Mac OS X 10.3.8
DSL connection via Ethernet LAN with Proxy Server
LAN is running Debian something or other
Other than that i've opened up FTP sharing because that appears to involve ports 1024-65535 but that hasn't affected anything. Thanks again!
I am probably mixing the technical stuff around so I hope this makes sense.
If I open the shockwave in safari it cannot communicate with the java. The shockwave initiates the communication but the server - from the logs - never receives anything. That means the data never leaves my computer. The new sysadmin swears he has re-opened all the ports on the LAN - or proxy or firewall, whichever it is - and the confusing thing is that other computers on the network here have no problem running the shockwave and communicating with the java.
That leaves me wondering if maybe with some osx upgrade or security patch that followed sometime in the past year that has closed the port and that is the problem now. I have run network utility and of course port 35005 is not open - but why would it be, and does that necessarily mean that it wouldn't be opened when the shockwave was running?
I still am not sure whether the problem lies on my computer specifically - ie the data from the shockwave is refused _leaving_ my computer on port 35005?! - or if it's getting cut off at our LAN (firewall, proxy or whichever)?! eitherway it's not reaching the server when the shockwave is run on my computer specifically.
SO - how the heck do i test for this? how can i open ports - or force open ports via root - or otherwise know at exactly which point along the chain the data is getting stopped?! from my perspective running the shockwave it's as if the java is completely dead - no response at all, and like i said the data never even reaches the server - but on another PC in the office it works just fine!?
Please PLEASE help. This is my setup if it helps.
G4 running Mac OS X 10.3.8
DSL connection via Ethernet LAN with Proxy Server
LAN is running Debian something or other
Other than that i've opened up FTP sharing because that appears to involve ports 1024-65535 but that hasn't affected anything. Thanks again!