delay after opening a network document

Hello, I have a Windows xp system at work and there is a delay after opening
a document from the network server. the XP machine is less then 6 months old
and has always had this issue. the version of office is either 2003 or
office xp. I don't remember at the top of my head. the other computers there
have the same office version but older operating systems. There are 4 other
computers with windows 2000 on them and have no problems like the windows xp
does. the files are being hosted on a nt4 server but if I create and share a
file on one of the windows 2000 workstations I have the same result.

When I open a local document, or even copy the networked document to the
local machine first, it open right away and you can immediately start
editing it. The network is 100 based and does have pretty good speed. I
don't think that is it. (especially since the other computers don't have the
issue)

here is a little m ore detail on what happens. I open the shared folder
which is called 2004, then select the filei want. In this case it is
roads.doc. now it opens word and displays an image of the document after
about 2 seconds or less. If the file was local I could go ahead and edit it
now but, I need to wait an additional 15-80 seconds. It has become longer at
times but usually stays within the 15-80 seconds.

I have no idea what is going on during this time. As I noted earlier, it
doesn't do this on local files. Also none of the windows 2000 workstations
with the same version of office does this. it is very annoying could someone
please point me in the right direction of what this could be. not only am I
interested in reducing the amount of time (getting rid of it would be ideal)
but I am curious to what is causing it. after this annoyance is solve the
other workstation are supposed to be upgraded to xp also. thank you

Jazz,

As a Microsoft Certified Network Geek (i.e., MCSE) I can tell you that it's your network that's the problem. Network delays vary widely depending on how many users are on the systems and what they are accessing at that given moment. If you have a lot of users who just happen to be doing something high bandwidth, you can easily wait for 1.5 minutes for a file to open. Also has to do with whether you're on the same side of the routers and switches as the server you're accessing and lots of other network config stuff. Sic your local network geek on the problem. It's most likely not word.

unfortunatly I too am a mcse certified net admin as well as a linux A+ and
novel netware certrified, (but i don't admin this network). I'm not seeing
how this would be network related when other computer on the same hub can
access the files without problems. It is only the windows XP machine.

As a test i placed a file on th XP machine and the same file on a windows
2000 machine. when i tryed to open it from the 2000 (on the xp) it opened
normally but the other way around it was slow again. It is almost like after
it opens (or would have been open on the windows 2000 machines) some other
proccess has to run. kind of like it is opening twice with the delay on the
second part. It may not be word in its entirety just seems that way.

thank you for your time though. i will try changing the network cables
around tomarrow and see what i can find with that. also i have finally found
some stuff about a temp buffer and stuff that i am going to look into some
more.

most notably i think the articles 280821 might apply

"BJLMorgan" See the article "How to create a template that makes it easy
for users wrote in message
...
Jazz,

As a Microsoft Certified Network Geek (i.e., MCSE) I can tell you that
it's your network that's the problem. Network delays vary widely depending
on how many users are on the systems and what they are accessing at that
given moment. If you have a lot of users who just happen to be doing
something high bandwidth, you can easily wait for 1.5 minutes for a file to
open. Also has to do with whether you're on the same side of the routers
and switches as the server you're accessing and lots of other network config
stuff. Sic your local network geek on the problem. It's most likely not
word.

I apoligize for being so stubborn. It would appear you are corect. After
reading your reply, I decided to do an extended ping test (ping -t) and
after the first 8 or so packets I was experiencing around a 50% packet loss.
I suspect one of the switches to be the problem. Thank you for making me
second guess what I was convinced of and pointing back into the right
direction.


"BJLMorgan" See the article "How to create a template that makes it easy
for users wrote in message
...
Jazz,

As a Microsoft Certified Network Geek (i.e., MCSE) I can tell you that
it's your network that's the problem. Network delays vary widely depending
on how many users are on the systems and what they are accessing at that
given moment. If you have a lot of users who just happen to be doing
something high bandwidth, you can easily wait for 1.5 minutes for a file to
open. Also has to do with whether you're on the same side of the routers
and switches as the server you're accessing and lots of other network config
stuff. Sic your local network geek on the problem. It's most likely not
word.

You're welcome. I just had to fix an almost exact duplicate of your problem on my net last week so I was reasonably sure it was network equipment.

There can be problems with slow opening of WordXP docs if the templates are corrupted or missing, so you might want to reinstall those as well.

"BJLMorgan" wrote in message
...
You're welcome. I just had to fix an almost exact duplicate of your
problem on my net last week so I was reasonably sure it was network
equipment.

There can be problems with slow opening of WordXP docs if the templates
are corrupted or missing, so you might want to reinstall those as well.

I'll give that a look. I fixed the network problem (the hub was bad).
Everythign is alot quicker now.. Word still is a littel slow but nothing
like what it was doing.