DNS Confusion

[Ban Pahlawan]

Dear Sir,

I have a problem with IP & DNS settings for both clients & servers, my network inofrmation are as following :

1- Domain Server :

IP address : 10.0.0.1
Subnet : 255.0.0.0
DNS : 127.0.0.1

2- Internet Server ( Where the wingate is installed )

IP address :10.0.0.80
Subnet :255.0.0.0
another IP :192.168.0.1
Sunbnet :255.255.255.0
DNS : 80.90.160.130

Note : I have error on wingate DNS and the following inof are in the Bound & Available Bindings

Bound Status
192.168.0.1 Error
10.0.0.80 Error

Available Status
169.254.138.1 Stopped


3- Clients :
IP address : 10.0.0.*
Subnet :255.0.0.0
Other IP :192.168.0.*
Subnet :255.255.255.0
Gateway :192.168.0.1
DNS :80.90.160.130 ( form ISP )

The main problem in my network is long time to log on to the network from any client also a sudden frezz when browsing the web also when connecting to a shared folder on the domain server.

Your software is a great software but I need to go over those small problems, also I need to assure that all my clients can log on to the domain and access the shared recources also the main thing access the Internet and using Outlook.

My regards & Good Luck

Note : Please I need your reply as soon as possible

Ban Pahlawan
[/list][/code]

[erwin]

Hi Ban

If all of your clients require Internet Access through WinGate (Via NetworkAddress Translation (NAT)) then they need to have their Gateway and DNS to point at the internal adapter on the WinGate Server.

I see the clients have their gateway configured to WinGAte 192.168.0.1
By setting their DNS to WinGate server IP 192.168.0.1, will force the clients to use (NAT) Network Address translation for Internet connection.
By setting the clients to use the DNS of the WinGate machine should sort out your client DNS issues.

The IP 169.254.138.1 you see in WinGate is issued by the MS Operating System when either no IP is entered for an adapter, and no DHCP server is available. My suggestion would be to recheck your TCP settings on the WinGate machine to see if they are correct. Any changes to adapter addresses on the WinGte machine will require a restart to the WinGate engine for it to rebind properly.

Let us know how you get on.

[adrien]

One other thing.

Those bindings showing up as error on the DNS server normally means there is a port conflict.

That would indicate that there is another DNS server running on that machine? Are you running also the MS DNS server on that machine?

Adrien

[Ban Pahlawan]

Dear All,

Thanks for the information, it was realy helpfull and I think we are about to know the cause of the problem, I think its a DNS conflict to cleare the picutre please note the following :

My Internet server is a replication of the Domain server and in both of them the DNS server service & Client DNS service are running do I have to stope them ?

Also I tired to put the 192.168.0.1 IP address as a DNS on one of the client computer but I couldn't access the Internet therefore I added as an alternative DNS IP to 80.90.160.130 but the problem still there.

Note: I have many error messages on both servers regarding DNS replication & registration.

[chr]

I had a DNS-problem (i know that this isnt your solution) but perhaps someone else can use this,

1 Someone on the net spoofed the DNS-servers adresses
2 By default Wingate "blackholes" these adressess.
2 Name resolving wont work...

Took me some hours but nows its working.