Old question again ! ARD Port 3283

Question

Old question again ! ARD Port 3283

We control 16 workstations with ARD 2.2. 15 of the workstations are inside
our LAN, and work great, and one is controlled via Pub IP, and forwarded to an internal IP. the problem is, we don't have full control (port 3283) on the internet connection and only VNC is available. According to our IT, there is no port restrictions, firewalls are off at both ends. He's indicated that our ISP is not trapping any ports, but obviously it's being filtered somewhere. I've used Network Utilities to verify open ports, however only 5900 shows up in the scan. Appently Net Util's only shows TCP not UDP. Anyway to verify port operation from this end?
It would truly be nice to have port 3283 working for other admin duties. Any thoughts or suggestions as to the remedy would be greatly appreciated.
Spec's: Mostly G5's running OSX 10.3.9, ARD 2.2. Connection ISP is Netifice over T1 both ends. Copper is Verizon and SBC. TIA

Posted on Oct 5, 2005 10:35 AM

Reply

Answer 1

varjak paw

Level 10

182,668 points

Oct 5, 2005 1:02 PM in response to Steve Hallquist

Network Utility will indeed scan for that port. I just tested it against one of my workstations to verify that it correctly reported that port as open. So if your port scan isn't showing that port as open, either it's being blocked at a router somewhere between the systems (regardless of what your IT/ISP is telling you) or access is not properly enabled on the workstation.

Reply

Answer 2

Oct 5, 2005 2:34 PM in response to varjak paw

Well heres the problem. When I scan our internal LAN which has the 14 workstations that DO work, it doesn't show UDP 3283 as open, only tcp 5900, which is what it I get with the T1 remote site, so I don't believe that network utilities reports UDP ports, only TCP 5900. But I have been known to wrong.
Thanks

Reply

Answer 3

varjak paw

Level 10

182,668 points

Oct 5, 2005 3:00 PM in response to Steve Hallquist

Hmmm... perhaps a difference in Network Utility between Mac OS X 10.3 and 10.4, because it does report 3283 for me. You might try a different port scanning tool (perhaps IPNetMonitor) and see if you get a proper scan of 3283 on the internal workstations. Then you can test the remote one and have useful information.

Reply

Answer 4

Oct 6, 2005 8:47 AM in response to varjak paw

Thanks Dave for the IPNetMonitor call, it does report UDP 3283 on the local LAN. When I scanned the outside remote location, it too says that port TCP 5900 and UDP 3283 are operational. So I'm further at a lose to understand why I can only operate that connection VNC mode only.
Any further ideas or should I just let it go for now?
TIA

Reply

Answer 5

varjak paw

Level 10

182,668 points

Oct 6, 2005 8:54 AM in response to Steve Hallquist

3283 should be open for both UDP and TCP, so if it's only open for UDP, that's most likely your problem, and my guess is that the problem is in the router configuration somewhere.

Reply

Answer 6

Oct 6, 2005 9:29 AM in response to varjak paw

Again - thanks for the direction. I believe I've traced problem to our ISP (Netifice), who seemed to be blocking 3283 through their router, enough though our IT says they aren't. So its on to the source. My guess is they'll charge us an additional fee to open port.
Thanks again.

Reply