Wingate 5.2.2 troubles on Windows XP

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

Moderator: Qbik Staff

Wingate 5.2.2 troubles on Windows XP

Postby nicholasf » Jan 07 04 2:48 am

I try to use Wingate 5.2.2 on Windows XP and everythings seem to work fine. But when Wingate Engine is running and I am connected to Internet Clients Machines cannot see the Wingate Server: if i try to ping the Wingate Server I received this error: "TTL exceed".
If I am connected to Internet and the Wingate Engine is stopped the Ping command works fine.
If I am NOT connected to Internet and the Wingate Engine is running the Ping command works fine.
BUT if I am connected to Internet and the Wingate Engine is running the Ping command does NOT work fine and give me TTL Timeout Error.
Same problem with Wingate Version 5.1 and 5.2.0.
The problem is not present on Wingate Version 5.0.0 and 5.0.7
Is there anybody that know why this happends?
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby labull » Jan 07 04 3:56 am

Sounds like it could be a Firewall problem.

What is the IP range of your network?

Larry
WinGate Lurker
labull
WinGate Guru
 
Posts: 710
Joined: Sep 06 03 1:03 am
Location: Washington, DC - USA

Postby nicholasf » Jan 07 04 1:01 pm

I have only 1 client and 1 Wingate Server:
192.168.0.1 Client (OS => WIN98SE)
192.168.0.3 Wingate Server (OS => WINXP SP1)
I don't think it is a Firewall problem, because if i remove Wingate 5.2.2 and I install Wingate 5.0.7 (and I don't modify anything else) everything works fine without problems.
P.S.: Windows XP Firewall on Internet Connection is Disabled.
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby omg900 » Jan 08 04 12:13 am

I seem to have a similar problem (see my posting under Wingate Gateway Problem). When I install ver 5.22 my internal static IP number (192.168.58.112) is not visible anymore and none of my server applications including DSL dial-up to internet function any more. When I uninstall 5.22 and re-install ver 5.02 my internal IP is visible and all applications work fine. Maybe you have the same situation? You might want to check the internal IP of your server after you have installed ver 5.22 ... If you have the same trouble maybe support has an idea.

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby nicholasf » Jan 08 04 7:59 am

Yes, it is the same problem I have! It look like it is a very BIG bug of Wingate from Version 5.1 to 5.2.2.
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby genie » Jan 08 04 4:36 pm

Hi,

What network cards do you have on your Wingate machine? Also,what kind of internet connection do you use (dialup, DSL, cable, etc.).
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby omg900 » Jan 08 04 10:57 pm

genie wrote:Hi,

What network cards do you have on your Wingate machine? Also,what kind of internet connection do you use (dialup, DSL, cable, etc.).


Hi genie,

on my server I have a 2 network cards installed. One for the internal connections (Netgear FA311 PCI Network card) with a static IP (192.168.58.112) and one for external connections (Realtek RTL8139A PCI Network card) used for a PPPOE DSL dial-up connection to the internet.

Let's see what kind of adapter nicholas has ...

However it seems strange for me that all works fine under ver 5.02 and not at all under ver. 5.22

Appreciate your help.

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby nicholasf » Jan 09 04 7:00 am

My network cards are:
- Fast Ethernet PCI SIS 900 (integrated on ATI matherboard) for external connections with address 192.168.0.4 used with PPPOE DSL dial up connection
- Realtek RTL8029(AS) PCI for internal connections with address 192.168.0.3
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby omg900 » Mar 03 04 4:31 am

nicholasf wrote:My network cards are:
- Fast Ethernet PCI SIS 900 (integrated on ATI matherboard) for external connections with address 192.168.0.4 used with PPPOE DSL dial up connection
- Realtek RTL8029(AS) PCI for internal connections with address 192.168.0.3


Hi Nicholas,

has your problem been solved meanwhile? Or have you found a solution yourself? Would be great to share ...

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby nicholasf » Mar 03 04 6:41 am

