Problem with wingate 5.01

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

Moderator: Qbik Staff

Problem with wingate 5.01

Postby hannez » Aug 11 04 8:28 pm

I have two maschines connected to each other via cross-cable. Host is running on xp and client is on 98 se.

I don't know why but client can't find host. Only after I stop and start wingate, everything's OK.

Any ideas?
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

RE: CANNOT CONNECT TO HOST...

Postby mcit » Aug 12 04 12:18 am

Try disabling the built in wingate firewall

EXTENDED NETWORKING > DISABLE FIREWALL

If this fixes the problem then you simply need to either configure the firewall or simply disablw it and run an alternate firewall.
mcit
 
Posts: 32
Joined: Jun 24 04 2:53 pm
Location: Australia

Postby hannez » Aug 12 04 9:44 am

Where's that option? Can't find it.
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

EXTENDED NETWORKING...

Postby mcit » Aug 12 04 3:02 pm

The "Extended Networking or ENS" should be found in the main Wingate menu, [the same place the the DHCP Server and DNS Server services are located]

However I have seen previously that if you install wingate and do not select the "Intall ENS" option, then it does not create this service in the menu, however it appears to still install the service and enable the firewal [from my experience that is].

What I have done in the past to get around it is to reinstall wingate over the top of the existing installation but during the setup, ensure that the "Install ENS" option is selected. Once you have done this, the Extended Networking should be available and you should be able to diable the firewall.
mcit
 
Posts: 32
Joined: Jun 24 04 2:53 pm
Location: Australia

Postby hannez » Aug 13 04 4:05 am

I installed ENS and found the 'disable firewall option' but it didn't help.

Client still can't find Wingate server on network before I have restarted it.

Any other tips?
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

Postby erwin » Aug 13 04 9:13 am

Hi there

How do you mean your client cant find the WinGate Server(XP machine).

Are you running the WinGate Internet client(WGIC) on the client machine, and cant find the server in the applet.

Or are you using Network Address Translation(NAT).

In either case disabling the WinGate Firewall will make little difference as this (by default) will block incoming connections on the External Interfaces (i.e. the Internet connection or interfaces that have Public IP addresses assigned) that WinGate server uses, and shouldnt affect the LAN network card (as this should be configured with a private IP address)

Are you able to ping the machine or access the WinGate XP machine normally in a networked situation.?

Regards
Erwin
erwin
Qbik Staff
 
Posts: 408
Joined: Sep 03 03 2:54 pm

Postby hannez » Aug 13 04 11:14 am

My network seems to be working correctyl. I can ping both maschines and network works just fine.

(One thing disturbs me though. If I reboot, then my comp can't dial up broadband connection for about a minute. Any ideas? On first start everything's OK.)

Usual procedure is like this: start host and connect to internet, start client and try to connect to internet but wingate reports that it can't find any servers on network.And then I must stop and start wingate on host. After that, everything works like it's "oiled".
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

Postby hannez » Aug 16 04 9:20 pm

Maby I should try the lastest version of WinGate? Do I client and host have to have the same version?
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

Postby Pascal » Aug 17 04 11:49 am

What version of WinGate are you using ?
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 hannez » Aug 18 04 12:15 am

Look @ topic heading.
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm

Postby Pascal » Aug 18 04 12:42 am

Slow day in the office - apologies.

I suspect what is happening is, because you are using a cross over cable with only the two computers, up until the point where both machines are started the XP machine is not seeing itself as connected to a network. Because WinGate has already started - it has no IP to bind to for services. When the client starts up, the IP begins to exist, but WinGate remains unaware of it until you stop/start the Engine.

6.0 has introduced dynamic binding to get around this exact type of problem. It lets you specify a policy that tells the service what to bind to (Internal vs External, specific adapters, ips, etc.) so no matter how you change things underneath, WinGate will bind correctly. (Plugging cables in out, USB adapters in out, etc.)

So, an upgrade to 6.0 might very well help you. As always, if you are upgrading, make appropriate backups of your registry and make sure you have your license key handy - this version requires activation.
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 hannez » Aug 19 04 4:01 am

You were right.

First thing I tried was starting mashines in the opposite order. It worked. XP recognised other maschine and I didn't had to restart wingate.

Well this was only a test. I also tried upgrading and it helped also. Everythings fine with this v6

(I have 1 more problem but I'll make another topic for that.)

Thanx!
hannez
 
Posts: 9
Joined: Aug 11 04 8:22 pm


Return to WinGate

Who is online

Users browsing this forum: Bing [Bot] and 6 guests

cron