New Windows Server file access is SLOW

I have just installed a new Windows 2003 R2 Enterprise X64 server and have
configured it as a file server. I am in the process of migrating from a
Novell file server to this Windows files server. I have moved 1 of the
volumes over and am having everyone test speed, reliability, etc. I am
mapping the drives via a VBS login script and that seems to be working.

My first issue is that the first time the drives are accessed, it takes
15-30 seconds (longer on our few Vista machines) for the drive to come up or
the application on the drive to launch, etc. After that, access is
acceptable. Not as fast as the Novell server but I kinda figured it wouldn't
be anyway. Our next issue is that after a certain amount of time of
inactivity it again takes 15-30 seconds to access anything on this drive.
It's as if it is 'losing' the connection and has to re-establish it (just an
observation, not a diagnosis.)

I have turned off all unnecessary services and disabled oplocks. I also
have dual Intel NICs that are teamed.

I'm not sure what else to do at this time to get rid of these delays. Anyone
have any ideas?

Is the server a member of a domain?



DDS

"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have just installed a new Windows 2003 R2 Enterprise X64 server and have
>configured it as a file server. I am in the process of migrating from a
>Novell file server to this Windows files server. I have moved 1 of the
>volumes over and am having everyone test speed, reliability, etc. I am
>mapping the drives via a VBS login script and that seems to be working.
>
> My first issue is that the first time the drives are accessed, it takes
> 15-30 seconds (longer on our few Vista machines) for the drive to come up
> or the application on the drive to launch, etc. After that, access is
> acceptable. Not as fast as the Novell server but I kinda figured it
> wouldn't be anyway. Our next issue is that after a certain amount of time
> of inactivity it again takes 15-30 seconds to access anything on this
> drive. It's as if it is 'losing' the connection and has to re-establish it
> (just an observation, not a diagnosis.)
>
> I have turned off all unnecessary services and disabled oplocks. I also
> have dual Intel NICs that are teamed.
>
> I'm not sure what else to do at this time to get rid of these delays.
> Anyone have any ideas?
>

Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
besides thier normal DC jobs. I am using the \\servername\sharename to map
them in a logon script.

"Danny Sanders" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Is the server a member of a domain?
>
>
>
> DDS
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I have just installed a new Windows 2003 R2 Enterprise X64 server and have
>>configured it as a file server. I am in the process of migrating from a
>>Novell file server to this Windows files server. I have moved 1 of the
>>volumes over and am having everyone test speed, reliability, etc. I am
>>mapping the drives via a VBS login script and that seems to be working.
>>
>> My first issue is that the first time the drives are accessed, it takes
>> 15-30 seconds (longer on our few Vista machines) for the drive to come up
>> or the application on the drive to launch, etc. After that, access is
>> acceptable. Not as fast as the Novell server but I kinda figured it
>> wouldn't be anyway. Our next issue is that after a certain amount of
>> time of inactivity it again takes 15-30 seconds to access anything on
>> this drive. It's as if it is 'losing' the connection and has to
>> re-establish it (just an observation, not a diagnosis.)
>>
>> I have turned off all unnecessary services and disabled oplocks. I also
>> have dual Intel NICs that are teamed.
>>
>> I'm not sure what else to do at this time to get rid of these delays.
>> Anyone have any ideas?
>>
>
>

Oh yeah, the DC's are also doing WINS.

-B

"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
> besides thier normal DC jobs. I am using the \\servername\sharename to
> map them in a logon script.
>
> "Danny Sanders" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Is the server a member of a domain?
>>
>>
>>
>> DDS
>>
>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
>>>have configured it as a file server. I am in the process of migrating
>>>from a Novell file server to this Windows files server. I have moved 1 of
>>>the volumes over and am having everyone test speed, reliability, etc. I
>>>am mapping the drives via a VBS login script and that seems to be
>>>working.
>>>
>>> My first issue is that the first time the drives are accessed, it takes
>>> 15-30 seconds (longer on our few Vista machines) for the drive to come
>>> up or the application on the drive to launch, etc. After that, access
>>> is acceptable. Not as fast as the Novell server but I kinda figured it
>>> wouldn't be anyway. Our next issue is that after a certain amount of
>>> time of inactivity it again takes 15-30 seconds to access anything on
>>> this drive. It's as if it is 'losing' the connection and has to
>>> re-establish it (just an observation, not a diagnosis.)
>>>
>>> I have turned off all unnecessary services and disabled oplocks. I also
>>> have dual Intel NICs that are teamed.
>>>
>>> I'm not sure what else to do at this time to get rid of these delays.
>>> Anyone have any ideas?
>>>
>>
>>
>
>

