Jump to content

Slow connection with new server


Recommended Posts

Posted

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

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

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@discussions.microsoft.com> wrote in message

news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>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

Posted

Re: Slow connection with new server

 

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@discussions.microsoft.com> wrote in message

> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

> >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

>

>

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

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@discussions.microsoft.com> wrote in message

news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

> 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@discussions.microsoft.com> wrote in message

>> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>> >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

>>

>>

Posted

Re: Slow connection with new server

 

I reinstalled the driver. I changed the speed to auto negotiate 1000 gbs.

That had no effect.

 

I changed the cable from the punchdown block to the server. - That had no

effect.

 

I ran netstat -e several times.

 

Each time I got similar results:

 

Bytes: 1038075 Received / 989775 sent

Unicast Packets: 3075 / 3437

Non-unicast Packets: 107 / 36

Discards: 0 / 0

Errors: 0 / 0

Unknown Protocols: 4

 

I don't think that is a problem.

 

 

 

--

Chuck_N

 

 

"Mathieu CHATEAU" wrote:

> 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@discussions.microsoft.com> wrote in message

> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

> > 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@discussions.microsoft.com> wrote in message

> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

> >> >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

> >>

> >>

>

>

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

You mustn't change the speed without doing the same on the switch. Can your

switch be managed ?

Which driver and version are you using ?

 

You may experience network-related problems after you install Windows Server

2003 SP2 or the Scalable Networking Pack

http://support.microsoft.com/kb/936594

 

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>I reinstalled the driver. I changed the speed to auto negotiate 1000 gbs.

> That had no effect.

>

> I changed the cable from the punchdown block to the server. - That had no

> effect.

>

> I ran netstat -e several times.

>

> Each time I got similar results:

>

> Bytes: 1038075 Received / 989775 sent

> Unicast Packets: 3075 / 3437

> Non-unicast Packets: 107 / 36

> Discards: 0 / 0

> Errors: 0 / 0

> Unknown Protocols: 4

>

> I don't think that is a problem.

>

>

>

> --

> Chuck_N

>

>

> "Mathieu CHATEAU" wrote:

>

>> 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@discussions.microsoft.com> wrote in message

>> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>> > 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@discussions.microsoft.com> wrote in message

>> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>> >> >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

>> >>

>> >>

>>

>>

Posted

Re: Slow connection with new server

 

This is significant.

 

I was able to access the share from the original server with no problem.

The connection was as fast as expected.

 

This is not a cabling issue or a NIC issue. This must be related to

security. I don't think this is a DNS issue. All three computers are on the

same subnet.

 

My desktop has no problem assessing any other computer on the network. Only

the new server. And I do not think that problem showed up until I added SP2.

 

I have given myself full rights to the new share. Even when I try to assess

my list of computers on the network, there is a long delay - probably when it

tries to access the new server.

 

 

--

Chuck_N

 

 

"Mathieu CHATEAU" wrote:

> You mustn't change the speed without doing the same on the switch. Can your

> switch be managed ?

> Which driver and version are you using ?

>

> You may experience network-related problems after you install Windows Server

> 2003 SP2 or the Scalable Networking Pack

> http://support.microsoft.com/kb/936594

>

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

> news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

> >I reinstalled the driver. I changed the speed to auto negotiate 1000 gbs.

> > That had no effect.

> >

> > I changed the cable from the punchdown block to the server. - That had no

> > effect.

> >

> > I ran netstat -e several times.

> >

> > Each time I got similar results:

> >

> > Bytes: 1038075 Received / 989775 sent

> > Unicast Packets: 3075 / 3437

> > Non-unicast Packets: 107 / 36

> > Discards: 0 / 0

> > Errors: 0 / 0

> > Unknown Protocols: 4

> >

> > I don't think that is a problem.

> >

> >

> >

> > --

> > Chuck_N

> >

> >

> > "Mathieu CHATEAU" wrote:

> >

> >> 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@discussions.microsoft.com> wrote in message

> >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

> >> > 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@discussions.microsoft.com> wrote in message

> >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

> >> >> >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

> >> >>

> >> >>

> >>

> >>

>

>

Posted

Re: Slow connection with new server

 

The workstation Iam working from is the only workstation with Vista. All

other workstations can access the new server. Is there something new in

security that would be creating this probelm?

--

Chuck_N

 

 

"Chuck_N" wrote:

> This is significant.

>

> I was able to access the share from the original server with no problem.

> The connection was as fast as expected.

>

> This is not a cabling issue or a NIC issue. This must be related to

> security. I don't think this is a DNS issue. All three computers are on the

> same subnet.

>

> My desktop has no problem assessing any other computer on the network. Only

> the new server. And I do not think that problem showed up until I added SP2.

>

> I have given myself full rights to the new share. Even when I try to assess

> my list of computers on the network, there is a long delay - probably when it

> tries to access the new server.

>

>

> --

> Chuck_N

>

>

> "Mathieu CHATEAU" wrote:

>

> > You mustn't change the speed without doing the same on the switch. Can your

> > switch be managed ?

> > Which driver and version are you using ?

> >

> > You may experience network-related problems after you install Windows Server

> > 2003 SP2 or the Scalable Networking Pack

