1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Domain connectivity question

Discussion in 'Networking (Hardware & Software)' started by mklangelo, 2005/11/19.

  1. 2005/11/19
    mklangelo

    mklangelo Inactive Thread Starter

    Joined:
    2005/07/01
    Messages:
    41
    Likes Received:
    0
    Hi all,

    I have a small domain set up in my house for my MCSA studies. I'm using Virtual PC and have a Windows Server 2003 Enterprise Edition DC/DNS server and one XP Pro Client. Server01 and Client01.

    I have created a User account for myself in Active Directory and am a member of the Domain Admins. Client01 is shown as a member of the domain both in AD and in it's own System Properties. I can ping the server from the client and access it in My Network Places. However, I cannot ping the Client from the server, nor can I access Client01 from My Network Places on the Server.

    I am also able to log on to the client using my domain username and password. This has me stumped. :confused:


    There is no firewall running on either machine. I even checked IE security settings but that isn't the problem. Any ideas on this would be greatly appreciated.

    M :eek:

    BTW: In My Network Places on the server, Workgroup shows up, as well as the Domain since I initially set up the server as a Stand-alone Server. Once Active Directory is installed, the server automatically becomes a Domain Controller so I'm wondering why Workgroup still shows.
     
    Last edited: 2005/11/19
  2. 2005/12/14
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    This looks to me like you haven't joined the client to the domain. You have to configure the client to use the domain:

    Control Panel > System Properties > Computer Name > Change.

    Until this is done, the client will still be set up to use workgroup and will advertise the presence of this group in its NETBIOS broadcasts. This may account for the server detecting the presence of the workgroup group. However, it could just be that the server is taking a while to forget that there was a Workgroup NETBIOS group on the network.
     

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.