Windows 200 Server and Wingate

[darizonah]

I may have set up the server wrong but here goes.

I have a NEW server running windows 2000 server. Active directory was set up on this machine. We use an ISP through a router and do not have a separate machine for DNS purposes. WIngate is loaded on this machine.
THis machine has 2 NIC cards one to the router to the internet and one to the Network HUB.

I have read the articles about active directory and can't seem to progress.

Keep in mind that I have been running wingate successfully for 2 years with a NT 4 Server running Wingate. ( with the 2 NIC cards)

I can not get anyone through on the internet. ( Running 10 machines on the LAN. THe client machines all have static IP's.

THe server is the one with WIngate and Active Directory on it. Is there an easy way to get this to work properly? Or did I make a mistake by loading active directory on this machine?

We have Domain but it is hosted by an ISP. THe Client machines log on to the server in the domain I set up on the server, that is why I told this machine to have active directory.

I am really confused and anyone who could help?? Sure would appreciate it!

[genie]

What does Wingate report? Does it refuse Internet access to the clients based on failed authorization?

[darizonah]

I have not seen wingate reporting anything. CLient machine is not given a chance to authenticate. I will double check this today at work. It seems more like it is a DNS issue where it can't find the server on the internet.

[darizonah]

The client machines are asked to authenticate ( which is what I want) They can log onto wingate through the java applet. However email does not work and the page is not available in internet explorer.

On the server I also can't get on the internet.

I am sure this has something to do with DNS and Active Directory, however I still can't figure it out even after reading the article configuring wingate in the active directory.

Any thoughts?

[adrien]

Hi

Which DNS server are you using? I am guessing, that if you are running an AD server on the same machine, then it will be running the MS DNS server. You would therefore need to disable WinGate's DNS server to avoid conflicts.

This then raises the issue of how do your network clients resolve DNS. This would require that the MS DNS server be configured with a forwarder address, so that any requests that it doesn't have the answer for (i.e. any normal internet name lookups) are forwarded to a DNS server on the Internet.

WinGate will use whichever DNS servers are assigned to a network adapter on that machine, except if it is localhost (127.0.0.1) However since you are running a different server, it isn't a loop to have WinGate use the local MS DNS server. You would need to simply use the IP address of the adapter though instead of 127.0.0.1.

Adrien