the solution is not to use any more wingate:-(
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby Warren » Mar 03 04 8:06 am

Hi Nicolasf,

I have a system running 5.2.2 with Windows XP and Clients running Windows 98 and all works well.

Only difference seems to be the two cards you are running on the Server. I suspect that it has something to do with those two cards. Also check the firewall settings again.

Don't give up so easily. I'm sure there's a fix out there.

Regards, Warren
Warren
 
Posts: 60
Joined: Sep 14 03 5:52 pm
Location: New Zealand

Postby omg900 » Mar 03 04 12:15 pm

Warren wrote:Hi Nicolasf,

I have a system running 5.2.2 with Windows XP and Clients running Windows 98 and all works well.

Only difference seems to be the two cards you are running on the Server. I suspect that it has something to do with those two cards. Also check the firewall settings again.

Don't give up so easily. I'm sure there's a fix out there.

Regards, Warren


What a great help! There could be plenty of reasons why there is a problem. But I believe it is not an unusual configuration that a midsize company runs a fileserver (Server 2003) with 2 NIC's and a PPPOE DSL line, a firewall and a couple of WS's on WinXP pro. I honestly hate very much to see things working and then all over sudden things don't work any more when upgrading to a new OS and/or a new version of Wingate ....

It is not a matter of giving up so easily but a matter of not wasting too much time in a coporate environment! We have to do business and not dig for soliutions ...

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby Warren » Mar 03 04 1:10 pm

Hi Nicolasf,

No offense intended and yes we all have to earn a buck for our Boss. Fortunately I'm the boss here.

In my own case, I have yet to find a problem with Wingate; but I sure have had lots of problems, that I initially thought were WinGate and that turned out to be either my lack of understanding or some obsquire problem; like being IP Address Black Holed. You sound as if you know a great deal more than I do, so I hesitate to make any further suggestions. If anything, the People at Qbik should take note and try again to assist with your problem.

Nothing more. Good Luck

Regards, Warren
Warren
 
Posts: 60
Joined: Sep 14 03 5:52 pm
Location: New Zealand

Postby omg900 » Mar 03 04 9:15 pm

Warren wrote:Hi Nicolasf,

No offense intended and yes we all have to earn a buck for our Boss. Fortunately I'm the boss here.

In my own case, I have yet to find a problem with Wingate; but I sure have had lots of problems, that I initially thought were WinGate and that turned out to be either my lack of understanding or some obsquire problem; like being IP Address Black Holed. You sound as if you know a great deal more than I do, so I hesitate to make any further suggestions. If anything, the People at Qbik should take note and try again to assist with your problem.

Nothing more. Good Luck

Regards, Warren


Thanks Warren. Unfortunately I am the admin in our company and the problem with these bugs is that it could be anything from the OS, Wingate, to the Network drivers or a combination of these. And it is virtually impossible to predict what might go wrong once you update a system. Windows in many cases is still a nightmare although easier to handle than Linux. Anyway let's see what the Qbik people have to say.

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby nicholasf » Mar 04 04 2:45 am

To Warren:
I don't think that the problem is something to do with 2 nic cards, because same comfiguration, same OS, same nic cards and same computers works fine with version 5.0.7 of wingate. Why?
At the question "Why?" I reply with: "it is a bug of latest version of Wingate".
If you use a different connection, for example 56k modem everything works fine, and you say "Only difference seems to be the two cards you are running on the Server". Your ONLY word is very BIG!!!!
With Wingate Engine running also the ping command won't work.
With Wingate Engine Stopped the ping command works again.
This shows that wingate is faulty.
I really don't think there is something wrong in my nic cards configuration.
Bye!
nicholasf
 
Posts: 11
Joined: Jan 07 04 2:25 am

Postby omg900 » Mar 04 04 2:57 am

nicholasf wrote:To Warren:
I don't think that the problem is something to do with 2 nic cards, because same comfiguration, same OS, same nic cards and same computers works fine with version 5.0.7 of wingate. Why?
At the question "Why?" I reply with: "it is a bug of latest version of Wingate".
If you use a different connection, for example 56k modem everything works fine, and you say "Only difference seems to be the two cards you are running on the Server". Your ONLY word is very BIG!!!!
With Wingate Engine running also the ping command won't work.
With Wingate Engine Stopped the ping command works again.
This shows that wingate is faulty.
I really don't think there is something wrong in my nic cards configuration.
Bye!


Let's be fair, Windows as any other piece of software is quite complex and the fault may not necessarily be only on Wingate's side. It could also be a problem with the PPPOE protocol/driveror with a network driver or with Windows itself. If Winroute had a SOCKS proxy I would probably give it a try but it has not. So let's wait and see what the Qbik people have to say about a possible fix. Meanwhile you have said you'r not using Wingate any more. So what are you using instead?

Brgds
omg900
 
Posts: 42
Joined: Dec 19 03 11:13 am

Postby magickg » Jun 09 04 7:53 am

I have the some problem. It happen after couple hours. I have instaled WinXP and WinGate 5.2.3 with one file from version 5.2.2, because firewall doesn't work corectly. I'm using Realtek RTL8139 network card.
magickg
 
Posts: 4
Joined: Jun 09 04 7:18 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 11 guests

cron