Hi,
Sorry for the strange title, but i cant seem to find any logic in this problem..
We have a 3rd party application for control of our VoIP system, and it uses TCP port 3333 to connect to the server that runs the application, and when one of my DirectAccess clients tries to start the application (it runs from a UNC-path) the application starts fine, but it cant connect to the server.
My first thought - there must be some element in the server / client configuration tied up on a IPv4 address. I checked everything, and asked the developers of the software, and there wasn't, everything runs on DNS names (witch should work, and i can ping the server by its DNS name).
My second thought - Maybe it gets blocked! Checked my network firewall log, the log seemed pretty normal. After I checked the firewall on the client, and tried to create a custom rule allowing TCP port 3333 - still no dice..
I also did a "NETSTAT" command on the client, while trying to connect, the TCP connection stalled at "SYN_SENT" - for me, still seems like the TCP port is blocked somewhere..
So, now I am a bit lost, i hope someone can help me - thanks!
/Mick Negendahl