Announcement

Collapse
No announcement yet.

VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

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

  • VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

    Our office has about 10 computers and 2 servers, all of them belong to the same domain. The 2 servers run Windows 2003 Enterprise & Standard, 1 runs as DC, DNS & DHCP server.

    2 of the workstations are running on Vista, it's been working flawlessly until today.

    Initially, these 2 Vista PCs have no internet, and can not see anything on the network.

    but the NIC resolves the domain, DNS & Gateway correctly by automatic obtain IP. I can ping from the problem Vista pc to server and gateway(Cisco firewall) no problem.

    We disabled TCP/IPv6 already on both Vista machines. I also moved the vista computers in Active Directory to a fresh OU called Vista.

    It seems the problem is DNS related.

    If I set the DNS server to 4.2.2.2 on the Vista pc, it works fine.

    When I use the vista pc to join the domain again, it gives error the domain could not be contacted. typical error for incorrect tcp/ip settings.

    However, all settings in TCP/IP IPv4 are correct and pointed to the correct IP. I tried obtaining IP & DNS automatically AND manually assigning IP to them.

    and I can ping to DNS / DC.

    if i do a NSLOOKUP on the vista, it just times out and can't resolve any address.

    I also did the following

    ran DCDIAG and found no issues at all.

    reset the switch (Dell PowerConnect 3448 managed) settings

    reboot the firewall (Cisco PIX506)

    clear the foward / reverse lookup zone computer names on DNS server

    changed computer name on problem Vista PCs.

    all of the above have no results.


    I was on the phone with microsoft tech support for 4 hours, they couldn't figure out either and said will call me again the next day...

    Anyone has idea what's going on?

  • #2
    Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

    Originally posted by mike2016 View Post
    I was on the phone with microsoft tech support for 4 hours, they couldn't figure out either and said will call me again the next day...
    Was that a month ago ?

    Can you post a Ipconfig /all for one of your Vistas and also a working XP?
    Caesar's cipher - 3

    ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

    SFX JNRS FC U6 MNGR

    Comment


    • #3
      Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

      Is the Vista PC currently a member of the domain? If it is can you hover your mouse over the network icon in the system tray and check that the computer is showing the domain name there?

      I've had a similar issue at a customer's site where NLA (Network Location Awareness) doesn't work as it should and the computer defaults to the public network firewall setting. This is much more restrictive than the private or domain profiles. In this site it was caused by NOD32 antivirus software.
      BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
      sigpic
      Cruachan's Blog

      Comment


      • #4
        Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

        Originally posted by L4ndy View Post
        Was that a month ago ?

        Can you post a Ipconfig /all for one of your Vistas and also a working XP?
        no it was earlier today..... i used 1 of my 2 free support incidents from my technet subscription. wasted...

        i'll post it up tomorrow when i'm back to work. but I compared the 2, they are all configured the same way.

        another thing is, the vistas can't resolve DNS, even I type in an IP to a website(our internal web as well as external), it still won't work.

        Comment


        • #5
          Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

          Originally posted by cruachan View Post
          Is the Vista PC currently a member of the domain? If it is can you hover your mouse over the network icon in the system tray and check that the computer is showing the domain name there?

          I've had a similar issue at a customer's site where NLA (Network Location Awareness) doesn't work as it should and the computer defaults to the public network firewall setting. This is much more restrictive than the private or domain profiles. In this site it was caused by NOD32 antivirus software.

          The Vista PC is a member of the domain, and it "sometimes" show the network as a domain network, sometimes it shows as "private network". it changes as I ping to the DNS server.

          I've disabled all firewalls on the Vistas and the DC/DNS server. We run a hardware firewall Cisco Pix 506 that all the mahcines are behind it.

          It had Mcafee antivirus installed on the Vista, but I've uninstalled the whole thing and the problem still exists.

          Comment


          • #6
            Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

            I did further testing with a Microsoft tech support using Network Monitor Tool 3.2 on the server and vista pc, and I got the following result


            ANALYSES OF THE CLIENT SIDE TRACE
            *********************************
            On the client side while opening website for www.live.com

            Client machine is regularly sending packets for the DNS query but there is no reply from the server for the DNS query.

            However for the ping request from the server to the client for which we were getting Request timed out on the server, we find that client is sending the reply packet to every ICMP request packet.


            521 36.862305 {IPv4:16} 192.168.2.2 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            522 36.862305 {IPv4:16} 192.168.2.37 192.168.2.2 ICMP ICMP:Echo Reply Message, From 192.168.2.37 To 192.168.2.2
            593 42.231445 {IPv4:16} 192.168.2.2 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            594 42.231445 {IPv4:16} 192.168.2.37 192.168.2.2 ICMP ICMP:Echo Reply Message, From 192.168.2.37 To 192.168.2.2
            728 47.731445 {IPv4:16} 192.168.2.2 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            729 47.731445 {IPv4:16} 192.168.2.37 192.168.2.2 ICMP ICMP:Echo Reply Message, From 192.168.2.37 To 192.168.2.2


            ANALYSES OF THE SERVER SIDE TRACE
            *********************************

            In the server side Trace we do not see any request coming for the DNS query of vista machine.

            Also we do not see any ICMP reply from vista machine on the server.

            We only see the ICMP (Ping) Request generated on the server. We do not see any ICMP (Ping) reply packet on the server side which is send by the vista machine.

            638 61.015625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            703 66.390625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            738 71.890625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            793 77.390625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            920 96.875000 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            947 101.890625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            1002 107.390625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37
            1035 112.890625 {IPv4:44} EVERESTAPP1 192.168.2.37 ICMP ICMP:Echo Request Message, From 192.168.2.2 To 192.168.2.37


            Does this look like a hardware related problem?

            I've tested 3 vista mcahines and they all have the exact same problems.

            Comment


            • #7
              Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

              Is there a firewall between them who is blocking the Echo reply messages (maybe on the server itself?
              Marcel
              Technical Consultant
              Netherlands
              http://www.phetios.com
              http://blog.nessus.nl

              MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
              "No matter how secure, there is always the human factor."

              "Enjoy life today, tomorrow may never come."
              "If you're going through hell, keep going. ~Winston Churchill"

              Comment


              • #8
                Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

                No there's nothing in between the server and client vista pc. They are wired to the same switch.

                I think I've found the problem, it's the Dell switch that is confusing the vista clients. In the switch management (web based), there's a setting for DNS server and domain name, but it's set correctly as it sends a DHCP request to the server and sets itself automatically.

                But once I clear the DNS settings and re-apply it again, the vista clients starts working, for only a minute then it stops again.

                I'm going to try reflashing the switch to a newer firmware tomorrow and see what happens...

                Comment


                • #9
                  Re: VISTA on Win2k3 domain, no network, no internet, can not rejoin domain

                  FOUND THE PROBLEM!!!

                  Stupid DELL NIC firmware update was the problem, it got assigned 2 different MAC ids to the same NIC, one is for regular use, the other is for the Dell remote management purpose.

                  for some reason, the 2nd MAC got assigned the same IP as the server itself, and the VISTA clients are looking at the 2nd MAC so it can't reach the server at all.

                  weird problem but it's all good now once I changed the IP on the dell remote interface.

                  Comment

                  Working...
                  X