Can not configure clients under Wingate 6.04 without DLINK

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

Moderator: Qbik Staff

Can not configure clients under Wingate 6.04 without DLINK

Postby redexperto » May 04 05 8:47 pm

Hello,
I could not get Wingate and the DLink router to work so I am attempting to eliminate the Dlink router and just use Wingate+switch
I have the same problem I can not get the client to access the internet.
When I ping from 192.168.4.2 to 192.168.4.1 I get a time out.
Wingate does have access to the internet, but not the client.

Se settings below.

Any ideas?
Thanks

Ethernet adapter Local Area Connection 3: External

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : provided by ISP*
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : same as IP above

Ethernet adapter Local Area Connection 5: Internal

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.4.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : same as above see *

Client section
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SIS 900 Based PCI adapter

Physical Address. . . . . . . . . : MAC ADDRESS GOES HERE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.4.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.4.1
DHCP Server . . . . . . . . . . . : 192.168.4.1
DNS Servers . . . . . . . . . . . : 192.168.4.1
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby genie » May 04 05 8:54 pm

You have to remove default gateway from the internally-deemed adapter - having the second default gateway confuses routing process.
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby redexperto » May 04 05 9:21 pm

I removed the default gateway from
Ethernet adapter Local Area Connection 5: Internal
Now it looks like this
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.4.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Client still can not connect.
Helpppppp

Bye the way Pinging 192.168.4.1 fails from the client (192.168.4.2 )
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby genie » May 04 05 10:26 pm

What network cards do you have there? The internal part is connected through SIS 900, how about the external side?
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby redexperto » May 05 05 4:06 am

The internal card is a 3Com Officeconnect 3Csoho100-tx connects to my switch
The realtekTTL8139A II Sis 900 is the external connects to the cable modem.

I notice that on the Firewall window of Gatekeeper

The external card has a subnet of 255.255.248.0 provided my ISP
the internal card has a subnet of 255.255.255.0 do they have to be the same ?

I was able to get a successful PING to 192.168.4.1 and .2
What happened is that 192.168.4.2 client was blackholed so I deleted it
from the list.

But, still no access.
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby genie » May 05 05 11:19 am

Hi,

Now, network masks are not necessarily the same - they reflect IP addresses distribution and can very from one network to another. Meanwhile, do you have internet access from the Wingate machine iteslef?
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby adrien » May 05 05 12:18 pm

Are either of these machines running XP service pack 2?

If so, disable XP's firewall...

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

Postby redexperto » May 05 05 3:39 pm

genie wrote:Hi,

Now, network masks are not necessarily the same - they reflect IP addresses distribution and can very from one network to another. Meanwhile, do you have internet access from the Wingate machine iteslef?


The wingate server has access to the web, the client does not.
When I Ping 192.168.4.1 and .2 I get a successful reply.
I am using Windows 2000 Pro and my personal firewalls are disabled

I also noticed that Wingate was flaging 192.168.4.2 and put it in as black holed.


Is there anywhere where I can get step by step instructions on how to
configure this. I have the trial version for 30 days, but I would like to
have it running properly before I buy.

Thanks
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby Pascal » May 05 05 3:45 pm

Out of curiosity - how is the client configured? Does it have:

* a default gateway / DNS server pointing to the WinGate server?
* using direct proxy connection ?
* have WinGate Internet Client installed?
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby MattP » May 05 05 4:23 pm

Hi,

We are more than happy to extend your trial license if it is going to expire before you are happy with how WinGate is working for you, just send in your trial id number to us.

Did you remove the IP from the blackhole list? Are you seeing any hits on the WinGate firewall when you try to ping the server?

Could you post your route table from the client?
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Postby redexperto » May 05 05 5:10 pm

MattP wrote:Hi,

We are more than happy to extend your trial license if it is going to expire before you are happy with how WinGate is working for you, just send in your trial id number to us.

Did you remove the IP from the blackhole list? Are you seeing any hits on the WinGate firewall when you try to ping the server?

Could you post your route table from the client?


Thank you for the offer of extending it. I Still have about 27 days
I have been fighting with this for 3 days now.
I did remove it and that is why I was able to Ping successfuly.
I also notice that my ISP was being put in the blackhole, I removed it
also.
Right now am I work I can not access the computer, but I will check if I see any hits.

I remember, I saw the client computer 192.168.4.2 under the firewall
section and it had a red circle with an X, it looks like the firewall is blocking it, but I can not remember if it was before or after I took out
the client from the blackhole.

I will check later and let you know.
Thanks
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby genie » May 05 05 5:49 pm

I think you have your interfaces mismatched - I mean, internal/external settings are probably incorrect - can you, please, double-check that Gatekeeper reports them as internal/external properly?
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby redexperto » May 05 05 7:59 pm

Pascal wrote:Out of curiosity - how is the client configured? Does it have:

* a default gateway / DNS server pointing to the WinGate server?
* using direct proxy connection ?
* have WinGate Internet Client installed?


The client has a default gateway and that is the IP 192.168.4.1
this is the internal card 3Com.

I do not know where "direct proxy connection " is
I have not installed Wingate Cient is that a separate software? If it is not
a separate software how do I do that?
redexperto
 
Posts: 11
Joined: May 04 05 4:00 am

Postby Pascal » May 05 05 8:12 pm

And DNS Server for the client machine? Can it resolve DNS? Have you ensured the adapters are correct like Genie suggested?
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand


Return to WinGate

Who is online

Users browsing this forum: No registered users and 65 guests