> > http://support.microsoft.com/kb/936594

> >

> >

> > --

> > Cordialement,

> > Mathieu CHATEAU

> > English blog: http://lordoftheping.blogspot.com

> > French blog: http://www.lotp.fr

> >

> >

> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

> > >I reinstalled the driver. I changed the speed to auto negotiate 1000 gbs.

> > > That had no effect.

> > >

> > > I changed the cable from the punchdown block to the server. - That had no

> > > effect.

> > >

> > > I ran netstat -e several times.

> > >

> > > Each time I got similar results:

> > >

> > > Bytes: 1038075 Received / 989775 sent

> > > Unicast Packets: 3075 / 3437

> > > Non-unicast Packets: 107 / 36

> > > Discards: 0 / 0

> > > Errors: 0 / 0

> > > Unknown Protocols: 4

> > >

> > > I don't think that is a problem.

> > >

> > >

> > >

> > > --

> > > Chuck_N

> > >

> > >

> > > "Mathieu CHATEAU" wrote:

> > >

> > >> 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@discussions.microsoft.com> wrote in message

> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

> > >> > 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@discussions.microsoft.com> wrote in message

> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

> > >> >> >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

> > >> >>

> > >> >>

> > >>

> > >>

> >

> >

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

indeed it may, is it large files ? Is the Vista clock in sync with the

domain (<5mn) ?

 

 

When you copy large files to or from earlier operating systems, the copy

operation may be slower than expected on some Windows Vista-based computers

http://support.microsoft.com/kb/932170/en-us

 

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

> The workstation Iam working from is the only workstation with Vista. All

> other workstations can access the new server. Is there something new in

> security that would be creating this probelm?

> --

> Chuck_N

>

>

> "Chuck_N" wrote:

>

>> This is significant.

>>

>> I was able to access the share from the original server with no problem.

>> The connection was as fast as expected.

>>

>> This is not a cabling issue or a NIC issue. This must be related to

>> security. I don't think this is a DNS issue. All three computers are on

>> the

>> same subnet.

>>

>> My desktop has no problem assessing any other computer on the network.

>> Only

>> the new server. And I do not think that problem showed up until I added

>> SP2.

>>

>> I have given myself full rights to the new share. Even when I try to

>> assess

>> my list of computers on the network, there is a long delay - probably

>> when it

>> tries to access the new server.

>>

>>

>> --

>> Chuck_N

>>

>>

>> "Mathieu CHATEAU" wrote:

>>

>> > You mustn't change the speed without doing the same on the switch. Can

>> > your

>> > switch be managed ?

>> > Which driver and version are you using ?

>> >

>> > You may experience network-related problems after you install Windows

>> > Server

>> > 2003 SP2 or the Scalable Networking Pack

>> > http://support.microsoft.com/kb/936594

>> >

>> >

>> > --

>> > Cordialement,

>> > Mathieu CHATEAU

>> > English blog: http://lordoftheping.blogspot.com

>> > French blog: http://www.lotp.fr

>> >

>> >

>> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>> > >I reinstalled the driver. I changed the speed to auto negotiate 1000

>> > >gbs.

>> > > That had no effect.

>> > >

>> > > I changed the cable from the punchdown block to the server. - That

>> > > had no

>> > > effect.

>> > >

>> > > I ran netstat -e several times.

>> > >

>> > > Each time I got similar results:

>> > >

>> > > Bytes: 1038075 Received / 989775 sent

>> > > Unicast Packets: 3075 / 3437

>> > > Non-unicast Packets: 107 / 36

>> > > Discards: 0 / 0

>> > > Errors: 0 / 0

>> > > Unknown Protocols: 4

>> > >

>> > > I don't think that is a problem.

>> > >

>> > >

>> > >

>> > > --

>> > > Chuck_N

>> > >

>> > >

>> > > "Mathieu CHATEAU" wrote:

>> > >

>> > >> 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@discussions.microsoft.com> wrote in message

>> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>> > >> > 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@discussions.microsoft.com> wrote in message

>> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>> > >> >> >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

>> > >> >>

>> > >> >>

>> > >>

>> > >>

>> >

>> >

Guest Chuck_N
Posted

Re: Slow connection with new server

 

I "solved" the problem with the following command on the Vista workstation:

 

netsh interface tcp set global autotuninglevel=disabled

 

I found that solution on another blog, but it came with no decription of

what it does.

 

You have talked about syncing with the domain, etc. I do not understand

what impact the above command has. Do you have any idea of where I can look

to correct the problem at the network level so that I can turn autotuing back

on?

 

Is there something in SP2 that would have caused the problem?

 

Thank you very much for your help.

 

 

 

 

 

--

Chuck_N

 

 

"Mathieu CHATEAU" wrote:

> indeed it may, is it large files ? Is the Vista clock in sync with the

> domain (<5mn) ?

>

>

> When you copy large files to or from earlier operating systems, the copy

> operation may be slower than expected on some Windows Vista-based computers

> http://support.microsoft.com/kb/932170/en-us

>

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

> > The workstation Iam working from is the only workstation with Vista. All

> > other workstations can access the new server. Is there something new in

> > security that would be creating this probelm?

> > --

> > Chuck_N

> >

