Still having slow issues on network shares

I posted this question before and was able to get some help but am still
having an issue. I have a 2003 R2 64bit file server I am doing some testing
on. I have migrated a volume from a Novell server and created a new share
and I map it via a VBS logon script. All that seems to be working fine. I
can access the share right away after the login script runs. However, after
an bit of time, say 15 minutes, with no activity on that share, I seem to
'lose' the connection. When I click on the drive to access it, it takes
between 15 and 30 seconds for the directories/files in that share to be
displayed. Applications that use that share also take that long to respond
after they have been sitting idle for a while.

I'm running an Active Directory domain with 2 DC's. I really want to figure
this out before I migrate the remainder of the volumes.

I have seen this happen to clients of an AD domain that have a DNS server
listed as "alternate" that is NOT a DNS server setup for the AD domain.
*Usually* the DNS server listed as alternate is the ISP's DNS server.

Would this be the case here?

hth
DDS

"J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
news:ulUYz66%(E-Mail Removed)...
>I posted this question before and was able to get some help but am still
>having an issue. I have a 2003 R2 64bit file server I am doing some
>testing on. I have migrated a volume from a Novell server and created a new
>share and I map it via a VBS logon script. All that seems to be working
>fine. I can access the share right away after the login script runs.
>However, after an bit of time, say 15 minutes, with no activity on that
>share, I seem to 'lose' the connection. When I click on the drive to
>access it, it takes between 15 and 30 seconds for the directories/files in
>that share to be displayed. Applications that use that share also take
>that long to respond after they have been sitting idle for a while.
>
> I'm running an Active Directory domain with 2 DC's. I really want to
> figure this out before I migrate the remainder of the volumes.
>

I appreciate your response but that's not it. I have figured out what is
causing this. It is a change made by the Netware client. In the key:

HKLM\System\CurrentControlSet\Control\NetworkProvi der\Order

there is a ProviderOrder Entry that had this value:

NetwareWorkstation,LanmanWorkstation,RDPNP,WebClie nt

Changing it to this solves the issue:

LanmanWorkstation,NetwareWorkstation,RDPNP,WebClie nt

The Netware shares become a little slow to respond but not nearly as slow as
the Windows shares. When everything is finally migrated and the Netware
client is removed, this will be a non-issue.

Thanks for your help,
Bryan


"Danny Sanders" <(E-Mail Removed)> wrote in message
news:OWhLBD7%(E-Mail Removed)...
>I have seen this happen to clients of an AD domain that have a DNS server
>listed as "alternate" that is NOT a DNS server setup for the AD domain.
>*Usually* the DNS server listed as alternate is the ISP's DNS server.
>
> Would this be the case here?
>
> hth
> DDS
>
> "J. Bryan Wehrenberg" <(E-Mail Removed)> wrote in message
> news:ulUYz66%(E-Mail Removed)...
>>I posted this question before and was able to get some help but am still
>>having an issue. I have a 2003 R2 64bit file server I am doing some
>>testing on. I have migrated a volume from a Novell server and created a
>>new share and I map it via a VBS logon script. All that seems to be
>>working fine. I can access the share right away after the login script
>>runs. However, after an bit of time, say 15 minutes, with no activity on
>>that share, I seem to 'lose' the connection. When I click on the drive to
>>access it, it takes between 15 and 30 seconds for the directories/files in
>>that share to be displayed. Applications that use that share also take
>>that long to respond after they have been sitting idle for a while.
>>
>> I'm running an Active Directory domain with 2 DC's. I really want to
>> figure this out before I migrate the remainder of the volumes.
>>
>
>