opening word document, getting bad ARP requests

[Jeremy P]

Here's the situation:
Problem - many users are having very slow response when opening Word
documents.

I've spent hours looking at the problem, and here's the only strange thing I
find. Running a packet sniffer, I see that opening a Word document causes
the PC to send out an ARP request (actually it sends out 5 or 6 requests)
for the IP (192.168.100.10). That is the address of an old BDC that was
removed from our network a few days ago. That machine doesn't exist
anymore. But for some reason, opening a Word document triggers the PC to
ARP that address, which causes Word to hang until the ARP request times out.

Opening Word without a document does not cause this. Also, if I open Word,
create and save a new document, then open that document again I don't get
the error. It's only when I open documents that were created while that old
server was still around. That old server was also our print server, so the
documents in question were very likely created when the user's default
printer was pointing to a printer share on that server. Not sure if that
makes a difference or not. All users now are using our new print server.

What data is embedded in a Word document that would cause this??? Any ideas
how to fix the problem?

All other network stuff is working fine. We are running in mixed mode
(didn;'t want to change to native for a few days after the last BDC was
removed in case of trouble)

 

[Jeremy P]

Also - i've tried using Word 2003, and Word 2000. get the same behaviour



Here's the situation:
Problem - many users are having very slow response when opening Word
documents.

I've spent hours looking at the problem, and here's the only strange thing I
find. Running a packet sniffer, I see that opening a Word document causes
the PC to send out an ARP request (actually it sends out 5 or 6 requests)
for the IP (192.168.100.10). That is the address of an old BDC that was
removed from our network a few days ago. That machine doesn't exist
anymore. But for some reason, opening a Word document triggers the PC to
ARP that address, which causes Word to hang until the ARP request times out.

Opening Word without a document does not cause this. Also, if I open Word,
create and save a new document, then open that document again I don't get
the error. It's only when I open documents that were created while that old
server was still around. That old server was also our print server, so the
documents in question were very likely created when the user's default
printer was pointing to a printer share on that server. Not sure if that
makes a difference or not. All users now are using our new print server.

What data is embedded in a Word document that would cause this??? Any ideas
how to fix the problem?

All other network stuff is working fine. We are running in mixed mode
(didn;'t want to change to native for a few days after the last BDC was
removed in case of trouble)

 

[Jeremy P]

I've tried reinstalling Office

using the /a switch

running Word in safe mode


same results

Here's the situation:
Problem - many users are having very slow response when opening Word
documents.

I've spent hours looking at the problem, and here's the only strange thing I
find. Running a packet sniffer, I see that opening a Word document causes
the PC to send out an ARP request (actually it sends out 5 or 6 requests)
for the IP (192.168.100.10). That is the address of an old BDC that was
removed from our network a few days ago. That machine doesn't exist
anymore. But for some reason, opening a Word document triggers the PC to
ARP that address, which causes Word to hang until the ARP request times out.

Opening Word without a document does not cause this. Also, if I open Word,
create and save a new document, then open that document again I don't get
the error. It's only when I open documents that were created while that old
server was still around. That old server was also our print server, so the
documents in question were very likely created when the user's default
printer was pointing to a printer share on that server. Not sure if that
makes a difference or not. All users now are using our new print server.

What data is embedded in a Word document that would cause this??? Any ideas
how to fix the problem?

All other network stuff is working fine. We are running in mixed mode
(didn;'t want to change to native for a few days after the last BDC was
removed in case of trouble)

 

[Bob S]

Here's the situation:
Problem - many users are having very slow response when opening Word
documents.

I've spent hours looking at the problem, and here's the only strange thing I
find. Running a packet sniffer, I see that opening a Word document causes
the PC to send out an ARP request (actually it sends out 5 or 6 requests)
for the IP (192.168.100.10). That is the address of an old BDC that was
removed from our network a few days ago. That machine doesn't exist
anymore. But for some reason, opening a Word document triggers the PC to
ARP that address, which causes Word to hang until the ARP request times out.

Opening Word without a document does not cause this. Also, if I open Word,
create and save a new document, then open that document again I don't get
the error. It's only when I open documents that were created while that old
server was still around. That old server was also our print server, so the
documents in question were very likely created when the user's default
printer was pointing to a printer share on that server. Not sure if that
makes a difference or not. All users now are using our new print server.

What data is embedded in a Word document that would cause this??? Any ideas
how to fix the problem?

All other network stuff is working fine. We are running in mixed mode
(didn;'t want to change to native for a few days after the last BDC was
removed in case of trouble)

Word is probably looking for an attached template on the old server.
Open one of the documents, change the attached template to one that
actually exists somewhere, make some trivial change to the document so
that Word thinks it is dirty (e.g. add a space character and then
delete it again), and close the document. Open it again; if it now
opens quickly you have found the problem. The cure is to change the
attached template for all of the old documents, o put the old server
address back. Either is a PITA...

Bob S

 

[Guest]

hey i am having the same problem.... has anyone found a solution yet

steve