Re: Slow connection with new server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Also check that the network card and switch are both auto or both forced in speed and duplex

You may also check for errors (damaged cable...):
netstat -e


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Chuck_N" <ChuckN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@xxxxxxxxxxxxxxxx
Thank you Mathieu. I think it was after I added SP2 that I recognized the
problem.

It is a new Gateway server. I am using the on-board GB NIC. I will check
on the NIC driver to make sure they are up to date.
--
Chuck_N


"Mathieu CHATEAU" wrote:

Hello,

Service pack 2 add many things on the network core. Do you have the latest
drivers ? Is it a Dell with Broadcom network card?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Chuck_N" <ChuckN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@xxxxxxxxxxxxxxxx
>I am preparing a new server to replace our 5 year old server running >Wndows
> Server 2003 - Enterprise edition. That server has been upgraded > through
> several versions of servers probably back to an early version of NT. As > a
> result, it retains the old directory structure.
>
> We only have 20 workstations that are served by the server. It handles
> everthing for us including file sharing, web site, FTP, Exchange Server
> 2003,
> enterprise virus protection, and probably a few more tasks. It is
> obviously
> the PDC. This 5 year old server is running great and has had no > problems.
>
> Because of its age, we are replacing it with a new server, and are
> planning
> the same configuration with new equipment. This time, I decided to > create
> the new server from scratch. This will correct the directory structure > to
> the current default structure for Server 2003.
>
> I installed Server 2003 on the new server including SP 1 and SP2.
> Somewhere
> in adding the updates, I found that access to the new server became > very
> slow. It is not slow from the server to the workstation - only from > the
> workstation to the server. Anything I do from a workstation, such as
> checking Event Viewer, initiating a Remote Desktop Connection, or
> accessing a
> drive share takes a very long time.
>
> I have added AD and DNS to the second server with no affect. I receive > no
> error messages on either server. I suspect the problem has something > to
> do
> with security or DNS, but I am not getting an error messages. WINS, > AD,
> and
> DNS replication appear to be working without errors.
>
>
> The original server continues to work fine - with no problems.
>
> Any idea of what the problem could be on the new server?
>
> Thanks
> -- > Chuck_N



.

Relevant Pages

  • Re: AD Newbie Questions
    ... Remember that though DNS and AD are ... You can copy the profile over, either doing a straight copy (get the ... > I've reviewed a few books on Server2K3, but before I> promote my server to a Domain Controller, there are still a few specifics> where I'd appreciate some guidance. ... I would install Studio.NET on the XP Pro workstation. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Basic Active Directory Questions
    ... Primary DC DNS service was disabled. ... Seondary DNS server has problem address with this DC ... Point your Member server and workstation to '10.81.20.19' as their prefered ...
    (microsoft.public.windows.server.active_directory)
  • Re: XP Client Connection Problem
    ... I'm not the most knowledgable about DNS but I ... > now consists of a single server and single workstation. ... > The server is Windows 2003 and is set up for DNS, ... This first client is also an XP ...
    (microsoft.public.windows.server.dns)
  • Re: Need help please, Having trouble finding/adding users for purpose of granting permissions or add
    ... the XP Pro computer to see if it reports any errors such as dns, dclist, ... server in the preferred dns server list of tcp/ip properties an shown via ... I also setup a simulation in my lab of an XP Pro ... > workstation and a single W2K Server running as the Domain controller. ...
    (microsoft.public.win2000.security)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... The workstation gets its networking information from DHCP that, in turn, ... the DNS has Enable Forwarders and the ... I don't believe the problem to be at the server end though. ... security settings) I messed with and that policy has since been removed. ...
    (microsoft.public.win2000.security)