> >

> > "Chuck_N" wrote:

> >

> >> This is significant.

> >>

> >> I was able to access the share from the original server with no problem.

> >> The connection was as fast as expected.

> >>

> >> This is not a cabling issue or a NIC issue. This must be related to

> >> security. I don't think this is a DNS issue. All three computers are on

> >> the

> >> same subnet.

> >>

> >> My desktop has no problem assessing any other computer on the network.

> >> Only

> >> the new server. And I do not think that problem showed up until I added

> >> SP2.

> >>

> >> I have given myself full rights to the new share. Even when I try to

> >> assess

> >> my list of computers on the network, there is a long delay - probably

> >> when it

> >> tries to access the new server.

> >>

> >>

> >> --

> >> Chuck_N

> >>

> >>

> >> "Mathieu CHATEAU" wrote:

> >>

> >> > You mustn't change the speed without doing the same on the switch. Can

> >> > your

> >> > switch be managed ?

> >> > Which driver and version are you using ?

> >> >

> >> > You may experience network-related problems after you install Windows

> >> > Server

> >> > 2003 SP2 or the Scalable Networking Pack

> >> > http://support.microsoft.com/kb/936594

> >> >

> >> >

> >> > --

> >> > Cordialement,

> >> > Mathieu CHATEAU

> >> > English blog: http://lordoftheping.blogspot.com

> >> > French blog: http://www.lotp.fr

> >> >

> >> >

> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

> >> > >I reinstalled the driver. I changed the speed to auto negotiate 1000

> >> > >gbs.

> >> > > That had no effect.

> >> > >

> >> > > I changed the cable from the punchdown block to the server. - That

> >> > > had no

> >> > > effect.

> >> > >

> >> > > I ran netstat -e several times.

> >> > >

> >> > > Each time I got similar results:

> >> > >

> >> > > Bytes: 1038075 Received / 989775 sent

> >> > > Unicast Packets: 3075 / 3437

> >> > > Non-unicast Packets: 107 / 36

> >> > > Discards: 0 / 0

> >> > > Errors: 0 / 0

> >> > > Unknown Protocols: 4

> >> > >

> >> > > I don't think that is a problem.

> >> > >

> >> > >

> >> > >

> >> > > --

> >> > > Chuck_N

> >> > >

> >> > >

> >> > > "Mathieu CHATEAU" wrote:

> >> > >

> >> > >> 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@discussions.microsoft.com> wrote in message

> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

> >> > >> > 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@discussions.microsoft.com> wrote in message

> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

> >> > >> >> >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

> >> > >> >>

> >> > >> >>

> >> > >>

> >> > >>

> >> >

> >> >

>

>

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

thanks for sharing your solution

 

more info about autotuning here:

 

http://www.microsoft.com/technet/technetmag/issues/2007/01/CableGuy/default.aspx?loc=en

Receive Window Auto-Tuning in Windows Vista

 

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

news:78AA7797-42FB-4064-A164-385DC019E369@microsoft.com...

>I "solved" the problem with the following command on the Vista workstation:

>

> netsh interface tcp set global autotuninglevel=disabled

>

> I found that solution on another blog, but it came with no decription of

> what it does.

>

> You have talked about syncing with the domain, etc. I do not understand

> what impact the above command has. Do you have any idea of where I can

> look

> to correct the problem at the network level so that I can turn autotuing

> back

> on?

>

> Is there something in SP2 that would have caused the problem?

>

> Thank you very much for your help.

>

>

>

>

>

> --

> Chuck_N

>

>

> "Mathieu CHATEAU" wrote:

>

>> indeed it may, is it large files ? Is the Vista clock in sync with the

>> domain (<5mn) ?

>>

>>

>> When you copy large files to or from earlier operating systems, the copy

>> operation may be slower than expected on some Windows Vista-based

>> computers

>> http://support.microsoft.com/kb/932170/en-us

>>

>>

>> --

>> Cordialement,

>> Mathieu CHATEAU

>> English blog: http://lordoftheping.blogspot.com

>> French blog: http://www.lotp.fr

>>

>>

>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

>> > The workstation Iam working from is the only workstation with Vista.

>> > All

>> > other workstations can access the new server. Is there something new

>> > in

>> > security that would be creating this probelm?

>> > --

>> > Chuck_N

>> >

>> >

>> > "Chuck_N" wrote:

>> >

>> >> This is significant.

>> >>

>> >> I was able to access the share from the original server with no

>> >> problem.

>> >> The connection was as fast as expected.

>> >>

>> >> This is not a cabling issue or a NIC issue. This must be related to

>> >> security. I don't think this is a DNS issue. All three computers are

>> >> on

>> >> the

>> >> same subnet.

>> >>

>> >> My desktop has no problem assessing any other computer on the network.

>> >> Only

>> >> the new server. And I do not think that problem showed up until I

>> >> added

>> >> SP2.

>> >>

>> >> I have given myself full rights to the new share. Even when I try to

>> >> assess

>> >> my list of computers on the network, there is a long delay - probably

>> >> when it

>> >> tries to access the new server.

>> >>

>> >>

>> >> --

>> >> Chuck_N

>> >>

>> >>

>> >> "Mathieu CHATEAU" wrote:

