Hello Skunks, I have a situation where there are two office locations connected to each other using point-to-point link via a local provider. The point to point link capacity is 1Mbps. The quality of the link (latency) is pretty good: C:\>ping 192.168.3.20 Pinging 192.168.3.20 with 32 bytes of data: Reply from 192.168.3.20: bytes=32 time=19ms TTL=126 Reply from 192.168.3.20: bytes=32 time=21ms TTL=126 Reply from 192.168.3.20: bytes=32 time=20ms TTL=126 Reply from 192.168.3.20: bytes=32 time=24ms TTL=126 Ping statistics for 192.168.3.20: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 24ms, Average = 21ms Now, I have a camera (D-Link DCS-950G) installed at location A. It's a basic IP camera anyways. It's only accessible via IE (and I hate that, but that's another story). I have a problem with the image when accessing the camera across the WAN - it only gives a black box and no image displays. I am basically at /etc with this one:) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube
Hi @Wash, the problem with not being able to view the images could be because of the firewall. *Most IP cameras use jpeg streaming so need those udp ports open*. Check on the jpeg strem requirements of the camera, the ports will be listed. HTHs. :-)
Or @Wash, I'm sure you using *nix, pls check the log on FW and you see the brute force from the camera on that udp port. On Tue, Oct 13, 2009 at 7:58 PM, aki <aki275@googlemail.com> wrote:
Hi @Wash, the problem with not being able to view the images could be because of the firewall. *Most IP cameras use jpeg streaming so need those udp ports open*. Check on the jpeg strem requirements of the camera, the ports will be listed. HTHs. :-)
On Tue, Oct 13, 2009 at 8:34 PM, aki <aki275@googlemail.com> wrote:
Or @Wash, I'm sure you using *nix, pls check the log on FW and you see the brute force from the camera on that udp port.
@Aki, In the scenario I am, I can surely tell I am s%$#d up. The network setup was done by some fellows and looks something like this: LAN 1 --> Netscreen <-- 1Mbps --> Netscreen <-- LAN2 --> ISA Firewall ----> Internet | | | | Cisco 1 (acts as GW/DHCP) --> VoIP tunnel ---> Cisco 2 (Another VoIP tunnel to the Internet) *but is not directly connected to Netscreen* Within the setup there are 3 Avaya PBXes :-) It would appear that the Netscreens are the ones causing me grief?? Lan 1 cannot RDP to LAN 2 as well which, according to your statement, seems to be something to do with UDP filtering, right? This is a network that I feel needs reworking, but for now I just want to figure out the camera issue. Let me delve deep! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube
@Wash, I bet you your camera is on the ISA server side. ( I'm guessing ) Microsoft really went out on ISA, difficult cookie to crack.... Anyway, if the camera is on the ISA side, pls check the publish list i.e allowed hosts/ports and open as necessary in both directions. Or on the ISA box, save the current setting as a template. Then set ISA with allow all internet settings, and test the camera. I have forgetton the name of the packet tool that one can download for ISA, this thing even checks signatures. HTHs.
@Wash, I remembered one more thing. Netscreen has a web gui and so pls access and enable capture log. The log is not very elaborate but will also help. But please keep you focus on udp ports, that where all the problems are. Hope you are able to get out of your predicament soon. :-)
participants (2)
-
aki -
Odhiambo Washington