Connection to remote server

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Connection to remote server

Postby tayyab38 » Sep 10 07 8:55 pm

We have 2 locations:

1) Branch Office

Having Wingate server with 2 NICs, one NIC card is attached to the ISP router and the other to LAN.

2) Head Office

Head Office users connect to internet via Planet Internet Gateway, Wingate is not available there, on that particulare internet gateway, we have configured port forwarding for few of our services like 25,110 TCP to our e-mail server and 23 to our Unix server etc.

Now problem is that, when users come from the internet to the head-office except the above mentioned branch office they get access into our servies, but users present at the above branch office comming thru wingate are not able to get into services available at head office like they can't get their outlook working or they can't connect to our unix box etc.

I think we need to configure wingate for this connection, but I'm not sure what configurations at client and server end are required.

Please ask me if any clarification is required.

Regards,
Tayyab
tayyab38
 
Posts: 2
Joined: Sep 10 07 8:45 pm

Postby jamesc » Sep 11 07 3:24 pm

Have you tried using NAT?
The changes between version 6.x releases can be reviewed here:
http://www.wingate.com/showfaq.php?faqid=2

Skype: wingatejames
jamesc
Qbik Staff
 
Posts: 928
Joined: Apr 04 05 2:04 pm
Location: Auckland, New Zealand

Postby tayyab38 » Sep 11 07 6:26 pm

Can you please let me know how to enable NAT for one particular user?
tayyab38
 
Posts: 2
Joined: Sep 10 07 8:45 pm

Postby jamesc » Sep 11 07 6:39 pm

Sure.

NAT is when the LAN Client has a default gateway set to the Internal ip address of the WinGate server. The LAN client will also need to be able to resolve internet domain names (DNS). A quick way to test for NAT on a LAN Client could be as follows:

(Windows) Start menu --> Run --> cmd --> ping 210.55.214.36
(Windows) Start menu --> Run --> cmd --> ping 72.14.253.104
(Windows) Start menu --> Run --> cmd --> ping www.wingate.com
(Windows) Start menu --> Run --> cmd --> ping www.google.com

More information on NAT can be found here:
http://support.qbik.com/index.php?_a=kn ... ils&_i=147


Now when you say you only want to allow one user for this then please do the following for the sake of testing - then remove when your test is complete.

Scenario: User who will test this is on a LAN Client with an ip address of 192.168.0.2

GateKeeper --> Extended Networking Services --> Policies --> Add

Everyone, User may be unknown,
Advanced tab:
Add Filer, Add Criterion
This criterion is met if client ip address equals 192.168.0.2
Ok back to the the GateKeeper and test.

*I also presume the Guest account is enabled in WinGate.
The changes between version 6.x releases can be reviewed here:
http://www.wingate.com/showfaq.php?faqid=2

Skype: wingatejames
jamesc
Qbik Staff
 
Posts: 928
Joined: Apr 04 05 2:04 pm
Location: Auckland, New Zealand


Return to WinGate

Who is online

Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 7 guests

cron