>> >>

>> >> > You mustn't change the speed without doing the same on the switch.

>> >> > Can

>> >> > your

>> >> > switch be managed ?

>> >> > Which driver and version are you using ?

>> >> >

>> >> > You may experience network-related problems after you install

>> >> > Windows

>> >> > Server

>> >> > 2003 SP2 or the Scalable Networking Pack

>> >> > http://support.microsoft.com/kb/936594

>> >> >

>> >> >

>> >> > --

>> >> > Cordialement,

>> >> > Mathieu CHATEAU

>> >> > English blog: http://lordoftheping.blogspot.com

>> >> > French blog: http://www.lotp.fr

>> >> >

>> >> >

>> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>> >> > >I reinstalled the driver. I changed the speed to auto negotiate

>> >> > >1000

>> >> > >gbs.

>> >> > > That had no effect.

>> >> > >

>> >> > > I changed the cable from the punchdown block to the server. - That

>> >> > > had no

>> >> > > effect.

>> >> > >

>> >> > > I ran netstat -e several times.

>> >> > >

>> >> > > Each time I got similar results:

>> >> > >

>> >> > > Bytes: 1038075 Received / 989775 sent

>> >> > > Unicast Packets: 3075 / 3437

>> >> > > Non-unicast Packets: 107 / 36

>> >> > > Discards: 0 / 0

>> >> > > Errors: 0 / 0

>> >> > > Unknown Protocols: 4

>> >> > >

>> >> > > I don't think that is a problem.

>> >> > >

>> >> > >

>> >> > >

>> >> > > --

>> >> > > Chuck_N

>> >> > >

>> >> > >

>> >> > > "Mathieu CHATEAU" wrote:

>> >> > >

>> >> > >> 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@discussions.microsoft.com> wrote in message

>> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>> >> > >> > 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@discussions.microsoft.com> wrote in message

>> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>> >> > >> >> >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

>> >> > >> >>

>> >> > >> >>

>> >> > >>

>> >> > >>

>> >> >

>> >> >

>>

>>

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

some really better clues:

 

Network connectivity may fail when you try to use Windows Vista behind a

firewall device

http://support.microsoft.com/kb/934430/en-us

 

Can you try te workaround ?

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

news:78AA7797-42FB-4064-A164-385DC019E369@microsoft.com...

>I "solved" the problem with the following command on the Vista workstation:

>

> netsh interface tcp set global autotuninglevel=disabled

>

> I found that solution on another blog, but it came with no decription of

> what it does.

>

> You have talked about syncing with the domain, etc. I do not understand

> what impact the above command has. Do you have any idea of where I can

> look

> to correct the problem at the network level so that I can turn autotuing

> back

> on?

>

> Is there something in SP2 that would have caused the problem?

>

> Thank you very much for your help.

>

>

>

>

>

> --

> Chuck_N

>

>

> "Mathieu CHATEAU" wrote:

>

>> indeed it may, is it large files ? Is the Vista clock in sync with the

>> domain (<5mn) ?

>>

>>

>> When you copy large files to or from earlier operating systems, the copy

>> operation may be slower than expected on some Windows Vista-based

>> computers

>> http://support.microsoft.com/kb/932170/en-us

>>

>>

>> --

>> Cordialement,

>> Mathieu CHATEAU

>> English blog: http://lordoftheping.blogspot.com

>> French blog: http://www.lotp.fr

>>

>>

>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

>> > The workstation Iam working from is the only workstation with Vista.

>> > All

>> > other workstations can access the new server. Is there something new

>> > in

>> > security that would be creating this probelm?

>> > --

>> > Chuck_N

>> >

>> >

>> > "Chuck_N" wrote:

>> >

>> >> This is significant.

>> >>

>> >> I was able to access the share from the original server with no

>> >> problem.

>> >> The connection was as fast as expected.

>> >>

>> >> This is not a cabling issue or a NIC issue. This must be related to

>> >> security. I don't think this is a DNS issue. All three computers are

>> >> on

>> >> the

>> >> same subnet.

>> >>

>> >> My desktop has no problem assessing any other computer on the network.

>> >> Only

>> >> the new server. And I do not think that problem showed up until I

>> >> added

>> >> SP2.

>> >>

>> >> I have given myself full rights to the new share. Even when I try to

>> >> assess

>> >> my list of computers on the network, there is a long delay - probably

>> >> when it

>> >> tries to access the new server.

>> >>

>> >>

>> >> --

>> >> Chuck_N

>> >>

>> >>

>> >> "Mathieu CHATEAU" wrote:

>> >>

>> >> > You mustn't change the speed without doing the same on the switch.

>> >> > Can

>> >> > your

>> >> > switch be managed ?

>> >> > Which driver and version are you using ?

>> >> >

>> >> > You may experience network-related problems after you install

>> >> > Windows

>> >> > Server

>> >> > 2003 SP2 or the Scalable Networking Pack

>> >> > http://support.microsoft.com/kb/936594

>> >> >

>> >> >

>> >> > --

>> >> > Cordialement,

>> >> > Mathieu CHATEAU

>> >> > English blog: http://lordoftheping.blogspot.com

>> >> > French blog: http://www.lotp.fr