From what you describe it may be DNS or a problem with the NIC teaming.

What DNS server do they point to for Preferred? Alternate?

As far as the NICs, I've seen those exact same symptoms on a computer with 2
NICs enabled but NOT teamed.

I would suggest testing this by using one NIC and see if the problem is
resolved.


hth
DDS


"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Oh yeah, the DC's are also doing WINS.
>
> -B
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:O%(E-Mail Removed)...
>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
>> besides thier normal DC jobs. I am using the \\servername\sharename to
>> map them in a logon script.
>>
>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Is the server a member of a domain?
>>>
>>>
>>>
>>> DDS
>>>
>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
>>>>have configured it as a file server. I am in the process of migrating
>>>>from a Novell file server to this Windows files server. I have moved 1
>>>>of the volumes over and am having everyone test speed, reliability, etc.
>>>>I am mapping the drives via a VBS login script and that seems to be
>>>>working.
>>>>
>>>> My first issue is that the first time the drives are accessed, it takes
>>>> 15-30 seconds (longer on our few Vista machines) for the drive to come
>>>> up or the application on the drive to launch, etc. After that, access
>>>> is acceptable. Not as fast as the Novell server but I kinda figured it
>>>> wouldn't be anyway. Our next issue is that after a certain amount of
>>>> time of inactivity it again takes 15-30 seconds to access anything on
>>>> this drive. It's as if it is 'losing' the connection and has to
>>>> re-establish it (just an observation, not a diagnosis.)
>>>>
>>>> I have turned off all unnecessary services and disabled oplocks. I
>>>> also have dual Intel NICs that are teamed.
>>>>
>>>> I'm not sure what else to do at this time to get rid of these delays.
>>>> Anyone have any ideas?
>>>>
>>>
>>>
>>
>>
>
>

I am pointing to each of the DC's as the two DNS servers. Should I try
switching the primary to the secondary entries?

Also, I had one NIC enabled. Same problem. Switched to second NIC. Same
problem. Enabled both NICs. No help and finally teamed the NICs with same
problem.


"Danny Sanders" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> From what you describe it may be DNS or a problem with the NIC teaming.
>
> What DNS server do they point to for Preferred? Alternate?
>
> As far as the NICs, I've seen those exact same symptoms on a computer with
> 2 NICs enabled but NOT teamed.
>
> I would suggest testing this by using one NIC and see if the problem is
> resolved.
>
>
> hth
> DDS
>
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Oh yeah, the DC's are also doing WINS.
>>
>> -B
>>
>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> news:O%(E-Mail Removed)...
>>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
>>> besides thier normal DC jobs. I am using the \\servername\sharename to
>>> map them in a logon script.
>>>
>>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Is the server a member of a domain?
>>>>
>>>>
>>>>
>>>> DDS
>>>>
>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
>>>>>have configured it as a file server. I am in the process of migrating
>>>>>from a Novell file server to this Windows files server. I have moved 1
>>>>>of the volumes over and am having everyone test speed, reliability,
>>>>>etc. I am mapping the drives via a VBS login script and that seems to
>>>>>be working.
>>>>>
>>>>> My first issue is that the first time the drives are accessed, it
>>>>> takes 15-30 seconds (longer on our few Vista machines) for the drive
>>>>> to come up or the application on the drive to launch, etc. After
>>>>> that, access is acceptable. Not as fast as the Novell server but I
>>>>> kinda figured it wouldn't be anyway. Our next issue is that after a
>>>>> certain amount of time of inactivity it again takes 15-30 seconds to
>>>>> access anything on this drive. It's as if it is 'losing' the
>>>>> connection and has to re-establish it (just an observation, not a
>>>>> diagnosis.)
>>>>>
>>>>> I have turned off all unnecessary services and disabled oplocks. I
>>>>> also have dual Intel NICs that are teamed.
>>>>>
>>>>> I'm not sure what else to do at this time to get rid of these delays.
>>>>> Anyone have any ideas?
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

It appears I have this fixed. I was getting an entry in the Application
Event Log indicating event id: 12317 on SRMSVC. MSKB article:
http://support.microsoft.com/kb/924035
seems to have fixed it. Seems this is a problem with R2.

Thanks for your help.
-Bryan


