Server 2003 and User Connection

Is there a brief step-by-step guide to use for installing Server 2003 on a
server PC and then connecting to that server with a remote PC. I think I have
the parts in-place but am not able to make the connection. Both PC's are
hard-wire connected to the same router as well.

I am running Windows Server 2003 R2 sp2

I started a post and unfortunately happened to be on the SBS group, where I
learned a few things beyond my original question above.

As stated, I have a trial version of Server 2003 and trying to implement it
in the fastest method so I can evaluate whether this is my ultimate direction
to go. I will end up with a server supporting maybe (3) user PC's; (2)
printers and (1) scanner. That is if all goes well.

The PC's will either be Windows XP-Pro or Vista Home Premium. And one of the
things I heard was that Vista Home editions would not allow connections to a
Domain. I'm interested in hearing further comments on this, because I may
have to upgrade OS.

The 2nd thing I need to know is what a DOMAIN name should look like. an it
be a simple 1-word domain like ELJAC ? Are there rules ? Apparently the
wizard of installation allowed me to call it ' MainOffice.microsoft.com '
--
ELJAC

 

Hello ELJAC,

What kind of connection do you mean Remote desktop connection form the workstation
to the server? Or mapping to shared folder on the server. Please be more
specific.

For connectivity make sure that you can ping between the machines with the
ip address. That's the first step, physical connection.

Home-premium is not able to connect to a domain, that's correct, you need
Ultimate or Business version. XP Pro can connect.

A domain name should have a form like Domainname.tld where tld is the the
top level domain, which should not be one of the officials used in the internet
like .com etc. In a private network use something like .loc or .local(has
problems with MAC computers).

Do not use only DOMAIN, this is called a single label domain name and creates
lot's of problems.

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


> Is there a brief step-by-step guide to use for installing Server 2003
> on a server PC and then connecting to that server with a remote PC. I
> think I have the parts in-place but am not able to make the
> connection. Both PC's are hard-wire connected to the same router as
> well.
>
> I am running Windows Server 2003 R2 sp2
>
> I started a post and unfortunately happened to be on the SBS group,
> where I learned a few things beyond my original question above.
>
> As stated, I have a trial version of Server 2003 and trying to
> implement it in the fastest method so I can evaluate whether this is
> my ultimate direction to go. I will end up with a server supporting
> maybe (3) user PC's; (2) printers and (1) scanner. That is if all goes
> well.
>
> The PC's will either be Windows XP-Pro or Vista Home Premium. And one
> of the things I heard was that Vista Home editions would not allow
> connections to a Domain. I'm interested in hearing further comments on
> this, because I may have to upgrade OS.
>
> The 2nd thing I need to know is what a DOMAIN name should look like.
> an it be a simple 1-word domain like ELJAC ? Are there rules ?
> Apparently the wizard of installation allowed me to call it '
> MainOffice.microsoft.com '
>

 

Connections that I am looking for are having a normal PC log onto the server.
Not using Remote Desktop , but in a domain environment. Along with your
comment, I have come to the conclusion that I will have to upgrade my Vista
'Home' Premium to "Ultimate"; and when that happens, maybe some of my
problems will resolve themselves.

I want my server to be just that, to service the printers, the scanner and
shared file folders. And the connections must be in the domain format of
logging onto the server.

As for the domain name, I need to work on that. As my company name is
ELJAC, I will want to try and configure it in somehow.

Thanks for your responses.

--
ELJAC


"Meinolf Weber [MVP-DS]" wrote:

> Hello ELJAC,
>
> What kind of connection do you mean Remote desktop connection form the workstation
> to the server? Or mapping to shared folder on the server. Please be more
> specific.
>
> For connectivity make sure that you can ping between the machines with the
> ip address. That's the first step, physical connection.
>
> Home-premium is not able to connect to a domain, that's correct, you need
> Ultimate or Business version. XP Pro can connect.
>
> A domain name should have a form like Domainname.tld where tld is the the
> top level domain, which should not be one of the officials used in the internet
> like .com etc. In a private network use something like .loc or .local(has
> problems with MAC computers).
>
> Do not use only DOMAIN, this is called a single label domain name and creates
> lot's of problems.
>
> 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
>
>
> > Is there a brief step-by-step guide to use for installing Server 2003
> > on a server PC and then connecting to that server with a remote PC. I
> > think I have the parts in-place but am not able to make the
> > connection. Both PC's are hard-wire connected to the same router as
> > well.
> >
> > I am running Windows Server 2003 R2 sp2
> >
> > I started a post and unfortunately happened to be on the SBS group,
> > where I learned a few things beyond my original question above.
> >
> > As stated, I have a trial version of Server 2003 and trying to
> > implement it in the fastest method so I can evaluate whether this is
> > my ultimate direction to go. I will end up with a server supporting
> > maybe (3) user PC's; (2) printers and (1) scanner. That is if all goes
> > well.
> >
> > The PC's will either be Windows XP-Pro or Vista Home Premium. And one
> > of the things I heard was that Vista Home editions would not allow
> > connections to a Domain. I'm interested in hearing further comments on
> > this, because I may have to upgrade OS.
> >
> > The 2nd thing I need to know is what a DOMAIN name should look like.
> > an it be a simple 1-word domain like ELJAC ? Are there rules ?
> > Apparently the wizard of installation allowed me to call it '
> > MainOffice.microsoft.com '
> >
>
>
>