Re: Can't see other computers/nodes on network!
- From: "Knight Technologies" <KnightTechnologies@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 14 Aug 2005 17:15:02 -0700
Doug I'm not following you on that because this is the server, I'm not trying
to have it join a workgroup I'm trying to have it host one.
Most the time system requirements are off when displayed, for instance
something that says minimum memory is 512 when it actually only requires 40 -
128.
The windows networking is supposed to work together fairly well, in the
networking samples I've seen say you can connect win 98 on up machine to any
windows workgroup so it should be fairly universal.
The other machines are Windows Home, I actually get better performance,
security, and convenience using Home when the service packs are installed,
I've noticed it only takes me minutes to accomplish what is taking me days or
weeks with Windows Server, I'm unhappy with Windows Server 2003 so far as I
keep having to seek answers to configuration related problems, and it doesn't
provide the kind of hardware/software support I'd expect it too.
--
Knight Technologies (http://knight-technologies.us)
E4 Chat (http://e4chat.com)
"Doug Sherman [MVP]" wrote:
> Your Windows Server 2003 machine is an Active Directory domain controller
> and therefore, cannot be joined to a workgroup. If your clients are running
> XP Pro, they can join the domain. If your clients are XP Home, they cannot
> join the domain; however, they should be able to browse if you change their
> workgroup to the NetBIOS name of the Active Directory domain - eg. NetBIOS
> name of mydomain.com = mydomain.
>
> Doug Sherman
> MCSE, MCP+I, MVP
>
> "Knight Technologies" <KnightTechnologies@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in message news:046ED2B6-E871-4C50-BE03-379177724FE3@xxxxxxxxxxxxxxxx
> > Clicking Change button pops up a warning that says "To continue renaming
> this
> > domain controller click OK."
> > --
> > Knight Technologies (http://knight-technologies.us)
> > E4 Chat (http://e4chat.com)
> >
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > "In Windows Server 2003 you can change the computer name and
> > > workgroup name in System Properties, Computer Name tab. No wizard is
> > > necessary."
> > >
> > > What happens when you click the Change button - or are you saying that
> you
> > > do not have a Computer name tab?
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Knight Technologies" <KnightTechnologies@xxxxxxxxxxxxxxxxxxxxxxxxx>
> wrote
> > > in message news:1C929AD2-A10D-4F40-8176-D5386C7C1E07@xxxxxxxxxxxxxxxx
> > > > Nope, nothing anywhere says Workgroup, it does in Windows XP though
> and I
> > > can
> > > > create a workgroup using that on another machine, but I still can't
> see
> > > any
> > > > machines on network aside from the machine names themselves alone.
> > > >
> > > > All the computers have a different name.
> > > >
> > > > How can I create a workgroup on Windows Server 2003 and/or have it see
> the
> > > > other machines, since there is no wizard, there is no obvious "hello,
> > > click
> > > > here to say I'm the main server, everyone else is a client."
> > > >
> > > >
> > > >
> > > > --
> > > > Knight Technologies (http://knight-technologies.us)
> > > > E4 Chat (http://e4chat.com)
> > > >
> > > >
> > > > "Doug Sherman [MVP]" wrote:
> > > >
> > > > > No. The workgroup name must be different from all computer names,
> all
> > > > > computers should by joined to the same workgroup, and all computer
> names
> > > > > must be unique. In Windows Server 2003 you can change the computer
> name
> > > and
> > > > > workgroup name in System Properties, Computer Name tab. No wizard
> is
> > > > > necessary.
> > > > >
> > > > > Doug Sherman
> > > > > MCSE, MCSA, MCP+I, MVP
> > > > >
> > > > > "Knight Technologies" <KnightTechnologies@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > > wrote
> > > > > in message
> news:FD443DA7-C0E7-4470-9842-C9F70A9D7041@xxxxxxxxxxxxxxxx
> > > > > > I can't see or find other computers on the network at all and I
> have
> > > File
> > > > > and
> > > > > > Printer Sharing turned on?
> > > > > >
> > > > > > Also, I'm running Windows Server 2003 and don't see how to create
> a
> > > group
> > > > > > network like with other Windows OS's, there is no "Create Home or
> > > Office
> > > > > > Network" option, etc. I'm assuming that as this is Windows Server
> the
> > > > > > computer name would be the workgroup correct?
> > > > > >
> > > > > > --
> > > > > > Knight Technologies (http://knight-technologies.us)
> > > > > > E4 Chat (http://e4chat.com)
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: Can't see other computers/nodes on network!
- From: Doug Sherman [MVP]
- Re: Can't see other computers/nodes on network!
- References:
- Can't see other computers/nodes on network!
- From: Knight Technologies
- Re: Can't see other computers/nodes on network!
- From: Doug Sherman [MVP]
- Re: Can't see other computers/nodes on network!
- From: Knight Technologies
- Re: Can't see other computers/nodes on network!
- From: Doug Sherman [MVP]
- Re: Can't see other computers/nodes on network!
- From: Knight Technologies
- Re: Can't see other computers/nodes on network!
- From: Doug Sherman [MVP]
- Can't see other computers/nodes on network!
- Prev by Date: RE: Can't see other computers/nodes on network!
- Next by Date: RE: Can't see other computers/nodes on network!
- Previous by thread: Re: Can't see other computers/nodes on network!
- Next by thread: Re: Can't see other computers/nodes on network!
- Index(es):