"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I am pointing to each of the DC's as the two DNS servers. Should I try
>switching the primary to the secondary entries?
>
> Also, I had one NIC enabled. Same problem. Switched to second NIC. Same
> problem. Enabled both NICs. No help and finally teamed the NICs with same
> problem.
>
>
> "Danny Sanders" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> From what you describe it may be DNS or a problem with the NIC teaming.
>>
>> What DNS server do they point to for Preferred? Alternate?
>>
>> As far as the NICs, I've seen those exact same symptoms on a computer
>> with 2 NICs enabled but NOT teamed.
>>
>> I would suggest testing this by using one NIC and see if the problem is
>> resolved.
>>
>>
>> hth
>> DDS
>>
>>
>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Oh yeah, the DC's are also doing WINS.
>>>
>>> -B
>>>
>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>> news:O%(E-Mail Removed)...
>>>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
>>>> besides thier normal DC jobs. I am using the \\servername\sharename to
>>>> map them in a logon script.
>>>>
>>>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>>>> news:%(E-Mail Removed)...
>>>>> Is the server a member of a domain?
>>>>>
>>>>>
>>>>>
>>>>> DDS
>>>>>
>>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
>>>>>>have configured it as a file server. I am in the process of migrating
>>>>>>from a Novell file server to this Windows files server. I have moved 1
>>>>>>of the volumes over and am having everyone test speed, reliability,
>>>>>>etc. I am mapping the drives via a VBS login script and that seems to
>>>>>>be working.
>>>>>>
>>>>>> My first issue is that the first time the drives are accessed, it
>>>>>> takes 15-30 seconds (longer on our few Vista machines) for the drive
>>>>>> to come up or the application on the drive to launch, etc. After
>>>>>> that, access is acceptable. Not as fast as the Novell server but I
>>>>>> kinda figured it wouldn't be anyway. Our next issue is that after a
>>>>>> certain amount of time of inactivity it again takes 15-30 seconds to
>>>>>> access anything on this drive. It's as if it is 'losing' the
>>>>>> connection and has to re-establish it (just an observation, not a
>>>>>> diagnosis.)
>>>>>>
>>>>>> I have turned off all unnecessary services and disabled oplocks. I
>>>>>> also have dual Intel NICs that are teamed.
>>>>>>
>>>>>> I'm not sure what else to do at this time to get rid of these delays.
>>>>>> Anyone have any ideas?
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Correction, this fixed this problem for my Vista workstation. The XP
workstations are still experiencing the idle problem listed below.

Bummer for us.

-Bryan

"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> It appears I have this fixed. I was getting an entry in the Application
> Event Log indicating event id: 12317 on SRMSVC. MSKB article:
> http://support.microsoft.com/kb/924035
> seems to have fixed it. Seems this is a problem with R2.
>
> Thanks for your help.
> -Bryan
>
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I am pointing to each of the DC's as the two DNS servers. Should I try
>>switching the primary to the secondary entries?
>>
>> Also, I had one NIC enabled. Same problem. Switched to second NIC. Same
>> problem. Enabled both NICs. No help and finally teamed the NICs with same
>> problem.
>>
>>
>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> From what you describe it may be DNS or a problem with the NIC teaming.
>>>
>>> What DNS server do they point to for Preferred? Alternate?
>>>
>>> As far as the NICs, I've seen those exact same symptoms on a computer
>>> with 2 NICs enabled but NOT teamed.
>>>
>>> I would suggest testing this by using one NIC and see if the problem is
>>> resolved.
>>>
>>>
>>> hth
>>> DDS
>>>
>>>
>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Oh yeah, the DC's are also doing WINS.
>>>>
>>>> -B
>>>>
>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>>> news:O%(E-Mail Removed)...
>>>>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
>>>>> besides thier normal DC jobs. I am using the \\servername\sharename
>>>>> to map them in a logon script.
>>>>>
>>>>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>>>>> news:%(E-Mail Removed)...
>>>>>> Is the server a member of a domain?
>>>>>>
>>>>>>
>>>>>>
>>>>>> DDS
>>>>>>
>>>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>>>>>> news:(E-Mail Removed)...
>>>>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
>>>>>>>have configured it as a file server. I am in the process of
>>>>>>>migrating from a Novell file server to this Windows files server. I
>>>>>>>have moved 1 of the volumes over and am having everyone test speed,
>>>>>>>reliability, etc. I am mapping the drives via a VBS login script and
>>>>>>>that seems to be working.
>>>>>>>
>>>>>>> My first issue is that the first time the drives are accessed, it
>>>>>>> takes 15-30 seconds (longer on our few Vista machines) for the drive
>>>>>>> to come up or the application on the drive to launch, etc. After
>>>>>>> that, access is acceptable. Not as fast as the Novell server but I
>>>>>>> kinda figured it wouldn't be anyway. Our next issue is that after a
>>>>>>> certain amount of time of inactivity it again takes 15-30 seconds to
>>>>>>> access anything on this drive. It's as if it is 'losing' the
>>>>>>> connection and has to re-establish it (just an observation, not a
>>>>>>> diagnosis.)
>>>>>>>
>>>>>>> I have turned off all unnecessary services and disabled oplocks. I
>>>>>>> also have dual Intel NICs that are teamed.
>>>>>>>
>>>>>>> I'm not sure what else to do at this time to get rid of these
>>>>>>> delays. Anyone have any ideas?
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

