WIngate 6.0.4 and Port opening problem

Jul 19 05 11:33 am

I was using the 5.0 version of wingate. Updated to 6.0.4, but did not buy a new license as the old one registered fine, and I don't need all the bells and whistles. On the old version, there were a range of ports open in extended networking so our tax software can communicate and transmit e tax returns, etc. Everything worked ok in the older version ( 5.0.?)

When I went with version 6.0.4, I can no longer communicate over those ports and do our e-filing of tax returns. I can see nothing,wrong, in fact when I try to transmit and I view the messages in the firewall tab, I can see it is allowing communication through port 10100. HOwever the software does not communicate. I have deleted the open ports and re opened them in an attempt to see if there was something not working correctly.

I have spent several hours on the phone with our tax software company ( Lacerte) and they can not figure out what else needs to happen to make this work.

The tax software vendore believes it may have something to do with the proxy server ( WIngate) and that I may need to allow certain IP's to byppass the proxy server. THey have given me ip's however, I get back to the fact all worked fine until I upgraded wingate. Any thoughts?

Thanks

Dave

Jul 19 05 12:48 pm

So there were no firewall hits when you tried communicating with the server, right? Is it only one particular sit that gives you these troubles or every outbound connection fails?

Jul 19 05 1:04 pm

This is the only site we are having this problem with. I had open ports 10000 - 10100 which is what they require. WOrked ok in 5.0.?, but not in the current version (6.0.4). As far as Hits is firewall. I could see it was allowing out on the port 10030 or whichecver one was trying. It is almost as if it is not receiveing a response?

Dave

Jul 19 05 1:13 pm

Can you export and send me Wingate registry branch?

Jul 19 05 1:39 pm

YEs Gina I will send it right over
Thanks
Dave

Jul 19 05 1:43 pm

Thanks - got it - I will run the tests right away.

Jul 19 05 2:16 pm

Hi,

Just checked it - it worked fine on the test machine. Now, first thing to check would be to make sure that your adapters are marked correctly (internal/external).

Jul 19 05 3:18 pm

Both of the cards are marked correctly, like I had mentioned, everything has been working just fine until I upgraded to the new version. Any thoughts?

Jul 19 05 3:23 pm

Can you try connecting from the Wingate machine itself?
Also, how is you client connected - does it use straight NAT?

Jul 19 05 3:26 pm

I set up and tried to connect by the wingate program itself and it did not work there either. I don't believe we use the NAT feature.

Dave

Jul 19 05 4:13 pm

So, if you are not using NAT then it should be something lese, like proxy or WGIC client - when you open the connection from the client what kind of traffic do you see in Gatekeeper activity panel?

Jul 19 05 7:29 pm

One thing to note.

WinGate 5 adapter settings were quite different to 6.0, so you may still need to check the adapter settings - you can't assume that since WinGate 5.0 had them pegged that WinGate 6.0 will treat them the same way sorry.

Cheers

Adrien