1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Difference between Server 2003 Standard and Enterprise?

Discussion in 'Windows Home Server' started by Carl Smith, May 21, 2009.

  1. Carl Smith

    Carl Smith Guest

    I have noticed that when joining server 2003 standard domain / or enterprise
    domain. I have noticed that you have to type the full domain name for
    enterprise edition e.g. smallbusiness.local in on the client pc's whereas
    when you are joining in a standard environment you only have to type e.g.
    smallbusiness (without having to put .local or .com at the end)

    If someone has noticed this and you know why enterprise seems to want a full
    domain name rather than standard edition will you please let us know because
    i am looking all over the internet to try and find why they seem to work
    slightly differently in that area.
     
  2. Hello Carl,

    That has nothing to do with the server version, we run STD and EE and don't
    have that.

    Choosing the FQDN (domain.com) or the NetBIOS name (domain) depends on your
    DNS, WINS setup and NetBIOS configuration. Make sure the "TCP/IP NetBIOS
    Helper" service is running on the client machines and set to automatic.

    On the DC's run diagnostic tools dcdiag /v, netdiag /v and repadmin /showrepl(if
    more then one DC exist) and post the output here. Also from dnslint /ad /s
    "ipaddress DC"

    For the first 3 commands you have to install the support\tools\suptools.msi
    from the 2000/2003 installation disk on the DC, dnslint you can download
    here (http://support.microsoft.com/kb/321045)

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > I have noticed that when joining server 2003 standard domain / or
    > enterprise domain. I have noticed that you have to type the full
    > domain name for enterprise edition e.g. smallbusiness.local in on the
    > client pc's whereas when you are joining in a standard environment you
    > only have to type e.g. smallbusiness (without having to put .local or
    > .com at the end)
    >
    > If someone has noticed this and you know why enterprise seems to want
    > a full domain name rather than standard edition will you please let us
    > know because i am looking all over the internet to try and find why
    > they seem to work slightly differently in that area.
    >
     
  3. Kyle BLake

    Kyle BLake Guest

    I believe you need Enterprise edition to do Microsoft CLUSTERING.


    "Carl Smith" wrote:

    > I have noticed that when joining server 2003 standard domain / or enterprise
    > domain. I have noticed that you have to type the full domain name for
    > enterprise edition e.g. smallbusiness.local in on the client pc's whereas
    > when you are joining in a standard environment you only have to type e.g.
    > smallbusiness (without having to put .local or .com at the end)
    >
    > If someone has noticed this and you know why enterprise seems to want a full
    > domain name rather than standard edition will you please let us know because
    > i am looking all over the internet to try and find why they seem to work
    > slightly differently in that area.
     
  4. "Carl Smith" <CarlSmith@discussions.microsoft.com> wrote in message news:B2568EAA-5D9A-4288-A46C-C3F9E7CEC7D2@microsoft.com...
    >I have noticed that when joining server 2003 standard domain / or enterprise
    > domain. I have noticed that you have to type the full domain name for
    > enterprise edition e.g. smallbusiness.local in on the client pc's whereas
    > when you are joining in a standard environment you only have to type e.g.
    > smallbusiness (without having to put .local or .com at the end)
    >
    > If someone has noticed this and you know why enterprise seems to want a full
    > domain name rather than standard edition will you please let us know because
    > i am looking all over the internet to try and find why they seem to work
    > slightly differently in that area.



    Is NetBIOS disabled on the enterprise version you're using that you need to use the FQDN? That would be the only thing I can think of causing this. Or even the firewall on the client side.

    And as Meinolf said, operating system version has NOTHING to do with this.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer
    aceman@mvps.RemoveThisPart.org

    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
    http://twitter.com/acefekay
     
  5. Carl Smith

    Carl Smith Guest

    Thanks for the postings they have been very helpful.

    "Carl Smith" wrote:

    > I have noticed that when joining server 2003 standard domain / or enterprise
    > domain. I have noticed that you have to type the full domain name for
    > enterprise edition e.g. smallbusiness.local in on the client pc's whereas
    > when you are joining in a standard environment you only have to type e.g.
    > smallbusiness (without having to put .local or .com at the end)
    >
    > If someone has noticed this and you know why enterprise seems to want a full
    > domain name rather than standard edition will you please let us know because
    > i am looking all over the internet to try and find why they seem to work
    > slightly differently in that area.
     
  6. "Carl Smith" <CarlSmith@discussions.microsoft.com> wrote in message news:AAB7C462-E187-4BB8-B49B-F5247A7B0E9B@microsoft.com...
    > Thanks for the postings they have been very helpful.
    >


    You are welcome, Carl.

    Were you able to resolve the issue?

    Ace
     

Share This Page