>> >> >

>> >> >

>> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>> >> > >I reinstalled the driver. I changed the speed to auto negotiate

>> >> > >1000

>> >> > >gbs.

>> >> > > That had no effect.

>> >> > >

>> >> > > I changed the cable from the punchdown block to the server. - That

>> >> > > had no

>> >> > > effect.

>> >> > >

>> >> > > I ran netstat -e several times.

>> >> > >

>> >> > > Each time I got similar results:

>> >> > >

>> >> > > Bytes: 1038075 Received / 989775 sent

>> >> > > Unicast Packets: 3075 / 3437

>> >> > > Non-unicast Packets: 107 / 36

>> >> > > Discards: 0 / 0

>> >> > > Errors: 0 / 0

>> >> > > Unknown Protocols: 4

>> >> > >

>> >> > > I don't think that is a problem.

>> >> > >

>> >> > >

>> >> > >

>> >> > > --

>> >> > > Chuck_N

>> >> > >

>> >> > >

>> >> > > "Mathieu CHATEAU" wrote:

>> >> > >

>> >> > >> 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@discussions.microsoft.com> wrote in message

>> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>> >> > >> > 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@discussions.microsoft.com> wrote in message

>> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>> >> > >> >> >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

>> >> > >> >>

>> >> > >> >>

>> >> > >>

>> >> > >>

>> >> >

>> >> >

>>

>>

  • 4 weeks later...
Posted

Re: Slow connection with new server

 

Sorry for not getting back to you sooner.

 

The problem occurs across our LAN. Therefore , there is no firewall device

between the connections.

In this case, the two Vista workstation connections to the server through a

switch only.

 

 

"Mathieu CHATEAU" <gollum123@free.fr> wrote in message

news:uf%23dc%23FBIHA.4752@TK2MSFTNGP04.phx.gbl...

> some really better clues:

>

> Network connectivity may fail when you try to use Windows Vista behind a

> firewall device

> http://support.microsoft.com/kb/934430/en-us

>

> Can you try te workaround ?

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

> news:78AA7797-42FB-4064-A164-385DC019E369@microsoft.com...

>>I "solved" the problem with the following command on the Vista

>>workstation:

>>

>> netsh interface tcp set global autotuninglevel=disabled

>>

>> I found that solution on another blog, but it came with no decription of

>> what it does.

>>

>> You have talked about syncing with the domain, etc. I do not understand

>> what impact the above command has. Do you have any idea of where I can

>> look

>> to correct the problem at the network level so that I can turn autotuing

>> back

>> on?

>>

>> Is there something in SP2 that would have caused the problem?

>>

>> Thank you very much for your help.

>>

>>

>>

>>

>>

>> --

>> Chuck_N

>>

>>

>> "Mathieu CHATEAU" wrote:

>>

>>> indeed it may, is it large files ? Is the Vista clock in sync with the

>>> domain (<5mn) ?

>>>

>>>

>>> When you copy large files to or from earlier operating systems, the copy

>>> operation may be slower than expected on some Windows Vista-based

>>> computers

>>> http://support.microsoft.com/kb/932170/en-us

>>>

>>>

>>> --

>>> Cordialement,

>>> Mathieu CHATEAU

>>> English blog: http://lordoftheping.blogspot.com

>>> French blog: http://www.lotp.fr

>>>

>>>

>>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

>>> > The workstation Iam working from is the only workstation with Vista.

>>> > All

>>> > other workstations can access the new server. Is there something new

>>> > in

>>> > security that would be creating this probelm?

>>> > --

>>> > Chuck_N

>>> >

>>> >

>>> > "Chuck_N" wrote:

>>> >

>>> >> This is significant.

>>> >>

>>> >> I was able to access the share from the original server with no

>>> >> problem.

>>> >> The connection was as fast as expected.

>>> >>

>>> >> This is not a cabling issue or a NIC issue. This must be related to

>>> >> security. I don't think this is a DNS issue. All three computers

>>> >> are on

>>> >> the

>>> >> same subnet.

>>> >>

>>> >> My desktop has no problem assessing any other computer on the

>>> >> network.

>>> >> Only

>>> >> the new server. And I do not think that problem showed up until I

>>> >> added

>>> >> SP2.

>>> >>

>>> >> I have given myself full rights to the new share. Even when I try to

>>> >> assess

>>> >> my list of computers on the network, there is a long delay - probably

>>> >> when it

>>> >> tries to access the new server.

>>> >>

>>> >>

>>> >> --

>>> >> Chuck_N

>>> >>

>>> >>

>>> >> "Mathieu CHATEAU" wrote:

>>> >>

>>> >> > You mustn't change the speed without doing the same on the switch.

>>> >> > Can

>>> >> > your

>>> >> > switch be managed ?

>>> >> > Which driver and version are you using ?

>>> >> >

>>> >> > You may experience network-related problems after you install

>>> >> > Windows

>>> >> > Server

>>> >> > 2003 SP2 or the Scalable Networking Pack

>>> >> > http://support.microsoft.com/kb/936594

>>> >> >

>>> >> >

>>> >> > --

>>> >> > Cordialement,

>>> >> > Mathieu CHATEAU

