Re: Windows 2003 Question - doing some part time work for a friend
- From: DefenderD90 <DefenderD90@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Feb 2007 13:08:22 -0800
Thanks for the input, will reply later. Good info.
"Danny Sanders" wrote:
The deal is, they don't even use any features of the.
server, their just essentially using the server as a file share, which can
be
done with a cheap box, so in my mind, it's a waste of thousands of
dollars.
But, it would provide expandability in the future. It's setup as a domain
controller(AD), and a "file server", but when everyone logs on, they don't
sign on to "local machine name" they select the domain.
Perfectly normal on an AD domain. Users don't usually log into the local
machine.
But when they log
on, it takes about 2-3 minutes, sometimes longer then they finally get in.
It's a 768k/768k 3/4th T1, running behind a BEFSX41, configured to use 1
static of a /29. ISP has dhcp turned off, as the linksys is now the dhcp
server.
Sounds like DNS is set up wrong. Your clients may be pointed to your ISP's
DNS server, which will cause long log in times.
AD must have a DNS server set up for the AD domain. All AD clients must
point to the AD DNS server only. For Internet access set up the AD DNS
server to forward requests and list your ISP's DNS servers as the
forwarders. This is the ONLY place on an AD domain your ISP's DNS servers
should be listed. If it's on a client as the preferred DNS server it will
cause long log in times like you are seeing. If it is listed as alternate it
will cause a whole other set of problems.
See:
http://support.microsoft.com/kb/814591/en-us
http://support.microsoft.com/kb/825036/en-us
http://support.microsoft.com/kb/323380/en-us
It seems upon login, the individuals seem to idle/hang on, when the
computer
is "applying computer settings", and/or "applying profile settings".
Does this sound like a glitched AD configuration, roaming profiles.
Sounds like someone has the clients using your ISP's DNS server.
But when I also goto each computer, and right click "my computer", and
left
click "properties", and goto "computer name" tab, each machine is listed
as :
Machinename.local
what is going on with ".local" ?
That is fine. AD domains should never have a single label name. The .local
is just a way to comply with the suggested AD naming convention and not
"step" on someone's registered domain name.
See:
http://support.microsoft.com/kb/300684/en-us
hth
DDS
"DefenderD90" <DefenderD90@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2CAEBF1B-12B8-49DC-90E6-6BB3C884C9D6@xxxxxxxxxxxxxxxx
They have Windows 2003 standard, it's a Poweredge 2950 Tower, not a 2U
rackmounted server. 2Gigs ram.
All boxes in the network are windows XP. I came on, after they released
the old "admin". The deal is, they don't even use any features of the
server, their just essentially using the server as a file share, which can
be
done with a cheap box, so in my mind, it's a waste of thousands of
dollars.
But, it would provide expandability in the future. It's setup as a domain
controller(AD), and a "file server", but when everyone logs on, they don't
sign on to "local machine name" they select the domain. But when they log
on, it takes about 2-3 minutes, sometimes longer then they finally get in.
It's a 768k/768k 3/4th T1, running behind a BEFSX41, configured to use 1
static of a /29. ISP has dhcp turned off, as the linksys is now the dhcp
server.
It seems upon login, the individuals seem to idle/hang on, when the
computer
is "applying computer settings", and/or "applying profile settings".
Does this sound like a glitched AD configuration, roaming profiles.
Also, when I run an angry IP scanner and scan the subnet given by the
linksys, the server shows up as "machinename.local", but other computers
show
up just as machine name. Due to me configuring wins, i have the benefit
of
the machine names.
But when I also goto each computer, and right click "my computer", and
left
click "properties", and goto "computer name" tab, each machine is listed
as :
Machinename.local
what is going on with ".local" ?
They aren't hosting any services internally. Any ideas/thoughts would be
greatly appreciated. What would be the first steps into getting a
properly
configured active directory, because essentially they sign onto the
"domain"
but I can't tell if their getting GP, and if the network really isn't a
network, i8t's just a workgroup with a "shared folder" acting as a file
share.
- References:
- Re: Windows 2003 Question - doing some part time work for a friend
- From: Danny Sanders
- Re: Windows 2003 Question - doing some part time work for a friend
- Prev by Date: Old VB6 ActiveX Exe registered on Windows 2003 Server does not show both Objects in ActiveX Exe
- Next by Date: Re: Server Rebooting
- Previous by thread: Re: Windows 2003 Question - doing some part time work for a friend
- Next by thread: Re: Windows 2003 Question - doing some part time work for a friend
- Index(es):
Relevant Pages
|