I have come upon this a few times where it turned out that someone set the
NIC properties to a manual setting, rather than leaving the default of
"Auto". Because our switches are set to auto negotiate, the NICs have to
match.

It may not be likely that this is the problem, but you might want to check it.

"J. Bryan Wehrenberg" wrote:

> Correction, this fixed this problem for my Vista workstation. The XP
> workstations are still experiencing the idle problem listed below.
>
> Bummer for us.
>
> -Bryan
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > It appears I have this fixed. I was getting an entry in the Application
> > Event Log indicating event id: 12317 on SRMSVC. MSKB article:
> > http://support.microsoft.com/kb/924035
> > seems to have fixed it. Seems this is a problem with R2.
> >
> > Thanks for your help.
> > -Bryan
> >
> >
> > "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >>I am pointing to each of the DC's as the two DNS servers. Should I try
> >>switching the primary to the secondary entries?
> >>
> >> Also, I had one NIC enabled. Same problem. Switched to second NIC. Same
> >> problem. Enabled both NICs. No help and finally teamed the NICs with same
> >> problem.
> >>
> >>
> >> "Danny Sanders" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>> From what you describe it may be DNS or a problem with the NIC teaming.
> >>>
> >>> What DNS server do they point to for Preferred? Alternate?
> >>>
> >>> As far as the NICs, I've seen those exact same symptoms on a computer
> >>> with 2 NICs enabled but NOT teamed.
> >>>
> >>> I would suggest testing this by using one NIC and see if the problem is
> >>> resolved.
> >>>
> >>>
> >>> hth
> >>> DDS
> >>>
> >>>
> >>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> >>> news:(E-Mail Removed)...
> >>>> Oh yeah, the DC's are also doing WINS.
> >>>>
> >>>> -B
> >>>>
> >>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> >>>> news:O%(E-Mail Removed)...
> >>>>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and DNS
> >>>>> besides thier normal DC jobs. I am using the \\servername\sharename
> >>>>> to map them in a logon script.
> >>>>>
> >>>>> "Danny Sanders" <(E-Mail Removed)> wrote in message
> >>>>> news:%(E-Mail Removed)...
> >>>>>> Is the server a member of a domain?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> DDS
> >>>>>>
> >>>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> >>>>>> news:(E-Mail Removed)...
> >>>>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server and
> >>>>>>>have configured it as a file server. I am in the process of
> >>>>>>>migrating from a Novell file server to this Windows files server. I
> >>>>>>>have moved 1 of the volumes over and am having everyone test speed,
> >>>>>>>reliability, etc. I am mapping the drives via a VBS login script and
> >>>>>>>that seems to be working.
> >>>>>>>
> >>>>>>> My first issue is that the first time the drives are accessed, it
> >>>>>>> takes 15-30 seconds (longer on our few Vista machines) for the drive
> >>>>>>> to come up or the application on the drive to launch, etc. After
> >>>>>>> that, access is acceptable. Not as fast as the Novell server but I
> >>>>>>> kinda figured it wouldn't be anyway. Our next issue is that after a
> >>>>>>> certain amount of time of inactivity it again takes 15-30 seconds to
> >>>>>>> access anything on this drive. It's as if it is 'losing' the
> >>>>>>> connection and has to re-establish it (just an observation, not a
> >>>>>>> diagnosis.)
> >>>>>>>
> >>>>>>> I have turned off all unnecessary services and disabled oplocks. I
> >>>>>>> also have dual Intel NICs that are teamed.
> >>>>>>>
> >>>>>>> I'm not sure what else to do at this time to get rid of these
> >>>>>>> delays. Anyone have any ideas?
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

Thanks for the reply. Everything is set to auto on both the server and
workstations. I can't believe this is how a Windows network operates. I've
never used a Windows server as a file server, just for Exchange, AD, stuff
like that. So far it's not working out too well.

-B