>>> >> > English blog: http://lordoftheping.blogspot.com

>>> >> > French blog: http://www.lotp.fr

>>> >> >

>>> >> >

>>> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>>> >> > >I reinstalled the driver. I changed the speed to auto negotiate

>>> >> > >1000

>>> >> > >gbs.

>>> >> > > That had no effect.

>>> >> > >

>>> >> > > I changed the cable from the punchdown block to the server. -

>>> >> > > That

>>> >> > > had no

>>> >> > > effect.

>>> >> > >

>>> >> > > I ran netstat -e several times.

>>> >> > >

>>> >> > > Each time I got similar results:

>>> >> > >

>>> >> > > Bytes: 1038075 Received / 989775 sent

>>> >> > > Unicast Packets: 3075 / 3437

>>> >> > > Non-unicast Packets: 107 / 36

>>> >> > > Discards: 0 / 0

>>> >> > > Errors: 0 / 0

>>> >> > > Unknown Protocols: 4

>>> >> > >

>>> >> > > I don't think that is a problem.

>>> >> > >

>>> >> > >

>>> >> > >

>>> >> > > --

>>> >> > > Chuck_N

>>> >> > >

>>> >> > >

>>> >> > > "Mathieu CHATEAU" wrote:

>>> >> > >

>>> >> > >> 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@discussions.microsoft.com> wrote in message

>>> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>>> >> > >> > 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@discussions.microsoft.com> wrote in message

>>> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>>> >> > >> >> >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

>>> >> > >> >>

>>> >> > >> >>

>>> >> > >>

>>> >> > >>

>>> >> >

>>> >> >

>>>

>>>

>

>

Guest Mathieu CHATEAU
Posted

Re: Slow connection with new server

 

so except the fact that you needed to tweak autotuning, it works correctly ?

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"ChuckN" <Chuck@newmanArchitecture.com> wrote in message

news:1C3E672D-FCC4-42B2-BC32-87B50FA9E2C9@microsoft.com...

> Sorry for not getting back to you sooner.

>

> The problem occurs across our LAN. Therefore , there is no firewall

> device between the connections.

> In this case, the two Vista workstation connections to the server through

> a switch only.

>

>

> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message

> news:uf%23dc%23FBIHA.4752@TK2MSFTNGP04.phx.gbl...

>> some really better clues:

>>

>> Network connectivity may fail when you try to use Windows Vista behind a

>> firewall device

>> http://support.microsoft.com/kb/934430/en-us

>>

>> Can you try te workaround ?

>>

>> --

>> Cordialement,

>> Mathieu CHATEAU

>> English blog: http://lordoftheping.blogspot.com

>> French blog: http://www.lotp.fr

>>

>>

>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>> news:78AA7797-42FB-4064-A164-385DC019E369@microsoft.com...

>>>I "solved" the problem with the following command on the Vista

>>>workstation:

>>>

>>> netsh interface tcp set global autotuninglevel=disabled

>>>

>>> I found that solution on another blog, but it came with no decription of

>>> what it does.

>>>

>>> You have talked about syncing with the domain, etc. I do not understand

>>> what impact the above command has. Do you have any idea of where I can

>>> look

>>> to correct the problem at the network level so that I can turn autotuing

>>> back

>>> on?

>>>

>>> Is there something in SP2 that would have caused the problem?

>>>

>>> Thank you very much for your help.

>>>

>>>

>>>

>>>

>>>

>>> --

>>> Chuck_N

>>>

>>>

>>> "Mathieu CHATEAU" wrote:

>>>

>>>> indeed it may, is it large files ? Is the Vista clock in sync with the

>>>> domain (<5mn) ?

>>>>

>>>>

>>>> When you copy large files to or from earlier operating systems, the

>>>> copy

>>>> operation may be slower than expected on some Windows Vista-based

>>>> computers

>>>> http://support.microsoft.com/kb/932170/en-us

>>>>

>>>>

>>>> --

>>>> Cordialement,

>>>> Mathieu CHATEAU

>>>> English blog: http://lordoftheping.blogspot.com

>>>> French blog: http://www.lotp.fr

>>>>

>>>>

>>>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>>> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

>>>> > The workstation Iam working from is the only workstation with Vista.

>>>> > All

>>>> > other workstations can access the new server. Is there something new

>>>> > in

>>>> > security that would be creating this probelm?

>>>> > --

>>>> > Chuck_N

>>>> >

>>>> >

>>>> > "Chuck_N" wrote:

>>>> >

>>>> >> This is significant.

>>>> >>

>>>> >> I was able to access the share from the original server with no

>>>> >> problem.

>>>> >> The connection was as fast as expected.

>>>> >>

>>>> >> This is not a cabling issue or a NIC issue. This must be related to

>>>> >> security. I don't think this is a DNS issue. All three computers

>>>> >> are on

>>>> >> the

>>>> >> same subnet.

>>>> >>

>>>> >> My desktop has no problem assessing any other computer on the

>>>> >> network.

>>>> >> Only

>>>> >> the new server. And I do not think that problem showed up until I

>>>> >> added

>>>> >> SP2.

>>>> >>

>>>> >> I have given myself full rights to the new share. Even when I try

>>>> >> to

>>>> >> assess

