Adding Intel SS4000e NAS Server to Domain
|
Prev: ESENT 215
Next: workstation issues
From: Nick on 23 Dec 2008 08:37 Here is the process for activating Active Directory on the Intel ss4000e: 1. Screen 1 asks for the IP address of the AD server 2. Screen 2 asks for login info (user name), (password), (organizational unit name [optional]). the field for user name is followd by "@domain.local". This cannot be changed. It is looked up after entering the IP address. 3. Screen 3 auto populates a list of groups and you select the ones you want with a check box. 4. Screen 4 asks for the Active Directory Admin login info. After clicking "finish" a pop up then comes up saying that it may take several minutes to log in. After hitting OK a pop up comes up stating that the username and password do not have sufficient privileges to join the domain where the Active Directory server resides. That is as far as I can get. As I mentioned, I had this device on an SBS 2003 domain before and the process worked fine. I am not sure what is different in SBS 2008. On Dec 22, 8:59 pm, "Chad A Gross" <chad.gr...(a)laytonflower.nospam.com> wrote: > Ok Nick - > > Just out of curiosity, how are you listing your domain in the NAS > authentication page? Are you using the netbios name (DOMAIN) or the > fully-qualified domain name (domain.local)? If you're using the netbios > name, have you tried using the FQDN (or vice versa)? > > -- > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > "Nick" <j...(a)giovas.net> wrote in message > > news:079c8a82-fa5f-4c2d-9a7f-8aef9c86245f(a)a26g2000prf.googlegroups.com... > I just checked the logs folder and didn't find anything listed for a > domain join. I also checked the netsetup debug log and nothing was > listed at all for a domain join. > > Is there a different log I should be checking? Even the successful > joins were not listed. > > On Dec 22, 5:54 pm, Nick <j...(a)giovas.net> wrote: > > > > > I tried several names including Intel4000e, StorageServer and others. > > It still didn't work. > > > I will check the logs to see if anything is listed. > > > I also opened a ticket with Intel, but their first indication was that > > it is a Windows issue. I will see if they provide any additional > > info. > > > Nick > > > On Dec 22, 10:56 am, "Chad A Gross" > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > Just out of curiosity, what name did you give the NAS? I've seen > > > instances > > > where the NAS name matched the netbios domain name, and that caused all > > > sorts of issues including preventing the NAS from joining the domain. > > > > Are you getting any errors in the event logs on the server when you > > > attempt > > > to join the NAS to the domain?- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
From: Chad A Gross on 23 Dec 2008 10:10 OK, in screen 4, what are you entering for a username? Have you tried using DOMAIN\username ? I haven't worked with the Intel NAS devices, but several of the NAS devices I have worked with have been picky about the formatting of the domain & username to get them to join -- Chad A Gross http://www.msmvps.com/blogs/cgross "Nick" <junk(a)giovas.net> wrote in message news:26daf308-08dc-447c-a5a6-d6d68ea168b3(a)k36g2000pri.googlegroups.com... Here is the process for activating Active Directory on the Intel ss4000e: 1. Screen 1 asks for the IP address of the AD server 2. Screen 2 asks for login info (user name), (password), (organizational unit name [optional]). the field for user name is followd by "@domain.local". This cannot be changed. It is looked up after entering the IP address. 3. Screen 3 auto populates a list of groups and you select the ones you want with a check box. 4. Screen 4 asks for the Active Directory Admin login info. After clicking "finish" a pop up then comes up saying that it may take several minutes to log in. After hitting OK a pop up comes up stating that the username and password do not have sufficient privileges to join the domain where the Active Directory server resides. That is as far as I can get. As I mentioned, I had this device on an SBS 2003 domain before and the process worked fine. I am not sure what is different in SBS 2008. On Dec 22, 8:59 pm, "Chad A Gross" <chad.gr...(a)laytonflower.nospam.com> wrote: > Ok Nick - > > Just out of curiosity, how are you listing your domain in the NAS > authentication page? Are you using the netbios name (DOMAIN) or the > fully-qualified domain name (domain.local)? If you're using the netbios > name, have you tried using the FQDN (or vice versa)? > > -- > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > "Nick" <j...(a)giovas.net> wrote in message > > news:079c8a82-fa5f-4c2d-9a7f-8aef9c86245f(a)a26g2000prf.googlegroups.com... > I just checked the logs folder and didn't find anything listed for a > domain join. I also checked the netsetup debug log and nothing was > listed at all for a domain join. > > Is there a different log I should be checking? Even the successful > joins were not listed. > > On Dec 22, 5:54 pm, Nick <j...(a)giovas.net> wrote: > > > > > I tried several names including Intel4000e, StorageServer and others. > > It still didn't work. > > > I will check the logs to see if anything is listed. > > > I also opened a ticket with Intel, but their first indication was that > > it is a Windows issue. I will see if they provide any additional > > info. > > > Nick > > > On Dec 22, 10:56 am, "Chad A Gross" > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > Just out of curiosity, what name did you give the NAS? I've seen > > > instances > > > where the NAS name matched the netbios domain name, and that caused > > > all > > > sorts of issues including preventing the NAS from joining the domain. > > > > Are you getting any errors in the event logs on the server when you > > > attempt > > > to join the NAS to the domain?- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
From: Nick on 23 Dec 2008 14:16 I got the same results. Which log should this error be logged in on the SBS server? I don't see anything listed in any of the logs about a domain join failure. I did hear back from Intel and they sent a generic statements saying that they do not support Server 2008 and do not have plans to support it. According to their OS compatability chart, they only list server 2003 under domain controller compatability. I'm not sure what would have changed in the OS to cause it to fail. If I try the wrong password it gives a different error, so this definitely appears to be a privileges issue. On Dec 23, 10:10 am, "Chad A Gross" <chad.gr...(a)laytonflower.cnospam.com> wrote: > OK, in screen 4, what are you entering for a username? Have you tried using > DOMAIN\username ? > > I haven't worked with the Intel NAS devices, but several of the NAS devices > I have worked with have been picky about the formatting of the domain & > username to get them to join > > -- > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > "Nick" <j...(a)giovas.net> wrote in message > > news:26daf308-08dc-447c-a5a6-d6d68ea168b3(a)k36g2000pri.googlegroups.com... > Here is the process for activating Active Directory on the Intel > ss4000e: > > 1. Screen 1 asks for the IP address of the AD server > > 2. Screen 2 asks for login info (user name), (password), > (organizational unit name [optional]). the field for user name is > followd by "@domain.local". This cannot be changed. It is looked up > after entering the IP address. > > 3. Screen 3 auto populates a list of groups and you select the ones > you want with a check box. > > 4. Screen 4 asks for the Active Directory Admin login info. > > After clicking "finish" a pop up then comes up saying that it may take > several minutes to log in. After hitting OK a pop up comes up stating > that the username and password do not have sufficient privileges to > join the domain where the Active Directory server resides. > > That is as far as I can get. As I mentioned, I had this device on an > SBS 2003 domain before and the process worked fine. > > I am not sure what is different in SBS 2008. > > On Dec 22, 8:59 pm, "Chad A Gross" > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > Ok Nick - > > > Just out of curiosity, how are you listing your domain in the NAS > > authentication page? Are you using the netbios name (DOMAIN) or the > > fully-qualified domain name (domain.local)? If you're using the netbios > > name, have you tried using the FQDN (or vice versa)? > > > -- > > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > > "Nick" <j...(a)giovas.net> wrote in message > > >news:079c8a82-fa5f-4c2d-9a7f-8aef9c86245f(a)a26g2000prf.googlegroups.com.... > > I just checked the logs folder and didn't find anything listed for a > > domain join. I also checked the netsetup debug log and nothing was > > listed at all for a domain join. > > > Is there a different log I should be checking? Even the successful > > joins were not listed. > > > On Dec 22, 5:54 pm, Nick <j...(a)giovas.net> wrote: > > > > I tried several names including Intel4000e, StorageServer and others. > > > It still didn't work. > > > > I will check the logs to see if anything is listed. > > > > I also opened a ticket with Intel, but their first indication was that > > > it is a Windows issue. I will see if they provide any additional > > > info. > > > > Nick > > > > On Dec 22, 10:56 am, "Chad A Gross" > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > > Just out of curiosity, what name did you give the NAS? I've seen > > > > instances > > > > where the NAS name matched the netbios domain name, and that caused > > > > all > > > > sorts of issues including preventing the NAS from joining the domain. > > > > > Are you getting any errors in the event logs on the server when you > > > > attempt > > > > to join the NAS to the domain?- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
From: Cris Hanna [SBS - MVP] on 23 Dec 2008 14:53 Just as a thought Try re-enabling the "real" Administrator (the true 500 account) I believe the password is blank but you may want to change it for this exercise. Then try joining with that account. It's a WAG but there have some been some issues with installing Trend WF 5.1 if you don't use the true Administrator account. -- Cris Hanna [SBS - MVP] Co-Author, Windows Small Business Server 2008 Unleashed http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1 Owner, CPU Services, Belleville, IL A Microsoft Registered Partner ------------------------------------ MVPs do not work for Microsoft Please do not submit questions directly to me. "Nick" <junk(a)giovas.net> wrote in message news:c2fc9236-5a2b-4048-be57-083a686a8f18(a)s9g2000prm.googlegroups.com... I got the same results. Which log should this error be logged in on the SBS server? I don't see anything listed in any of the logs about a domain join failure. I did hear back from Intel and they sent a generic statements saying that they do not support Server 2008 and do not have plans to support it. According to their OS compatability chart, they only list server 2003 under domain controller compatability. I'm not sure what would have changed in the OS to cause it to fail. If I try the wrong password it gives a different error, so this definitely appears to be a privileges issue. On Dec 23, 10:10 am, "Chad A Gross" <chad.gr...(a)laytonflower.cnospam.com> wrote: > OK, in screen 4, what are you entering for a username? Have you tried using > DOMAIN\username ? > > I haven't worked with the Intel NAS devices, but several of the NAS devices > I have worked with have been picky about the formatting of the domain & > username to get them to join > > -- > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > "Nick" <j...(a)giovas.net> wrote in message > > news:26daf308-08dc-447c-a5a6-d6d68ea168b3(a)k36g2000pri.googlegroups.com... > Here is the process for activating Active Directory on the Intel > ss4000e: > > 1. Screen 1 asks for the IP address of the AD server > > 2. Screen 2 asks for login info (user name), (password), > (organizational unit name [optional]). the field for user name is > followd by "@domain.local". This cannot be changed. It is looked up > after entering the IP address. > > 3. Screen 3 auto populates a list of groups and you select the ones > you want with a check box. > > 4. Screen 4 asks for the Active Directory Admin login info. > > After clicking "finish" a pop up then comes up saying that it may take > several minutes to log in. After hitting OK a pop up comes up stating > that the username and password do not have sufficient privileges to > join the domain where the Active Directory server resides. > > That is as far as I can get. As I mentioned, I had this device on an > SBS 2003 domain before and the process worked fine. > > I am not sure what is different in SBS 2008. > > On Dec 22, 8:59 pm, "Chad A Gross" > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > Ok Nick - > > > Just out of curiosity, how are you listing your domain in the NAS > > authentication page? Are you using the netbios name (DOMAIN) or the > > fully-qualified domain name (domain.local)? If you're using the netbios > > name, have you tried using the FQDN (or vice versa)? > > > -- > > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > > "Nick" <j...(a)giovas.net> wrote in message > > >news:079c8a82-fa5f-4c2d-9a7f-8aef9c86245f(a)a26g2000prf.googlegroups.com.... > > I just checked the logs folder and didn't find anything listed for a > > domain join. I also checked the netsetup debug log and nothing was > > listed at all for a domain join. > > > Is there a different log I should be checking? Even the successful > > joins were not listed. > > > On Dec 22, 5:54 pm, Nick <j...(a)giovas.net> wrote: > > > > I tried several names including Intel4000e, StorageServer and others. > > > It still didn't work. > > > > I will check the logs to see if anything is listed. > > > > I also opened a ticket with Intel, but their first indication was that > > > it is a Windows issue. I will see if they provide any additional > > > info. > > > > Nick > > > > On Dec 22, 10:56 am, "Chad A Gross" > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > > Just out of curiosity, what name did you give the NAS? I've seen > > > > instances > > > > where the NAS name matched the netbios domain name, and that caused > > > > all > > > > sorts of issues including preventing the NAS from joining the domain. > > > > > Are you getting any errors in the event logs on the server when you > > > > attempt > > > > to join the NAS to the domain?- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
From: Nick on 23 Dec 2008 15:31
Thanks Cris. How do I enable the true 500 account? I tried logging in as administrator without a password, but it said that the account was disabled. How do I re-enable it? I don't see it listed under users. Thanks Nick On Dec 23, 2:53 pm, "Cris Hanna [SBS - MVP]" <crisnospamha...(a)cpunospamservices.net> wrote: > Just as a thought > Try re-enabling the "real" Administrator (the true 500 account) > I believe the password is blank but you may want to change it for this exercise. > > Then try joining with that account. > > It's a WAG but there have some been some issues with installing Trend WF 5.1 if you don't use the true Administrator account. > > -- > Cris Hanna [SBS - MVP] > Co-Author, Windows Small Business Server 2008 Unleashedhttp://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672... > Owner, CPU Services, Belleville, IL > A Microsoft Registered Partner > ------------------------------------ > MVPs do not work for Microsoft > Please do not submit questions directly to me. > > "Nick" <j...(a)giovas.net> wrote in messagenews:c2fc9236-5a2b-4048-be57-083a686a8f18(a)s9g2000prm.googlegroups.com... > I got the same results. Which log should this error be logged in on > the SBS server? I don't see anything listed in any of the logs about > a domain join failure. > > I did hear back from Intel and they sent a generic statements saying > that they do not support Server 2008 and do not have plans to support > it. According to their OS compatability chart, they only list server > 2003 under domain controller compatability. > > I'm not sure what would have changed in the OS to cause it to fail. > If I try the wrong password it gives a different error, so this > definitely appears to be a privileges issue. > > On Dec 23, 10:10 am, "Chad A Gross" <chad.gr...(a)laytonflower.cnospam.com> wrote: > > > OK, in screen 4, what are you entering for a username? Have you tried using > > DOMAIN\username ? > > > > I haven't worked with the Intel NAS devices, but several of the NAS devices > > I have worked with have been picky about the formatting of the domain & > > username to get them to join > > > > -- > > > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > > > "Nick" <j...(a)giovas.net> wrote in message > > > >news:26daf308-08dc-447c-a5a6-d6d68ea168b3(a)k36g2000pri.googlegroups.com... > > Here is the process for activating Active Directory on the Intel > > ss4000e: > > > > 1. Screen 1 asks for the IP address of the AD server > > > > 2. Screen 2 asks for login info (user name), (password), > > (organizational unit name [optional]). the field for user name is > > followd by "@domain.local". This cannot be changed. It is looked up > > after entering the IP address. > > > > 3. Screen 3 auto populates a list of groups and you select the ones > > you want with a check box. > > > > 4. Screen 4 asks for the Active Directory Admin login info. > > > > After clicking "finish" a pop up then comes up saying that it may take > > several minutes to log in. After hitting OK a pop up comes up stating > > that the username and password do not have sufficient privileges to > > join the domain where the Active Directory server resides. > > > > That is as far as I can get. As I mentioned, I had this device on an > > SBS 2003 domain before and the process worked fine. > > > > I am not sure what is different in SBS 2008. > > > > On Dec 22, 8:59 pm, "Chad A Gross" > > > > > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > Ok Nick - > > > > > Just out of curiosity, how are you listing your domain in the NAS > > > authentication page? Are you using the netbios name (DOMAIN) or the > > > fully-qualified domain name (domain.local)? If you're using the netbios > > > name, have you tried using the FQDN (or vice versa)? > > > > > -- > > > > > Chad A Grosshttp://www.msmvps.com/blogs/cgross > > > > > "Nick" <j...(a)giovas.net> wrote in message > > > > >news:079c8a82-fa5f-4c2d-9a7f-8aef9c86245f(a)a26g2000prf.googlegroups..com... > > > I just checked the logs folder and didn't find anything listed for a > > > domain join. I also checked the netsetup debug log and nothing was > > > listed at all for a domain join. > > > > > Is there a different log I should be checking? Even the successful > > > joins were not listed. > > > > > On Dec 22, 5:54 pm, Nick <j...(a)giovas.net> wrote: > > > > > > I tried several names including Intel4000e, StorageServer and others. > > > > It still didn't work. > > > > > > I will check the logs to see if anything is listed. > > > > > > I also opened a ticket with Intel, but their first indication was that > > > > it is a Windows issue. I will see if they provide any additional > > > > info. > > > > > > Nick > > > > > > On Dec 22, 10:56 am, "Chad A Gross" > > > > > > <chad.gr...(a)laytonflower.nospam.com> wrote: > > > > > Just out of curiosity, what name did you give the NAS? I've seen > > > > > instances > > > > > where the NAS name matched the netbios domain name, and that caused > > > > > all > > > > > sorts of issues including preventing the NAS from joining the domain. > > > > > > > Are you getting any errors in the event logs on the server when you > > > > > attempt > > > > > to join the NAS to the domain?- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - |