wingate doesn't propely works.

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

Moderator: Qbik Staff

wingate doesn't propely works.

Postby LastAkademik » Jan 19 04 11:24 pm

I have windos XP prof. I made the server of remote acess to internet by modem. After Client connects, I need to restart WinGate Engine. Without it Client can't connect to internet. But Proxy works propely with other Clients, who are connetcting with network adapters. Can anybody help me?

Version of wingate is 5.2.2 (build 892)
LastAkademik
 
Posts: 3
Joined: Jan 19 04 11:11 pm

Postby neil » Jan 20 04 1:13 pm

Just to clarify. When you open a web browser (say IE) on a client machine behind WinGate, the connection appears in GateKeeper's Activity panel. But then nothing happens, and you have to restart the WinGate engine?! How is WinGate connecting to the internet? dail up modem or DSL modem? How are the clients on your network connecting to your WinGate machine? NAT, WGIC, proxy etc. Sounds like some sort of binding issue, where WinGate isn't seeing an interface because it's (WinGate) is starting before it.

Regards

Neil
neil
Qbik Staff
 
Posts: 356
Joined: Sep 03 03 2:42 pm
Location: Auckland

Postby LastAkademik » Jan 22 04 10:00 am

1) When Client open's IE nothing happens. Wingate doesn't show any appearing of the connection.
2) Wingate is connecting to the internet by DSL.
3) Client connects to wingate by modem. He use IE. Only proxy settings enabled in dail up options.

About binding issue. (How I may solve this problem?)
I think you are right. But the modem (Client is connectig by modem) begins to listen the line from start up.
LastAkademik
 
Posts: 3
Joined: Jan 19 04 11:11 pm

Postby adrien » Jan 22 04 3:47 pm

WinGate enumerates available interfaces when it starts, and these are the only interfaces you can bind a service to.

Since before a dialin client connects to your RAS server the interface is not present in your system IP properties, WinGate does not see it.

The way to solve this is to bind the services that the client needs to use to "accept connections on any interface". Then when the client dials in, they will be able to connect to that proxy.

The client should also be able to use NAT rather than proxy.

If this server machine is also directly connected to the Internet, you can protect the proxies that are bound to "any interface" by using the port security settings in the ENS firewall.

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

Postby LastAkademik » Jan 23 04 2:36 am

Thanks greate. Now all is working.

Problem was in binding sevices.
LastAkademik
 
Posts: 3
Joined: Jan 19 04 11:11 pm


Return to WinGate

Who is online

Users browsing this forum: No registered users and 1 guest

cron