>>>> >> my list of computers on the network, there is a long delay -

>>>> >> probably

>>>> >> when it

>>>> >> tries to access the new server.

>>>> >>

>>>> >>

>>>> >> --

>>>> >> Chuck_N

>>>> >>

>>>> >>

>>>> >> "Mathieu CHATEAU" wrote:

>>>> >>

>>>> >> > You mustn't change the speed without doing the same on the switch.

>>>> >> > Can

>>>> >> > your

>>>> >> > switch be managed ?

>>>> >> > Which driver and version are you using ?

>>>> >> >

>>>> >> > You may experience network-related problems after you install

>>>> >> > Windows

>>>> >> > Server

>>>> >> > 2003 SP2 or the Scalable Networking Pack

>>>> >> > http://support.microsoft.com/kb/936594

>>>> >> >

>>>> >> >

>>>> >> > --

>>>> >> > Cordialement,

>>>> >> > Mathieu CHATEAU

>>>> >> > English blog: http://lordoftheping.blogspot.com

>>>> >> > French blog: http://www.lotp.fr

>>>> >> >

>>>> >> >

>>>> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>>> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>>>> >> > >I reinstalled the driver. I changed the speed to auto negotiate

>>>> >> > >1000

>>>> >> > >gbs.

>>>> >> > > That had no effect.

>>>> >> > >

>>>> >> > > I changed the cable from the punchdown block to the server. -

>>>> >> > > That

>>>> >> > > had no

>>>> >> > > effect.

>>>> >> > >

>>>> >> > > I ran netstat -e several times.

>>>> >> > >

>>>> >> > > Each time I got similar results:

>>>> >> > >

>>>> >> > > Bytes: 1038075 Received / 989775 sent

>>>> >> > > Unicast Packets: 3075 / 3437

>>>> >> > > Non-unicast Packets: 107 / 36

>>>> >> > > Discards: 0 / 0

>>>> >> > > Errors: 0 / 0

>>>> >> > > Unknown Protocols: 4

>>>> >> > >

>>>> >> > > I don't think that is a problem.

>>>> >> > >

>>>> >> > >

>>>> >> > >

>>>> >> > > --

>>>> >> > > Chuck_N

>>>> >> > >

>>>> >> > >

>>>> >> > > "Mathieu CHATEAU" wrote:

>>>> >> > >

>>>> >> > >> 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@discussions.microsoft.com> wrote in message

>>>> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>>>> >> > >> > 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@discussions.microsoft.com> wrote in

>>>> >> > >> >> message

>>>> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>>>> >> > >> >> >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

>>>> >> > >> >>

>>>> >> > >> >>

>>>> >> > >>

>>>> >> > >>

>>>> >> >

>>>> >> >

>>>>

>>>>

>>

>>

>

Posted

Re: Slow connection with new server

 

Yes

 

"Mathieu CHATEAU" <gollum123@free.fr> wrote in message

news:e2ReTR1FIHA.936@TK2MSFTNGP06.phx.gbl...

> so except the fact that you needed to tweak autotuning, it works correctly

> ?

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "ChuckN" <Chuck@newmanArchitecture.com> wrote in message

> news:1C3E672D-FCC4-42B2-BC32-87B50FA9E2C9@microsoft.com...

>> Sorry for not getting back to you sooner.

>>

>> The problem occurs across our LAN. Therefore , there is no firewall

>> device between the connections.

>> In this case, the two Vista workstation connections to the server through

>> a switch only.

>>

>>

>> "Mathieu CHATEAU" <gollum123@free.fr> wrote in message

>> news:uf%23dc%23FBIHA.4752@TK2MSFTNGP04.phx.gbl...

>>> some really better clues:

>>>

>>> Network connectivity may fail when you try to use Windows Vista behind a

>>> firewall device

>>> http://support.microsoft.com/kb/934430/en-us

>>>

>>> Can you try te workaround ?

>>>

>>> --

>>> Cordialement,

>>> Mathieu CHATEAU

>>> English blog: http://lordoftheping.blogspot.com

>>> French blog: http://www.lotp.fr

>>>

>>>

>>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>> news:78AA7797-42FB-4064-A164-385DC019E369@microsoft.com...

>>>>I "solved" the problem with the following command on the Vista

>>>>workstation:

>>>>

>>>> netsh interface tcp set global autotuninglevel=disabled

>>>>

>>>> I found that solution on another blog, but it came with no decription

>>>> of

>>>> what it does.

>>>>

>>>> You have talked about syncing with the domain, etc. I do not

>>>> understand

>>>> what impact the above command has. Do you have any idea of where I can

>>>> look

>>>> to correct the problem at the network level so that I can turn

>>>> autotuing back

>>>> on?

>>>>

>>>> Is there something in SP2 that would have caused the problem?

>>>>

>>>> Thank you very much for your help.

>>>>

>>>>

>>>>

>>>>

>>>>

>>>> --

>>>> Chuck_N

>>>>

>>>>

>>>> "Mathieu CHATEAU" wrote:

>>>>

>>>>> indeed it may, is it large files ? Is the Vista clock in sync with the

>>>>> domain (<5mn) ?

>>>>>

>>>>>

