2003 Domain Issue
Again; I Have Small Network 50PCs, 1 Domain Server (2003), Internet (Using CISCO Router), Firewall Juniper. Cisco Router Linked To Juniper Fire Wall Then The Juniper Fire Wall Linked To The Main Switch... Juniper Firewall Acts As DHCP Server ..... Here Is The Problem: We Got To The Point Where We Can not Ping The Server, or Any PC On The Network ... Some Time You Can Ping .. Some Others No ... Plus When We Can Ping The Server Ther Is A Delay .... I Removed The FireWall ... So The Router Now Works As DHCP Server For The Workstaions .... Any One Can Help On This Issue ... Is There Any Thing I Can DO To stop This In Future .... Plus Do I Need To Reinstall The Firewall Again (Is It Important To Do So .. Although The CISCO Has A F=Built In Firewall) ... Thankx
June 18th, 2009 10:23am
Hello,please post an unedited ipconfig /all from the DC/DNS server and one problem client. Also configure the DCas DHCP server, not the firewall. Advantage is that also DNS updates can be done from DHCPand you have more configuration options for DHCP.Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 10:26am
Hi Meinolf Weber Thankx For Your Reply; The Ping Result Was: Request Timed Out Request Timed Out Request Timed Out Request Timed Out Then Request Timed Out Reply From 192.168.x.x : Bytes=32 time xxxxxxxxx Reply From 192.168.x.x : Bytes=32 time xxxxxxxxx Request Timed Out And So On; But Most Of The Time I Get: Request Timed Out. So When I Removed The Firewall ; And Linked The CISCO Router (Internet Service Through IT) To The Switch (Acts As DHCP Server) ... It Works Fine So Far With ME. And By The Way; Do I Need To Use A FireWall After The Cisco Router ... Iam Not The One Who Biult The System (I Found It Like THis) Thankx Again
June 18th, 2009 11:13am
Hello,if you read my previous post again you will see that i meant the IPCONFIG /ALL and not the ping answer. The router port is connected to the internet so use the firewall behind the router.Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 11:25am
ok here it is: Physical Address ...................: xxxxxxxxxxxxxxxx DHCP Enabled.......................: Yes AutoConfiguration Enabled .....:Yes IP Address ............................: 192.168.1.61 Subnet Mask..........................: 255.255.255.0 Default Gateway....................: 192.168.1.1 DHCP Server........................: 192.168.1.1 DNS Servers .......................: 192.168.1.2 xx.xx.xx.2 (Internet DNS IP) Leased Obta.............................................. Lease Expire ................................................................ Thankx Again
June 18th, 2009 12:56pm
Hello,assuming that this is the workstation, hopefully because a DC/DNS server should have fixed ip addresses, remove the ISPs DNS server from the NIC. The ISPs DNS server has to be configured as a FORWARDER on the DNS server properties in the DNS management console.And again, better use the server for DHCP and not the firewall in your case. Firewalls and routers should only do there basic job, not DNS or DHCP.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 1:11pm
Again; Thankx Alot Meniolf 1. Yes This Is Work Station. DC/DNS Have Static IPs (x.x.x.1 & x.x.x.2). 2. You Mean Remove The ISP IP Address From TCP/IP Properties. and Should I Keep The IP Address For The Server To Point At As Primary DNS. 3. ISPs DNS server has to be configured as a FORWARDER on the DNS server properties in the DNS management console (You Mean From The Router Console Right). 1 is ok. 3. is ok 2. Waiting For You To Resolve. Thankx Alot
June 18th, 2009 1:37pm
Hello,please read carefully my suggestions:"The ISPs DNS server has to be configured as a FORWARDER on the !!!DNS server properties in the DNS management console!!!"Also see and read carefully:http://support.microsoft.com/kb/323380NOT on the NIC, domain internal use only the 192.168.1.2 as DNS on the NIC.So the DC/DNS should look similar to this example:DHCP Enabled.......................: NoAutoConfiguration Enabled .....: NoIP Address ............................: 192.168.1.2Subnet Mask..........................: 255.255.255.0Default Gateway....................: 192.168.1.1DNS Servers .......................: 192.168.1.2Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 1:47pm
Thankx Alot Meinolf ... Wish U Good Luck In Your Life ...
June 18th, 2009 1:56pm