"Baboon" <(E-Mail Removed)> wrote in message
news:E729B3B2-5E55-444F-BEC5-(E-Mail Removed)...
>I have come upon this a few times where it turned out that someone set the
> NIC properties to a manual setting, rather than leaving the default of
> "Auto". Because our switches are set to auto negotiate, the NICs have to
> match.
>
> It may not be likely that this is the problem, but you might want to check
> it.
>
> "J. Bryan Wehrenberg" wrote:
>
>> Correction, this fixed this problem for my Vista workstation. The XP
>> workstations are still experiencing the idle problem listed below.
>>
>> Bummer for us.
>>
>> -Bryan
>>
>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > It appears I have this fixed. I was getting an entry in the
>> > Application
>> > Event Log indicating event id: 12317 on SRMSVC. MSKB article:
>> > http://support.microsoft.com/kb/924035
>> > seems to have fixed it. Seems this is a problem with R2.
>> >
>> > Thanks for your help.
>> > -Bryan
>> >
>> >
>> > "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed)...
>> >>I am pointing to each of the DC's as the two DNS servers. Should I try
>> >>switching the primary to the secondary entries?
>> >>
>> >> Also, I had one NIC enabled. Same problem. Switched to second NIC.
>> >> Same
>> >> problem. Enabled both NICs. No help and finally teamed the NICs with
>> >> same
>> >> problem.
>> >>
>> >>
>> >> "Danny Sanders" <(E-Mail Removed)> wrote in message
>> >> news:(E-Mail Removed)...
>> >>> From what you describe it may be DNS or a problem with the NIC
>> >>> teaming.
>> >>>
>> >>> What DNS server do they point to for Preferred? Alternate?
>> >>>
>> >>> As far as the NICs, I've seen those exact same symptoms on a computer
>> >>> with 2 NICs enabled but NOT teamed.
>> >>>
>> >>> I would suggest testing this by using one NIC and see if the problem
>> >>> is
>> >>> resolved.
>> >>>
>> >>>
>> >>> hth
>> >>> DDS
>> >>>
>> >>>
>> >>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> >>> news:(E-Mail Removed)...
>> >>>> Oh yeah, the DC's are also doing WINS.
>> >>>>
>> >>>> -B
>> >>>>
>> >>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> >>>> news:O%(E-Mail Removed)...
>> >>>>> Yes. An AD domain with two DC's. The DC's are only doing DHCP and
>> >>>>> DNS
>> >>>>> besides thier normal DC jobs. I am using the
>> >>>>> \\servername\sharename
>> >>>>> to map them in a logon script.
>> >>>>>
>> >>>>> "Danny Sanders" <(E-Mail Removed)> wrote in message
>> >>>>> news:%(E-Mail Removed)...
>> >>>>>> Is the server a member of a domain?
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> DDS
>> >>>>>>
>> >>>>>> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
>> >>>>>> news:(E-Mail Removed)...
>> >>>>>>>I have just installed a new Windows 2003 R2 Enterprise X64 server
>> >>>>>>>and
>> >>>>>>>have configured it as a file server. I am in the process of
>> >>>>>>>migrating from a Novell file server to this Windows files server.
>> >>>>>>>I
>> >>>>>>>have moved 1 of the volumes over and am having everyone test
>> >>>>>>>speed,
>> >>>>>>>reliability, etc. I am mapping the drives via a VBS login script
>> >>>>>>>and
>> >>>>>>>that seems to be working.
>> >>>>>>>
>> >>>>>>> My first issue is that the first time the drives are accessed, it
>> >>>>>>> takes 15-30 seconds (longer on our few Vista machines) for the
>> >>>>>>> drive
>> >>>>>>> to come up or the application on the drive to launch, etc. After
>> >>>>>>> that, access is acceptable. Not as fast as the Novell server but
>> >>>>>>> I
>> >>>>>>> kinda figured it wouldn't be anyway. Our next issue is that
>> >>>>>>> after a
>> >>>>>>> certain amount of time of inactivity it again takes 15-30 seconds
>> >>>>>>> to
>> >>>>>>> access anything on this drive. It's as if it is 'losing' the
>> >>>>>>> connection and has to re-establish it (just an observation, not a
>> >>>>>>> diagnosis.)
>> >>>>>>>
>> >>>>>>> I have turned off all unnecessary services and disabled oplocks.
>> >>>>>>> I
>> >>>>>>> also have dual Intel NICs that are teamed.
>> >>>>>>>
>> >>>>>>> I'm not sure what else to do at this time to get rid of these
>> >>>>>>> delays. Anyone have any ideas?
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>>