SQL Enterprise Manager

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

Moderator: Qbik Staff

SQL Enterprise Manager

Postby pexsol » Oct 13 05 7:39 pm

Hi,

I have a server within Wingate 6.0 installed using ip 192.168.0.1. I have several client PC with IPs 192.168.0.x connecting to the internet using the wingate server. Everything is fine when it comes to web browsing, ftp, msn etc.

However, when trying to connect to an SQL server remotely using enterprise manager we can't. Note that the Wingate Server is able to connect directly, but with the client PCS connecting through the wingate get an error. So its likely that we are missing some configuration on the wingate server. FYI, SQL uses port 1433.

I'd appreciate a step by step guide on making this work.

Thanks in advance. Kamran[/b]
pexsol
 
Posts: 3
Joined: Oct 13 05 7:32 pm

Postby adrien » Oct 14 05 9:38 am

Hi

in the past we have had success using simple NAT to get access to SQL server.

How do the client machines connect to the Internet? Through proxies (i.e. clients configured to connect to the proxy), or through NAT (i.e. clients configured with their TCP/IP default gateway set to the IP of the WinGate machine, but client software e.g. browsers configured to connect as if they were directly connected to the Internet)?

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Postby pexsol » Oct 14 05 6:52 pm

Adrien,

Thanks for your message.

Here is my network scenerio:

1. All client machines have fixed IP addresses and have Wingate Machine as the gateway in TCP/IP

2. The client computers use proxy (Wingate machine:80) to connect to the internet using software like web browsers, msn etc.

Regards,
Kamran
pexsol
 
Posts: 3
Joined: Oct 13 05 7:32 pm

Postby jamesc » Oct 14 05 7:32 pm

1. All client machines have fixed IP addresses and have Wingate Machine as the gateway in TCP/IP


1. And do they have a setting for their DNS as well?
2. Can you confirm NAT is working

You can easily test if NAT and DNS are working by doing the following.

First of all
(Windows) Start menu --> Run --> cmd --> ping 66.102.7.147
If that works (you get replies back), then NAT is configured
Secondly
(Windows) Start menu --> Run --> cmd --> ping www.google.com
If that works as well, NAT and DNS are configured.
jamesc
Qbik Staff
 
Posts: 928
Joined: Apr 04 05 2:04 pm
Location: Auckland, New Zealand

Postby pexsol » Oct 15 05 12:30 am

(Windows) Start menu --> Run --> cmd --> ping 66.102.7.147
If that works (you get replies back), then NAT is configured
Secondly
(Windows) Start menu --> Run --> cmd --> ping www.google.com
If that works as well, NAT and DNS are configured.


- Yes it works....
pexsol
 
Posts: 3
Joined: Oct 13 05 7:32 pm

Postby adrien » Oct 15 05 9:11 am

OK, do you see any entries in GateKeepers's firewall tab when you try to run enterprise manager?

Something may be trying to connect back.

Normally we have found it just works with a TCP connection.

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate

Who is online

Users browsing this forum: Google [Bot] and 5 guests

cron