Announcement

Collapse
No announcement yet.

Network Crash of Domain

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Network Crash of Domain

    Dear All,
    I am facing this problem for the first time.
    Details of the Computers/Network
    192.168.1.1 - Internet Router
    192.168.1.250 - Wireless Router
    192.168.1.253 - Canon Printer
    192.168.1.254 - Windows 2008 R2 Server Standard Edition
    192.168.1.5 to 192.168.1.225 - Available for client computers
    Client Computers range from Windows 8 to Windows XP.
    Server Configuration:
    The server has been configured as the Primary Domain Controller with DNS, IIS & File Server. DHCP has also been configured on the server however using Open DHCP Server (open source DHCP Server) which shall allocate necessary IP address to the clients. The IP are leased for 12 hours.
    Problem:
    The whole network crashes without any proper reason at random. All the client and the server are not able to ping with each other. When we try ping, we get the message Destination host unreachable on all clients and server (pinging to the internet router, printer and wifi router (which are not part of the domain) gives the same error). But if I restart the server and the network, the everything begins functioning properly. There is no error message in the event viewer of the server also in this regard.
    Pl advise what could be the reason behind this issue and how to solve the same.
    Thanks and regards,
    --
    Sri

  • #2
    Re: Network Crash of Domain

    I would start by using Windows DHCP - solid as a rock - instead of the open source one.
    What do you mean by "restart the network" - reboot the switch? If you can try a different switch, it might be the cause

    When things go down, can you do an IPCONFIG/ALL on a client and post it up here
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Network Crash of Domain

      Dear Ossian

      Please find below the ipconfig/all output:


      Windows IP Configuration

      Host Name . . . . . . . . . . . . : IBH2
      Primary Dns Suffix . . . . . . . : ACS.LOCAL
      Node Type . . . . . . . . . . . . : Hybrid
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : ACS.LOCAL

      Ethernet adapter Local Area Connection 2:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : TeamViewer VPN Adapter
      Physical Address. . . . . . . . . : 00-FF-8D-19-92-F7
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes

      Ethernet adapter Local Area Connection:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : TAP-Win32 Adapter V9
      Physical Address. . . . . . . . . : 00-FF-C1-51-2D-78
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes

      Wireless LAN adapter Local Area Connection* 11:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
      Physical Address. . . . . . . . . : 12-08-CA-B2-C1-8C
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes

      Wireless LAN adapter WiFi:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter
      Physical Address. . . . . . . . . : 00-08-CA-B2-C1-8C
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Ethernet adapter Ethernet:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
      Physical Address. . . . . . . . . : C8-60-00-2B-64-CF
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::413a:efbd:744:df2c%12(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.1.9(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : 24 October 2013 08:26:40
      Lease Expires . . . . . . . . . . : 24 October 2013 19:05:22
      Default Gateway . . . . . . . . . : 192.168.1.1
      DHCP Server . . . . . . . . . . . : 192.168.1.254
      DHCPv6 IAID . . . . . . . . . . . : 264790016
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-FF-6D-BE-C8-60-00-2B-64-CF
      DNS Servers . . . . . . . . . . . : 192.168.1.254
      192.168.1.1
      208.67.222.222
      8.8.8.8
      208.67.220.220
      8.8.4.4
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Ethernet adapter VMware Network Adapter VMnet1:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
      Physical Address. . . . . . . . . : 00-50-56-C0-00-01
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::fddf:9955:50fe:aa01%25(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.153.1(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . :
      DHCPv6 IAID . . . . . . . . . . . : 1023430742
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-FF-6D-BE-C8-60-00-2B-64-CF
      DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
      fec0:0:0:ffff::2%1
      fec0:0:0:ffff::3%1
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Ethernet adapter VMware Network Adapter VMnet8:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
      Physical Address. . . . . . . . . : 00-50-56-C0-00-08
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::dcff:c5ee:4afe:d7ad%26(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.157.1(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . :
      DHCPv6 IAID . . . . . . . . . . . : 1040207958
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-FF-6D-BE-C8-60-00-2B-64-CF
      DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
      fec0:0:0:ffff::2%1
      fec0:0:0:ffff::3%1
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Tunnel adapter 6TO4 Adapter:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft 6to4 Adapter
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter Teredo Tunneling Pseudo-Interface:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter isatap.{1C1C52F2-59AB-41E3-8820-8545C9805425}:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter isatap.{9E818248-FBBD-452E-9080-282D023841F6}:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter isatap.{AB2000AB-2516-4ADF-90DC-4B65C3055D49}:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes



      By rebooting the switch i mean, switching off the power to the switch and switching it back on. Only a reboot of the system i.e., server, adsl router, wifi router and the switch is solving the problem.

      Pl advise. Also please let me know if there any way to identify if there is a problem with the switch, i mean some kind of device or so.

      Thanks
      Sri

      Comment


      • #4
        Re: Network Crash of Domain

        It sounds like the switch is your problem. What make/model do you use? When the failures occur, do the lights on the switch ports show normal activity, change color, go out?

        When hosts in a local network inside the same address space can't ping, the 'destination unreachable' message infers that your switch isn't switching. Have you checked that the switch fan is running? If it overheats, show's over.
        *RicklesP*
        MSCA (2003/XP), Security+, CCNA

        ** Remember: credit where credit is due, and reputation points as appropriate **

        Comment


        • #5
          Re: Network Crash of Domain

          What is the purpose of the DNS servers on the IPCONFIG you posted?

          If this is a domain environment your clients should point to only your internal DNS servers and your DNS servers should use forwarders to communicate with the external world.

          Fix that and see if it helps.

          Comment


          • #6
            Re: Network Crash of Domain

            if nothing can ping anything else via IP address, then it's the switch.
            Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

            Comment


            • #7
              Re: Network Crash of Domain

              Dear All.

              Thanx for the advise. I have identified the problem. Wifi Router was causing the problem. Now that we have removed the router, the network is function properly. Thanx for the advise once again.

              Comment


              • #8
                Re: Network Crash of Domain

                Very glad you got it fixed, and thanks for reporting back
                Tom Jones
                MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
                PhD, MSc, FIAP, MIITT
                IT Trainer / Consultant
                Ossian Ltd
                Scotland

                ** Remember to give credit where credit is due and leave reputation points where appropriate **

                Comment

                Working...
                X