Wingate - disabling and re-enabling NIC for Wingate to work

[kentb]

Hi,
I have installed Wingate 6.22 on a PC (win 2000)

- I have 2 NICs installed
- One for our Internal network (90.0.0.*)
- One connected to the Internet (Bell Aliant)

Everytime we restart the proxy server
with Wingate, Internet does not work
at all on the workstation, either
going through the proxy server or connecting to the Internet.
I must manually disable NIC that connects to our internal network and re-enable it again.
That usually does the trick

I know that the Internet works, because if I leave the NIC card that is connected to our internal network (90.0.0.*) *disabled* and restart the PC, then the Internet works correctly. Then I enabled the NIC card for our internal network and Wingate works.

It's as if the Wingate or Windows 2000 gets confused. It's like disabling the NIC and enable it again updates the routing table ???
I don't know.

Would you have a solution for this ?

This also happen at another site too

[adrien]

Hi

I'm wondering if there's a port conflict with some other software on that host, e.g. IIS.

When you say internet doesn't work, does absolutely nothing work, or did you just try web browsing? What error do you get when you're trying to access the net?

Do you log into GateKeeper and see any reported errors, or do any services show as in error?

Regards

Adrien

[kentb]

Hi

I'm wondering if there's a port conflict with some other software on that host, e.g. IIS.

When you say internet doesn't work, does absolutely nothing work, or did you just try web browsing? What error do you get when you're trying to access the net?

Do you log into GateKeeper and see any reported errors, or do any services show as in error?

Regards

Adrien

Just web browsing...cannot resolve the DNS name or it times out
I do not see any errors in Gatekeeper.

[kentb]

Hi,
I have installed Wingate 6.22 on a PC (win 2000)

- I have 2 NICs installed
- One for our Internal network (90.0.0.*)
- One connected to the Internet (Bell Aliant)

Everytime we restart the proxy server
with Wingate, Internet does not work
at all on the workstation, either
going through the proxy server or connecting to the Internet.
I must manually disable NIC that connects to our internal network and re-enable it again.
That usually does the trick

I know that the Internet works, because if I leave the NIC card that is connected to our internal network (90.0.0.*) *disabled* and restart the PC, then the Internet works correctly. Then I enabled the NIC card for our internal network and Wingate works.

It's as if the Wingate or Windows 2000 gets confused. It's like disabling the NIC and enable it again updates the routing table ???
I don't know.

Would you have a solution for this ?

This also happen at another site too

Forgot to mention the following:
- On the Internet, it's an ADSL connection with a router, so the modem IP is set to 192.168.2.1
Username and password is stored in the router

The range of IP 90.0.0.1 on our Internal LAN is for the public.
(This is a government agendy with a few stations that can go on the Internet for Hotmail and stuff)

This setup used to work correctly with Winproxy...

[adrien]

Hi

The interesting thing is that your internal network is using public IP addresses, and your external one is using private addresses, so by default WinGate will consider their roles to be reversed.

Can you check in the adapter properties in the network window in GateKeeper that the "usage" of each adapter is correct? To change it just double-click the adapter and select the appropriate option.

Regards

Adrien

[kentb]

Hi

The interesting thing is that your internal network is using public IP addresses, and your external one is using private addresses, so by default WinGate will consider their roles to be reversed.

Can you check in the adapter properties in the network window in GateKeeper that the "usage" of each adapter is correct? To change it just double-click the adapter and select the appropriate option.

Regards

Adrien

The 90.0.0.* is set to Internal (Trusted) network
and the 192.168.2.1 one is set to the Internet (untrusted)

The 192.168.2.1 is a router that uses NAT so it's normal that it would have a private IP

What would explain that after disabling and enabling the NIC card for the Internal network that it would work after that ?

Thanks for your help

[logan]

What would explain that after disabling and enabling the NIC card for the Internal network that it would work after that ?

Without having seen this for myself, my only guess is that stopping and starting the NIC also caused the bindings to reevaluate and rebind when the NIC came back up.