Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Oct 23 04 12:45 pm
I just switched over to the new DSL service from the old cable modem service.
We use wingate on a gateway pc. Right now the gateway pc accesses the internet fine. However, the rest of the hosts can't.
IE browser get the error HTTP: 500 internal server error.
On the Wingate window it says the error : New Interface detected.
The gateway has 2 interfaces, Wan and Lan. I put in the new ip address info that provided by the new isp on the wan interface. on the lan interface I did not do anything accept that the gateway is the ip of the wan interface.
Is there anything else extra I have to do on wingate? Do I have to to reconfigure the routing table? I don't think so, because wingate autodetected everything.
On the hosts I could ping all the interface of the gateway. I could do tracert on all the interfaces. But as soon as I get out, it lost.
I need some help.
Andy
Oct 23 04 12:55 pm
xeo196 wrote:
The gateway has 2 interfaces, Wan and Lan. I put in the new ip address info that provided by the new isp on the wan interface. on the lan interface I did not do anything accept that the gateway is the ip of the wan interface.
You don't want to do this. Leave the gateway setting for your internal adapter blank. You only need a default gateway on your external adapter, and this will likely be provided by your ISP.
Adrien
Oct 25 04 4:10 pm
Adrien, if I leave the GW blank in the internal interface, will my hosts able to get out? With the old isp I put the ip for the gw on the internal interface and all my hosts got out. What else I have to do?
Thanks so much.
Andy
Oct 26 04 10:13 am
xeo196 wrote:Adrien, if I leave the GW blank in the internal interface, will my hosts able to get out?
You are definately more likely to get out. Which version of WinGate are you using?
Oct 27 04 4:03 am
Thanks Pascal, my company Wingate version is: 5.2.0 (Build 885)
It was intended to be a simple process to switch over to the new service. But We could not get out.
Is there any additional steps have do in the Wingate gateway itself?
Please help, Thanks
Andy
Oct 27 04 9:40 am
It depends on how your clients connect out through WinGate.
The first thing I'd do would be to check that the adapters has been setup properly. (In WinGate) Go to "Options -> Advanced" and check that the adapters are marked properly. ("Public|Untrusted vs Private|Trusted")
Secondly, go into your services and make sure that things are bound correctly. Your services should normally be bound to your internal IP (Local network).
So, how do your clients connect out? Are you using NAT, WGIC or Proxy?
Oct 30 04 4:24 am
All my hosts connect to the wingate PC as proxy and the wingate pc will perform any nat function.
I am sorry for could not get back sooner. I try to do that couple times but no result.
Is there anything have to do with the router? Out of the box the router should work, right? I call our isp and they said that things look normal.
What else I have to do.
Andy
Nov 01 04 9:55 am
So, you have a proxy setup configured in your browsers? (In IE, you have set the clients to use WinGate's internal IP as their proxy server?) (Proxy)
OR
Have you set them to use the WinGate machines internal IP address as their default gateway in TCP/IP properties and not configured anything in your browser (NAT)
Can you go to a command prompt and type "route print". Use your mouse to select the result (You might have to dropdown the menu to get the "mark" option) and paste the results of that here, please.
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.