RE: Newly Installed SBS 2003 Odd Connect Computer Failure
- From: v-branee@xxxxxxxxxxxxxxxxxxxx ("Brandy Nee [MSFT]")
- Date: Thu, 25 May 2006 06:08:28 GMT
Hello Jeff,
Thank you for posting to the SBS NEwgroup.
Thanks a lot for Maxibo's input!
May I know what Media Centre version you are using now. If it is Windows XP
Media Center Edition 2005, this is an expected behavior. We cannot join a
MCE computer to a Windows domain.
As Maxibo said, Windows XP Media Center Edition does not support a scenario
where you join your computer to a domain. Windows XP Media Center Edition
is designed as the foundation for a premier home entertainment system.
Media Center allows you share Media Center content with other locations in
the home by using Media Center Extender devices. Media Center Extender
devices require concurrent connections, and these connections are available
only through the Fast User Switching component. Therefore, the domain join
functionality in Windows XP Media Center Edition is disabled.
For more info, please refer to:
887212 You cannot join your computer to a domain in Windows XP Media Center
http://support.microsoft.com/?id=887212
NOTE: In earlier versions of Media Center, you can join it to a domain but
it is not a supported scenario in SBS Server 2003.
Although MCE clients cannot join the domain, they can still use UNC path to
access the domain resource. When they do that, they need to enter the valid
user credential on the pop-up user credential message box.
In SBS Server, we can join Windows XP professional edition or Windows 2000
professional system as client computer. So we suggest that you install
Windows XP Professional and join it to the Domain.
Hope it helps! If you have any further questions or concerns, please feel
free to let me know. I am looking forward to hearing from you!
Best regards,
Brandy Nee
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Jeff" <alynian@xxxxxxxxxxx>18:07:09 GMT)
Newsgroups: microsoft.public.windows.server.sbs
Subject: Newly Installed SBS 2003 Odd Connect Computer Failure
Date: 24 May 2006 11:07:04 -0700
Organization: http://groups.google.com
Lines: 46
Message-ID: <1148494024.093808.177550@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 71.113.155.171
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1148494029 13972 127.0.0.1 (24 May 2006
X-Complaints-To: groups-abuse@xxxxxxxxxx..NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC
NNTP-Posting-Date: Wed, 24 May 2006 18:07:09 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
4.0),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxxTK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed00
Injection-Info: i39g2000cwa.googlegroups.com; posting-host=71.113.155.171;
posting-account=L1v1WA0AAACnfHI1mUcu9vEKtUSxavwJ
Path:
..sul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.
giganews.com!nntp.giganews.com!postnews.google.com!i39g2000cwa.googlegroups.
com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:270572
X-Tomcat-NG: microsoft.public.windows.server.sbs
I've recently installed SBS 2003 SP1 on a machine. Followed all the
wizards on creating users and assigning them to specific computer
names. From the client - IE - //server/connectcomputer I run the
connect wizard.
I'm able to log in using the User ID and password, it comes up with the
related computer name for the user ID, continues with all the windows
without any problems. The final window has the "Finish" button which I
click on.
Immediately after I click on "Finish" IE displays a new page reading as
follows:
An error occured when configuring your network settings. See your
network administrator.
<hyperlink> Connect to the network now <end hyperlink>
Some things to note.
1) There are no reboots prior to this error.
2) A new local user account __sbs_netsetup__ with administrator
privilages (for the client machine) is created on the client's machine.
3) The client computer name is NOT changed to the one associated to the
user logon (which was correct when running the wizard).
4) The client is running Windows XP Media Center edition (all updates
have been applied on it)
5) The client's DNS has been hardcoded with the server's static IP
address (and I'm able to ping using the server name without any
problems).
6) The client is receiving it's own IP address via a DHCP router up the
hardcoded DNS remains listed.
7) Running MSCONFIG and disabling everything non-microsoft (both in
startup and services running) ...and I mean everything, results in the
same problem. So it does not seem to be related to Anti-virus
software, firewall software or any other non-Windows XP software that
is on the system.
As far as I can tell, there aren't any issues with DNS resolution as
those cleared up once I hardcoded the IP address for the server on the
client. I was unable to complete the client wizard (reached the final
screen with the "Finish" button) until I hardcoded the server's IP
address in the DNS of the client.
Any help with this will be greatly appreciated.
.
- Follow-Ups:
- References:
- Prev by Date: RE: Http 403.6 error
- Next by Date: Re: SBS2003 + Project, Sharepoint 2007 Servers...
- Previous by thread: Re: Newly Installed SBS 2003 Odd Connect Computer Failure
- Next by thread: Re: Newly Installed SBS 2003 Odd Connect Computer Failure
- Index(es):
Relevant Pages
|