>>>>> When you copy large files to or from earlier operating systems, the

>>>>> copy

>>>>> operation may be slower than expected on some Windows Vista-based

>>>>> computers

>>>>> http://support.microsoft.com/kb/932170/en-us

>>>>>

>>>>>

>>>>> --

>>>>> Cordialement,

>>>>> Mathieu CHATEAU

>>>>> English blog: http://lordoftheping.blogspot.com

>>>>> French blog: http://www.lotp.fr

>>>>>

>>>>>

>>>>> "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>>>> news:39CBDD8E-67A6-499A-8C0E-73D3F7C332E4@microsoft.com...

>>>>> > The workstation Iam working from is the only workstation with Vista.

>>>>> > All

>>>>> > other workstations can access the new server. Is there something

>>>>> > new in

>>>>> > security that would be creating this probelm?

>>>>> > --

>>>>> > Chuck_N

>>>>> >

>>>>> >

>>>>> > "Chuck_N" wrote:

>>>>> >

>>>>> >> This is significant.

>>>>> >>

>>>>> >> I was able to access the share from the original server with no

>>>>> >> problem.

>>>>> >> The connection was as fast as expected.

>>>>> >>

>>>>> >> This is not a cabling issue or a NIC issue. This must be related

>>>>> >> to

>>>>> >> security. I don't think this is a DNS issue. All three computers

>>>>> >> are on

>>>>> >> the

>>>>> >> same subnet.

>>>>> >>

>>>>> >> My desktop has no problem assessing any other computer on the

>>>>> >> network.

>>>>> >> Only

>>>>> >> the new server. And I do not think that problem showed up until I

>>>>> >> added

>>>>> >> SP2.

>>>>> >>

>>>>> >> I have given myself full rights to the new share. Even when I try

>>>>> >> to

>>>>> >> assess

>>>>> >> my list of computers on the network, there is a long delay -

>>>>> >> probably

>>>>> >> when it

>>>>> >> tries to access the new server.

>>>>> >>

>>>>> >>

>>>>> >> --

>>>>> >> Chuck_N

>>>>> >>

>>>>> >>

>>>>> >> "Mathieu CHATEAU" wrote:

>>>>> >>

>>>>> >> > You mustn't change the speed without doing the same on the

>>>>> >> > switch. Can

>>>>> >> > your

>>>>> >> > switch be managed ?

>>>>> >> > Which driver and version are you using ?

>>>>> >> >

>>>>> >> > You may experience network-related problems after you install

>>>>> >> > Windows

>>>>> >> > Server

>>>>> >> > 2003 SP2 or the Scalable Networking Pack

>>>>> >> > http://support.microsoft.com/kb/936594

>>>>> >> >

>>>>> >> >

>>>>> >> > --

>>>>> >> > Cordialement,

>>>>> >> > Mathieu CHATEAU

>>>>> >> > English blog: http://lordoftheping.blogspot.com

>>>>> >> > French blog: http://www.lotp.fr

>>>>> >> >

>>>>> >> >

>>>>> >> > "Chuck_N" <ChuckN@discussions.microsoft.com> wrote in message

>>>>> >> > news:7F1F7037-F5A4-4FC8-A05C-B4C072801592@microsoft.com...

>>>>> >> > >I reinstalled the driver. I changed the speed to auto negotiate

>>>>> >> > >1000

>>>>> >> > >gbs.

>>>>> >> > > That had no effect.

>>>>> >> > >

>>>>> >> > > I changed the cable from the punchdown block to the server. -

>>>>> >> > > That

>>>>> >> > > had no

>>>>> >> > > effect.

>>>>> >> > >

>>>>> >> > > I ran netstat -e several times.

>>>>> >> > >

>>>>> >> > > Each time I got similar results:

>>>>> >> > >

>>>>> >> > > Bytes: 1038075 Received / 989775 sent

>>>>> >> > > Unicast Packets: 3075 / 3437

>>>>> >> > > Non-unicast Packets: 107 / 36

>>>>> >> > > Discards: 0 / 0

>>>>> >> > > Errors: 0 / 0

>>>>> >> > > Unknown Protocols: 4

>>>>> >> > >

>>>>> >> > > I don't think that is a problem.

>>>>> >> > >

>>>>> >> > >

>>>>> >> > >

>>>>> >> > > --

>>>>> >> > > Chuck_N

>>>>> >> > >

>>>>> >> > >

>>>>> >> > > "Mathieu CHATEAU" wrote:

>>>>> >> > >

>>>>> >> > >> 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@discussions.microsoft.com> wrote in message

>>>>> >> > >> news:6C6C0D86-D484-43D4-B19D-F8B827BB8C4E@microsoft.com...

>>>>> >> > >> > 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@discussions.microsoft.com> wrote in

>>>>> >> > >> >> message

>>>>> >> > >> >> news:09DF7E7B-3B7B-479E-92B3-04DD3DE9CECB@microsoft.com...

>>>>> >> > >> >> >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

>>>>> >> > >> >>

>>>>> >> > >> >>

>>>>> >> > >>

>>>>> >> > >>

>>>>> >> >

>>>>> >> >

>>>>>

>>>>>

>>>

>>>

>>

>

>

×
×
  • Create New...