Problems with Windows 2003 Server with Windows XP Clients

[Darryl Lict]

I've got a Windows 2003 server and 3 computers running Windows XP. The XP computers are in a workgroup called CompanyT. Is it possible to some how set up the Server merely as a workgroup computer or do I have to set up a domain?

I can actually set up Windows XP Server if it helps at all.

Soon, I also want to have a media serving computer which performs some or all of the following functions:

• Blueray (or DVD) burner/player.
• DVR
• File Server with Raid 1.
• Netflix server.
• Automatic off site backup.

I'd like to be able to access files on this media server through the network. What should I be concerned about?

Bottom line, I need to be able to back up files on the Windows Server in the short term but I can't figure out how to share a directory on the server with the XP computers.

[Quartz]

Are the clients XP Home or XP Pro?

Seems like you might be better with two boxes: Windows Home Server and Windows Media Centre.

[SunSandSuffering]

You don't need a domain, although you can use one. Add user accounts to the server that exactly match the username / password combinations in use on the workstations (whether XP home or Pro) then you can run the shares without the logon nag. ETA: the workstations can remain in the workgroup.

[drachillix]

Originally Posted by Quartz

Are the clients XP Home or XP Pro?

Seems like you might be better with two boxes: Windows Home Server and Windows Media Centre.

I know you love home server but its kinda getting to be old news. 2008 or 2011 Essentials packages are cheap, easily run on any decent box, and much easier to set up than 2003 era stuff ever was.

If the OP is looking to upgrade client machines later on its also going to make life easier having win7 machines to work with.

[Quartz]

Originally Posted by drachillix

I know you love home server but its kinda getting to be old news. 2008 or 2011 Essentials packages are cheap, easily run on any decent box, and much easier to set up than 2003 era stuff ever was.

There's a new version of Home Server. It's a version of SBS 2011.

[md2000]

A server can be a workgroup or a domain. XP Pro can connect to domains, regular XP can only connect to workgroups.

The problem with workgroups is they are not domains. Each userid/password is local to each box. As mentioned above, if you make the name/password the same on the local box and the server, or do not require passwords (allow the group "Everyone" access) then there is no hassle- it will look like user Fred can login to the server, but the server is actually assuming the XP machine means "server\fred" when "xp box\fred" connects; it works because the passwords are the same too. To change a password, you have to change it in 2 or more places, once on each box.

or, you can set up completely different user/password on the server; and the person enters that each time they connect to the server.

If it's a local server, no chance the files can be accessed by random users on the internet, why password protect? Just try making shares Read Only if you are worried about deletion.

[drachillix]

Originally Posted by Quartz

There's a new version of Home Server. It's a version of SBS 2011.

I stand corrected..

[Darryl Lict]

Hey, thanks for responding. I have one XP Home machine, my ASUS netbook; the others are XP Pro. I assume future machines will all be Windows 7. That new version of Windows Home Server seems compelling. Will I be able to connect using my Windows XP Home netbook? I'm likely to upgrade to a Win 7 starter netbook, but not until this one dies.

@Quartz, two boxes sounds like a reasonable solution.

I'll spend a little time trying to futz around with the accounts and see if I can't get it to work as a workgroup, while keeping in mind an upgrade to a new Windows Home Server box.