XP home edition and networking

[Guest]

I have an NT4 domain and owned a laptop with XP Pro with SP2 and had no
problems using the domain resources. I bought a new laptop which came
pre-installed with XP Home with SP2 and always have problems using the domain
resources. Right after purchasing the laptop I attempted to upgrade it from
Home to Pro and was surprised that Home w/ SP2 will not upgrade to Pro w/ SP1.

I am a Registered Partner and there hasn't been a shipment of a Pro w/ SP2
DVD yet.

I am wondering if there is anything I can do to overcome fact that Home
doesn't allow you to truly join a domain in order to use all the resources on
that domain? Specifically I have big problems accessing SQL Server and
occasional problems accessing Exchange Server.

 

[Mike Brannigan [MSFT]]

I have an NT4 domain and owned a laptop with XP Pro with SP2 and had no
problems using the domain resources. I bought a new laptop which came
pre-installed with XP Home with SP2 and always have problems using the
domain
resources. Right after purchasing the laptop I attempted to upgrade it
from
Home to Pro and was surprised that Home w/ SP2 will not upgrade to Pro w/
SP1.

You cannot upgrade because you are trying to upgrade to a older version fo
the operating system (at the core OS level an integrated SP2 OS is newer
then a SP1)

I am a Registered Partner and there hasn't been a shipment of a Pro w/ SP2
DVD yet.

Make you own ? Just slipstream SP2 into an SP1 XP and burn a new CD. There
are plenty of instructions out there about how to do this.

I am wondering if there is anything I can do to overcome fact that Home
doesn't allow you to truly join a domain in order to use all the resources
on
that domain? Specifically I have big problems accessing SQL Server and
occasional problems accessing Exchange Server.

You can usually access a resource by providing a domain\username and
password combination.
So for example I have a workgroup machine that I want to access an e-mail
box on an Exchange 2003 serve - I just have to specific some credentials and
have them remembered when I set up the Outlook client on the PC.
one other thing you can do is to map to the IPC$ on a server and provide
some credentials - you can do this in you login script (which you can have
on a none domain machine) that does a
net use \\servername\IPC$ /U:domain\username password
see the net use /? for more was of doing this.
This may allow you access to the resource on that server without having to
specify additional sets of credentials.
SQL Server access depends on the SQL security model used and application
etc.



--

Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups