5.2.3 and 6.0.1

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

Moderator: Qbik Staff

5.2.3 and 6.0.1

Postby spire » Aug 16 04 2:17 am

Hi,
I am a new user of Wingate and Wingate VPN.
I have a small local network at first office and machine at home.
- Wingate Server: Pentium 200, 160Mb, Windows 98; 192.168.0.1 - internal adapter, 192.168.95.26 - external adapter connected to Internet trough Microsoft VPN-adapter
- Wingate Client: Duron 1200, 256Mb, Windows 98; 192.168.0.2
We need minimum functionality from Wingate (Internet Sharing, E-mail, VPN).

I find out the following problems:

1. Internet Sharing and E-mail in ver. 5.2.3 works OK, but traffic during file copying trough VPN is 2-3 times bigger than size of file. At opening files on a network the traffic exceeds the size of a file in 20-40 times. It is a problem whether or not?

2. After default installing ver. 6.0.1, Wingate don't works correctly. The network ceases to answer. I can not to ping server from client-machine. After wingate 6.0 installing I cannot see a server from a network. The disabling of firewall does not help. Bindings are installed correctly.

When firewall works I can see during pinging from client-machine in firewall window:
"...Reason - Port Range; Source IP - 192.168.0.2; Port - N/A...".
By the client machine I receive the answer: "Time out".

It is remarkable, that after default installation of ver.5.2.3 the network works normally.
I install both versions with identical parameters (without Mail-server and without Auto-update), but under 5.2.3 is all right and under 6.0.1 there are problems.

Somebody help me!
spire
 
Posts: 5
Joined: Aug 14 04 9:36 am

Postby adrien » Aug 16 04 11:59 am

1. That is normal, thank MS for creating really inefficient network protocols! Also TCP/IP has a certain amount of overhead as well (normally about 6%). However one thing to check would be ping times end to end - if there is a large delay, then packets are re-transmitted due to timeouts.

2. Make sure that your internal adapter is deemed to be internal by WinGate. Look in GateKeeper in the Network Tab, under Network Connections. In the usage column, if your internal adapter is showing as external, it will firewall itself from your LAN.

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

Postby spire » Aug 16 04 8:42 pm

Hi Adrien!

My internal adapter is deemed to be internal by WinGate.
In GateKeeper in the Network Tab it looks so:
"Name - Realtek 8139 Series PCI NIC | Type - LAN or High Speed Internet | Status - Unknown | Usage - Internal | Device Name - Realtek 8139 Series PCI NIC | Speed - 100 Mbps | IP adress - 192.168.0.1 | Gateway - None"
I cannot work with a network even when I disable firewall in "Extended Networking". In this case during pinging I see in Activity Tab:
"NAT: ICMP 192.168.0.2", but no networking.
Why?

Best regards,
spire
spire
 
Posts: 5
Joined: Aug 14 04 9:36 am

Postby adrien » Aug 17 04 2:48 am

do you only have one network adapter in that machine?

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

Postby spire » Aug 17 04 6:57 am

I have two LAN adapters.
After I have pulled out them from a computer, and then have inserted back and reinstalled - the problem has disappeared. I managed to avoid Windows reinstallation.
But Wingate v.5.2.3 worked without reinstallation.
However, thanks for help.
Best regards,
spire
spire
 
Posts: 5
Joined: Aug 14 04 9:36 am

Postby adrien » Aug 17 04 7:00 am

You're welcome.

WinGate 6, since it dynamically reacts to changes in your network configuration etc is more reliant on knowing about your adapters, so this is why it might have trouble where WinGate 5.x didn't in this regard - WinGate 5 was basically just ignoring the situation.

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 3 guests