"Chuck" wrote:

> On Sun, 10 Sep 2006 23:03:01 -0700, Richard Bonn <Richard
> B***@discussions.microsoft.com> wrote:
>
> >When I double click on a file to open in Windows Explorer (Word, Excel, PDF,
> >ect) the system hang for 1 to 2 minutes and then the file opens and works
> >normally.  This happen if the file is local or on the network but only
> >happens when I am connect to the network.  All mapped drive are connected and
> >working.  When I am in Word, for example, and I open the file from file/open
> >it open normally. 
>
> Richard,
>
> I'd first look at the protocol stack.
> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>
> And IP Configuration.
> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html
>
> Does this happen on just one computer?  More detail about your network might
> help.
> <http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
> http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
>
> And LSP / Winsock Corruption is another possibility.
> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.
>

>"Chuck" wrote:
>
>> On Sun, 10 Sep 2006 23:03:01 -0700, Richard Bonn <Richard
>> B***@discussions.microsoft.com> wrote:
>>
>> >When I double click on a file to open in Windows Explorer (Word, Excel, PDF,
>> >ect) the system hang for 1 to 2 minutes and then the file opens and works
>> >normally.  This happen if the file is local or on the network but only
>> >happens when I am connect to the network.  All mapped drive are connected and
>> >working.  When I am in Word, for example, and I open the file from file/open
>> >it open normally. 
>>
>> Richard,
>>
>> I'd first look at the protocol stack.
>> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
>> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>>
>> And IP Configuration.
>> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
>> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html
>>
>> Does this happen on just one computer?  More detail about your network might
>> help.
>> <http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
>> http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
>>
>> And LSP / Winsock Corruption is another possibility.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

>Thank Chuck but that did not fix my problem.  We have 10 computers and an SBS
>2003 server.  The problem is on 1 Desktop and 1 notebook.  Only the needed
>items are installed under networking.  IPconfig looks normal.  I ran "netsh
>winsock reset catalog", WinsockFix, LSP-Fix.
>
>Anyother ideas?  Thank you!

"Chuck" wrote:

> On Mon, 11 Sep 2006 12:07:02 -0700, Richard Bonn
> <RichardB***@discussions.microsoft.com> wrote:
>
> >"Chuck" wrote:
> >
> >> On Sun, 10 Sep 2006 23:03:01 -0700, Richard Bonn <Richard
> >> B***@discussions.microsoft.com> wrote:
> >>
> >> >When I double click on a file to open in Windows Explorer (Word, Excel, PDF,
> >> >ect) the system hang for 1 to 2 minutes and then the file opens and works
> >> >normally.  This happen if the file is local or on the network but only
> >> >happens when I am connect to the network.  All mapped drive are connected and
> >> >working.  When I am in Word, for example, and I open the file from file/open
> >> >it open normally. 
> >>
> >> Richard,
> >>
> >> I'd first look at the protocol stack.
> >> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
> >> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
> >>
> >> And IP Configuration.
> >> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
> >> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html
> >>
> >> Does this happen on just one computer?  More detail about your network might
> >> help.
> >> <http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
> >> http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
> >>
> >> And LSP / Winsock Corruption is another possibility.
> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> >> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
>
> >Thank Chuck but that did not fix my problem.  We have 10 computers and an SBS
> >2003 server.  The problem is on 1 Desktop and 1 notebook.  Only the needed
> >items are installed under networking.  IPconfig looks normal.  I ran "netsh
> >winsock reset catalog", WinsockFix, LSP-Fix.
> >
> >Anyother ideas?  Thank you!
>
> Richard,
>
> Lots of ideas.  We've only started.  But you will have to work.
>
> What's different about the 2 computers with problems?  How are they like each
> other, yet not like the rest?
> # Owners.
> # Physical connectivity.
> # Configuration.
> # Software.
> <http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
> http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
>
> Look at "browstat status", "ipconfig /all", "net config server", and "net config
> workstation", from those 2 computers, and from 2 others, and diagnose the
> problem.  Share them with us.  Read these articles, and linked articles, and
> follow instructions precisely (download browstat!):
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
> <http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html>
> http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html
>
> And please type your replies after mine.
> <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.

>

>
>
>"Chuck" wrote:
>
>> On Mon, 11 Sep 2006 12:07:02 -0700, Richard Bonn
>> <RichardB***@discussions.microsoft.com> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Sun, 10 Sep 2006 23:03:01 -0700, Richard Bonn <Richard
>> >> B***@discussions.microsoft.com> wrote:
>> >>
>> >> >When I double click on a file to open in Windows Explorer (Word, Excel, PDF,
>> >> >ect) the system hang for 1 to 2 minutes and then the file opens and works
>> >> >normally.  This happen if the file is local or on the network but only
>> >> >happens when I am connect to the network.  All mapped drive are connected and
>> >> >working.  When I am in Word, for example, and I open the file from file/open
>> >> >it open normally. 
>> >>
>> >> Richard,
>> >>
>> >> I'd first look at the protocol stack.
>> >> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
>> >> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>> >>
>> >> And IP Configuration.
>> >> <http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
>> >> http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html
>> >>
>> >> Does this happen on just one computer?  More detail about your network might
>> >> help.
>> >> <http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
>> >> http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
>> >>
>> >> And LSP / Winsock Corruption is another possibility.
>> >> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> >> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
>>
>> >Thank Chuck but that did not fix my problem.  We have 10 computers and an SBS
>> >2003 server.  The problem is on 1 Desktop and 1 notebook.  Only the needed
>> >items are installed under networking.  IPconfig looks normal.  I ran "netsh
>> >winsock reset catalog", WinsockFix, LSP-Fix.
>> >
>> >Anyother ideas?  Thank you!
>>
>> Richard,
>>
>> Lots of ideas.  We've only started.  But you will have to work.
>>
>> What's different about the 2 computers with problems?  How are they like each
>> other, yet not like the rest?
>> # Owners.
>> # Physical connectivity.
>> # Configuration.
>> # Software.
>> <http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
>> http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html
>>
>> Look at "browstat status", "ipconfig /all", "net config server", and "net config
>> workstation", from those 2 computers, and from 2 others, and diagnose the
>> problem.  Share them with us.  Read these articles, and linked articles, and
>> follow instructions precisely (download browstat!):
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
>> <http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html>
>> http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html
>>
>> And please type your replies after mine.
>> <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
>> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
>>
>> --
>> Cheers,
>> Chuck, MS-MVP [Windows - Networking]
>> http://nitecruzr.blogspot.com/
>> Paranoia is not a problem, when it's a normal response from experience.
>> My        email         is          AT         DOT
>>    actual       address    pchuck       mvps        org.
>
>Chuck,
>
>I would like to repost this question and see if someone else has some input.
> I have read all done all of what you sent but this is not fixing my problem.