another newbie ?? - dhcp problem

[jackfrost1329]

I'm yet another Winproxy user evaluating Wingate, at least I'm attempting to.

I don't seem to be able to get the Wingate DHCP service to assign IP addresses to clients. I've checked everything about my network and tcp/ip setup and all seems fine. I can ping and see shared directories on the Wingate machine from the client when I assign static IPs from the range I want to use. I can also get IP addresses assigned from the DHCP service on a router when I enable it no problem (and can ping, etc.). But I can't get the Wingate DHCP service to do the same.

Both machines I am using to evaulate are running Win XP Pro SP2, the server is a Dell Optiplex 270 and the client is a Dell Dimension 4700 and both have Intel NIC (albiet different models) for the LAN. The server is the standard 2 NIC setup (with the 2nd NIC for the cable modem being Realtek). Wingate correctly identifies the internal and external connection.

Anyone got any ideas what the problem may be?


Thanks, Jack

[Nev]

Hi Jack,

On the clients have you configured the IP of Wingate's Internal NIC as a gateway?

Drop back to the forum to let us know how you get on!

[jackfrost1329]

Hi Nev

Thanks for the reply. The guys from Qbik support helped me resolve the problem. Fairly quick reply for New Zealanders too (just kidding guys).

Anyway, the Windows firewall on the Wingate machine was blocking requests to port 67. I didn't think of that one, maybe because I run Winproxy on a Win 2000 machine and that doesn't come up in that scenario. My problem now is convincing the Windows firewall to open port 67 without having to disable the the firewall completely (which is the only way it works at the moment). I know Wingate will replace the Windows firewall, but that doesn't git rid of the annoying Windows messages telling me i'm not protected.

So theres a suggestion for the next version of Wingate - get it to replace the Windows firewall like Zone Alarm does.

Thanks again - I'll no doubt be back with more questions.


Regards, Jack

[jackfrost1329]

Just a quick update. I worked out the opening port 67 in Windows firewall. I was trying to restrict it to just the local subnet, but apparently it prefers that you open to all.

Thanks, Jack

[Nev]

Hi Nev

I didn't think of that one, maybe because I run Winproxy on a Win 2000 machine and that doesn't come up in that scenario. My problem now is convincing the Windows firewall to open port 67 without having to disable the the firewall completely (which is the only way it works at the moment). I know Wingate will replace the Windows firewall, but that doesn't git rid of the annoying Windows messages telling me i'm not protected.


Regards, Jack

Hi Jack,

Wingate has a SI firewall inbuilt if NAT is enabled, from the testing I have done it is superior to the Windows one. Personally I set it to high in all the networks I have installed and there hasn't been any difficulties with all sorts of traffic.

The 'Windows message' you mention, is that the Security Centre, Red Shield in the System Tray? If it is you can disable that service. Although, I haven't seen it on a Win2k system myself, only since XP.

Cheers,

[Nev]

Just a quick update. I worked out the opening port 67 in Windows firewall. I was trying to restrict it to just the local subnet, but apparently it prefers that you open to all.

Thanks, Jack

Doesn't it allow you to choose interfaces?

The few I have worked with could disable it for say just the internal NIC and keep it on for the other NIC.

[jackfrost1329]

Doesn't it allow you to choose interfaces?

The few I have worked with could disable it for say just the internal NIC and keep it on for the other NIC.

Hi Nev

Yes, it allows that in the advanced settings but it appears to be for specific services like POP3, SMTP, HTTP, etc, and DHCP isn't mentioned. I was doing it in the "Exceptions" tab.

Anyways, its all irrelevant now (well not entirely, I learnt something) 'cos in further trials I've discovered that the Windows Firewall on the Wingate server interferes with any discussion a client may wish to have with the server. So rather than try to think of all the exceptions required, I just turned it off (just as Logan from Qbik said in a follow up email but I didn't get that 'til I'd found out for myself). And as you say, you can get rid of the Red Shield. Its also good to know that you have tested it and found it superior.

I must say I am finding it harder to setup Wingate than I did Winproxy, then again that could just be that I've forgotten a lot a things I learnt in that experience some 9 years ago. On the other hand, it does appear to have gained a lot of the features that made me choose Winproxy all those years ago, so thats pleasing. And I have noticed that some errors I have been getting through Winproxy have disappeared which is very pleasing. It also seems faster, but I haven't really put that to the test yet.

Once again, thanks for your input. Its impressive to actually get a response to a problem - I could get used to that.


Regards, Jack

[logan]

You can actually disable that warning message you get when the firewall is disabled. If you would like to use WinGate's firewall and disable the Windows one.

First disable the Windows Firewall permanently:
- Start > Run > services.msc
- Double-click on `Windows Firewall/Internet Connection Sharing`
- Change the `Startup type` to Disabled
- Click `Stop`

A message will popup from your system tray stating that your computer might be at risk. Click on the message or double click on the red shield tray icon it came from.

Expand out the Firewall section and click Recommendations. Place a check in the "I have a firewall solution that I'll monitor myself" box. This will stop Windows from popping up alerts that you are at risk.

[winproxy_guru]

Well your not the only one who's having issue with converting to wingate but ive found that i called winproxy support and they are helping people convert to wingate since bluecoat is basically abandoning its users. So i've delt with them in the past and there support is good. I'm glad to see that they are jumping ship too