Announcement

Collapse
No announcement yet.

Systems not accessible.

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

  • Systems not accessible.

    Hi all,

    Recently i installed new windows 2003 std edition based domain server with exchange 2003. DNS and DHCP Servers are also installed on it.

    Problem: Some of the systems (NOT ALL) are not accessible from other systems.

    Comp-A= not Accessible.
    Comp-B= Accessible.
    Findings:
    1- if we try to access Comp-A from Comp-B, I can't (\\Comp-A). Comp-A can access Comp-b, Domain Server and other accessible systems.
    2- I can ping Comp-A from Comp-B, With IP & FQDN
    3- When i restart Comp-A, Computer browser Service & Firewall doesn't starts itself.
    4- When i disjoin Comp-A from domain and rejoin it, it works for some time(1 hr or 1 Day) but after that problem arises again.
    5- able to telnet Comp-A with 139 port.
    6- DNS lookup command runs successfully from comp-A.
    7- net view \\Comp-A from comp-b returns error "system error 53 has occured. Network path not found".

    Please help me out to resolve this problem.
    Thanks
    Manoj Bhardwaj

  • #2
    Re: Systems not accessible.

    You should look at the Workstation and Server services and make sure they are started. Also make sure File & Printer sharing is bound to the NIC. Make sure Windows Firewall is turned off. If all the above is OK you should be able to access it by \\Comp-A\c$. If not, then you won't.

    Comment


    • #3
      Re: Systems not accessible.

      Thanks for your reply,

      Workstation and Server services- Running
      File & Printer sharing - Bounded
      Firewall - turned off
      but \\Comp-A or \\Comp-A\c$ still not Accessible

      Regards
      Manoj

      Comment


      • #4
        Re: Systems not accessible.

        What happens if you try to access the shares using the ip??

        Instead of \\compa\c$ try \\IPAddress\c$

        Comment


        • #5
          Re: Systems not accessible.

          Sounds like CompA is not well. Also sounds like a similar problem I am having where I have a 2003 server which runs fine for days/hours/minutes then the NIC card loses connection to the network. I then can not even ping the router- nothing.

          I tried a different NIC card but I have the same problem. I'm starting to feel that there is an MS patch which was recently released that has killed off both our NIC connections.
          |
          +-- JDMils
          |
          +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
          |

          Comment


          • #6
            Re: Systems not accessible.

            Hi All,
            Thanks for your suggestions, but my problem is different. Comp A doesn't have any problem, as i said earlier this comp can access other systems.
            I want to share some more information-
            MY DC has two NIC Cards, Before installing Active Directory configured both of them

            NIC1 (Internal)
            192.X.X.3
            255.255.255.0
            Gateway--------------NoGateway---------
            DNS
            192.X.X.3(its own IP)

            NIC2 (External)
            X.X.X.X
            Subnet X.X.X.X
            Gateway X.X.X.X
            DNS X.X.X.X, X.X.X.X

            NIC2 has all the information given by isp. Please Guide me, is that problem beacuse of the DNS value i have given to NIC2 before installing Active directory?

            Regards
            Manoj

            Comment


            • #7
              Re: Systems not accessible.

              Hi,


              Disable NIC 2 and check, do configure gateway and DNS on NIC1 as its your DC....


              Do not configure DC as Internet gateway, hackers will crack your network info..


              Regards
              Muneer

              Comment


              • #8
                Re: Systems not accessible.

                Thanks for suggestions, but its protected by hardware firewall. Can we reconfigure DNS server after AD installation, means i want to delete exsisting Zones and remove dns role of the server and than disable nic2 and re install dns with ad integration. Please suggest is that safe.
                Thanks
                Manoj

                Comment


                • #9
                  Re: Systems not accessible.

                  Hi,

                  Kindly check on faulty/problematic machine is any event log for computer

                  browser, is computer browser service is started on your probmatic machine, what

                  if you turned off/stop the computer browser service on probmatic machine..

                  Regards
                  Muneer

                  Comment


                  • #10
                    Re: Systems not accessible.

                    Computer browser doesn't starts itself, and leave following error event on the machine.


                    Event Type: Error
                    Event Source: Service Control Manager
                    Event Category: None
                    Event ID: 7023
                    Date: 1/23/2008
                    Time: 5:30:07 PM
                    User: N/A
                    Computer: GAURAVSHARMA
                    Description:
                    The Computer Browser service terminated with the following error:
                    This operation returned because the timeout period expired.

                    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



                    Do u agree that the problem is because of DNS. And i can reinstall the DNS Server.
                    Regards
                    Manoj

                    Comment


                    • #11
                      Re: Systems not accessible.

                      Hi,

                      Do not reinstall the DNS server, but recheck your dns server for confguration..



                      what is the OS of problematic machine and what is the role of the machine.

                      Regards
                      Muneer

                      Comment


                      • #12
                        Re: Systems not accessible.

                        Windows XP


                        NS LOOK Up and commands for DNS are runnig perfectly........
                        Is that because of no. of CAL (license).

                        Thanks
                        Manoj
                        Last edited by Manojbhardwaj; 6th February 2008, 09:59. Reason: Add some more info

                        Comment


                        • #13
                          Re: Systems not accessible.

                          Hi,

                          Yep that could be one of the reason...

                          How the license is configure on server..

                          Regards
                          Muneer

                          Comment


                          • #14
                            Re: Systems not accessible.

                            200 Cals, No of clients are less than it.
                            Thanks
                            Manoj

                            Comment


                            • #15
                              Re: Systems not accessible.

                              Yester day i enabled license loggig services but didn't get any error event in eventviewer. It seems to me that error is not because of licensing.
                              Regards
                              Manoj

                              Comment

                              Working...
                              X