W
Wintensive
Hi all, exellent group and a great resource. Here's my problem:
I have 4 systems:
File Sevrer: XP pro SP2 file server. Has 3 hard drives all setup for
sharing the root drive with the following computers
Workstation: XP Pro SP2
Laptop1: XP Pro SP2
Laptop 2: XP Pro SP2
simple file sharing is off. All shares have permission and security
set for 2 admin users, admins, owner and system to have full access.
The "everyone" group is always removed.
All the computers EXCEPT the workstation can access the shares without
any problem. The workstation has the following problem. It can
access all shares whether through the network neighborhood or the
mapped drives in My Computer. However, beyond the root of the share,
there are 3 folders which lag for about 20 seconds before opening up.
Most of the time each of these folders lags and sometimes, immediately
after I have just opened one and then gone back a few levels it may
open up without a lag. Sometimes even if I have just been in one of
the problem folder, it lags again when I try to access it. I haven't
been able to find a pattern to this. So the root of the shares always
open fine and the mapped drives immediately open, but just those
problem folders cuase the lag. There are 2 problem folders just
beyond the root drive, and then each level you drill down into the
problem folders has a few folders within it that do the same thing.
All the other computers on the network including the serve itself
access all shares and folders beyond the root without a problem. The
ONLY exception to this is that if I try with the workstation and the
lag begins, if I then try from another computer or the server itself
while the workstation is lagging, the other computers also lag until
the workstation computer lag finishes and opens the folder. Right
then all other systems open the folder as well. So I can only
initiate the lag on all other machines by attempting access to the
problem folders on the workstation first.
Most Likely explanation in my opinion (even though I can't see
evidence for this:
I recently got rid of my old file server because it was an old P2 and
getting slow in general. It did NOT have this lag. On the new file
server I did recreate the exact shares with the same drive letter as
exactly as I could so that I didn't have to remap everything on the
"client" systems. After I did this all the shares worked fine from
their existing mapped drives, with the exception of the lag happening
after I did this. So I suppose it could be an old registry item for
an old mapping that is getting in the way. You'll see below that I see
no incorrect IP addresses in the netstat -a command though.
Here's what I have tried to do to fix it without success:
- enabling NetBIOS over TCP/IP on all systems
-I disabled write caching on the hard drives themselves in hard drive
properties on server
-I created another folder called "new folder" on the root of the share
and copied the problem folder and its content (some of which are also
problem folders). The same folders which caused the problem in the
original location lag in the new location as well (or anywhere else I
copy the folder to)
-tried looking at the netstat -a log but I can't see much of a
difference before the lag vs. during the lag. There are no old IPs or
shares listed that could be causing a timeout because they no longer
exist. But I am not totally sure what I am looking at in the report
anyway. I'll post if anyone wants it.
-reset TCP/IP with netsh int ip reset command
-the server uses a static IP, and the rest are DHCP, but I added the
DNS server (which is my router) to all the network configs of the
server and the workstation anyway
Are there any scans, command, logs I can run to see if we can take a
closer look at the behavior of the system and network when the lag
happens that may point us to the problem?
Thanks in advance to anyone who has read this far and wants to help.
It is much appreciated!
Jason T.
wintensive at yahoo dot (com)
I have 4 systems:
File Sevrer: XP pro SP2 file server. Has 3 hard drives all setup for
sharing the root drive with the following computers
Workstation: XP Pro SP2
Laptop1: XP Pro SP2
Laptop 2: XP Pro SP2
simple file sharing is off. All shares have permission and security
set for 2 admin users, admins, owner and system to have full access.
The "everyone" group is always removed.
All the computers EXCEPT the workstation can access the shares without
any problem. The workstation has the following problem. It can
access all shares whether through the network neighborhood or the
mapped drives in My Computer. However, beyond the root of the share,
there are 3 folders which lag for about 20 seconds before opening up.
Most of the time each of these folders lags and sometimes, immediately
after I have just opened one and then gone back a few levels it may
open up without a lag. Sometimes even if I have just been in one of
the problem folder, it lags again when I try to access it. I haven't
been able to find a pattern to this. So the root of the shares always
open fine and the mapped drives immediately open, but just those
problem folders cuase the lag. There are 2 problem folders just
beyond the root drive, and then each level you drill down into the
problem folders has a few folders within it that do the same thing.
All the other computers on the network including the serve itself
access all shares and folders beyond the root without a problem. The
ONLY exception to this is that if I try with the workstation and the
lag begins, if I then try from another computer or the server itself
while the workstation is lagging, the other computers also lag until
the workstation computer lag finishes and opens the folder. Right
then all other systems open the folder as well. So I can only
initiate the lag on all other machines by attempting access to the
problem folders on the workstation first.
Most Likely explanation in my opinion (even though I can't see
evidence for this:
I recently got rid of my old file server because it was an old P2 and
getting slow in general. It did NOT have this lag. On the new file
server I did recreate the exact shares with the same drive letter as
exactly as I could so that I didn't have to remap everything on the
"client" systems. After I did this all the shares worked fine from
their existing mapped drives, with the exception of the lag happening
after I did this. So I suppose it could be an old registry item for
an old mapping that is getting in the way. You'll see below that I see
no incorrect IP addresses in the netstat -a command though.
Here's what I have tried to do to fix it without success:
- enabling NetBIOS over TCP/IP on all systems
-I disabled write caching on the hard drives themselves in hard drive
properties on server
-I created another folder called "new folder" on the root of the share
and copied the problem folder and its content (some of which are also
problem folders). The same folders which caused the problem in the
original location lag in the new location as well (or anywhere else I
copy the folder to)
-tried looking at the netstat -a log but I can't see much of a
difference before the lag vs. during the lag. There are no old IPs or
shares listed that could be causing a timeout because they no longer
exist. But I am not totally sure what I am looking at in the report
anyway. I'll post if anyone wants it.
-reset TCP/IP with netsh int ip reset command
-the server uses a static IP, and the rest are DHCP, but I added the
DNS server (which is my router) to all the network configs of the
server and the workstation anyway
Are there any scans, command, logs I can run to see if we can take a
closer look at the behavior of the system and network when the lag
happens that may point us to the problem?
Thanks in advance to anyone who has read this far and wants to help.
It is much appreciated!
Jason T.
wintensive at yahoo dot (com)