IIS 5.0 on Wingate 5.2.2.

[Jan-Wouter Stigter]

Windows 2000 newly installed, network fine, TCP/IP fine, pings fine, IIS 5.0 installed working fine.

Installed Wingate 5.2.2 on server and clients, everything working fine... except IIS 5.0 works no longer.

I can ping: 127.0.0.1
I can ping: localhost
I can ping: 10.0.0.1 (a client)

I cannot ping 10.0.0.3 (= the server of IIS and Wingate)
I cannot ping jan (=name of server)

nslookup (no options) will give the ISP
nslookup 10.0.0.1 will result in 'cannot find server'.

Wingate firewall is off. NPF Firewall active (does not hinder IIS).
Wingate is port 808, IIS on 80.

What to do?

[Pascal]

Wingate firewall is off. NPF Firewall active (does not hinder IIS).

What happens if you disable NPF Firewall ? (Even temporarily)

[Jan-Wouter Stigter]

Thanks for your help.

It makes no difference, NPF does not hinder IIS.

[Pascal]

Thanks for your help. It makes no difference, NPF does not hinder IIS.

Not IIS, but what about WinGate ?

Alright, few other questions then:

1. Where are you pinging from ? Client / WinGate server ?
2. How does your clients connect ? Through WGIC, NAT, etc. ?
3. What is the DNS Server set to for the clients ? The WG Server ?

[Jan-Wouter Stigter]

I was pinging from the server (where both IIS and WinGate need to be working). Everything was set up 'automatically', with ENS enabled. So I think they connect through WGIC. The clients have 5.2.2 installed.

From clients I can ping succesfully on IP addresses, and with their own name - but not with other computer's names, just the addresses. Pinging 'wingate' fails on server and clients.

There is no DNS server set up on the server or on the clients. TCP/IP is set to 'Obtain DNS server automatically'. The clients also have 'Obtain IP address automaticaly ticked, the server has an IP address set to 10.0.0.3. (The ADSL modem is 10.0.0.138).

NPF doesn't hinder Wingate, either, it keeps working happily.

Hope this helps. Thanks for your efforts!

[erwin]

Hi there

Sorry a few more questions:

Is the ADSL router using DHCP and is giving IP's to clients?
Does the server have one or two network(cards) interfaces?

Generally from what I can see the configuration for WinGate to work behind a ADSL router like you have described is as the following:

1. WinGate Server has two NIC's, one to the ADSL modem and one to the clients (rest of the LAN)

2. The WinGate server 's NIC that is address 10.0.0.3 should be connected to the ADSL modem, and the NIC's Gateway and DNS setting set to the IP of the ADSL router (10.0.0.138).

As I asked earlier, the NIC may be assigned these details earlier by DHCP on the ADSL modem if the modem is using it, or you may have to configure these settings manually.

The other NIC (connected to the rest of the LAN ) should be configured with another private IP address range such as 192.168.1.X. The clients on the LAN can then receive DHCP addresses from the WinGate if this IP address scope is configured in the WinGate DHCP service. and it will assign the correct DNS for clients (Which should be the 192.168.1.X address on the WinGate server.) Or these details can be assigned manually of course.

This way requests from clients will be sent to WinGate and forwarded to the ADSL modem for Internet access.

With IIS running on the WinGate machine you will need to assign the www proxy service in WinGate an alternative port if IIS webserver is using port 80 already, to avoid conflicts. Of course you will have to tell client apps accessing WWW on the Internet to use the alternative port.

Hope this helps

Regards
Erwin

[Jan-Wouter Stigter]

Hi there,

at the moment, there is only 1 NIC. I can see that this could possibly be the problem, although IIS and WinGate used to work together before (but separately, on other machines who are now clients but who also had only 1 NIC each; in any case this doens't work anymore with 5.2.2).

I'll try your solution, bit daunting on the config side but I'll ask your help in case I get stuck.

Thanks a lot!

Jan-Wouter