Selling my soul to the devil is the next step...

  • Thread starter Thread starter Dr Teeth
  • Start date Start date
Hi Chuck,
Tests 1 - 4 will identify either a router port or Ethernet cable as the problem.
If no changes are observed from any of the 4 tests, then the problem will be a
firewall. Or possibly a LSP / Winsock problem, but with the symmetry, I don't
believe that.
Click to expand...

None of the tests made any difference to the problem at all. SpyBot
S&D has a facility to examine LSP/Winsocks and nothing strange (to my
eyes) was there. The Laptop, PC2, seemed to have more protocols
though, but all referenced the same MSoft DLL. Screenies can be
uploaded to my site.
If it's a firewall, we'll think of some more tests. Just do this very
deliberately.
Click to expand...

Firewalls have been installed on the laptop, but are fully
disabled...uninstalled and running services checked. But obviously, am
happy to run whatever tests you advise.

The symmetry of this problem has bothered me all along <g>.


--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,


None of the tests made any difference to the problem at all. SpyBot
S&D has a facility to examine LSP/Winsocks and nothing strange (to my
eyes) was there. The Laptop, PC2, seemed to have more protocols
though, but all referenced the same MSoft DLL. Screenies can be
uploaded to my site.


Firewalls have been installed on the laptop, but are fully
disabled...uninstalled and running services checked. But obviously, am
happy to run whatever tests you advise.

The symmetry of this problem has bothered me all along <g>.
Click to expand...

Please don't do screenies, do texties, and post here. Start with LSP / Winsock
enumerations, for Windows XP SP2 simply "netsh winsock show catalog".
<http://nitecruzr.blogspot.com/2006/03/lsp-winsock-analysis-using-netsh.html>
http://nitecruzr.blogspot.com/2006/03/lsp-winsock-analysis-using-netsh.html

What firewalls are "disabled"? Google in this forum for folks who have problems
even with firewalls "disabled".
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
 
I was just thinking how wonderful life was, when Chuck
And your testing, as you swap cables and / or router ports, can be very simple.
From Tardis_2, open one command window, and type "ping -t 192.168.1.3" (Ping
Laptop by IP address). Then open a second command window, and type "ping -t
192.168.1.4" (Ping Number_1 by IP address). Do the same for the other two
computers, but differing targets. The "ping -t" will ping continuously, and you
won't have to restart anything. See instantly when you make a change that makes
the problem move.
Click to expand...

I'll run the tests again. Previously, I just tried to browse the
various shares.

I've got to the stage where I'm prepared to partition my h/ds on PCs
1+2 and use a vanilla install of XP for testing...I hate it when
technology wins [though it hasn't yet].

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
I was just thinking how wonderful life was, when Chuck
What firewalls are "disabled"?
Click to expand...

Zonealarm free...uninstalled and double check for running services [a
known issue even after uninstall].

Kerio, similarly uninstalled and checked for running services.

Both on Laptop (PC2 only).

PC1 has never had a firewall installed either of the software variety
or nVidia's hardware one.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
I was just thinking how wonderful life was, when Chuck
And your testing, as you swap cables and / or router ports, can be very simple.
From Tardis_2, open one command window, and type "ping -t 192.168.1.3" (Ping
Laptop by IP address). Then open a second command window, and type "ping -t
192.168.1.4" (Ping Number_1 by IP address). Do the same for the other two
computers, but differing targets. The "ping -t" will ping continuously, and you
won't have to restart anything. See instantly when you make a change that makes
the problem move.
Click to expand...

Neat idea, but nothing made any difference. I did notice that pinging
TARDIS_2 from Laptop produced a 'request timed out' error. Pinging in
the other direction produced a 'destination unreachable error'.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,

I've fixed it, but you probably won't be happy with my solution. I am
not as we should have been able to get things to work 'properly'.

I did partition the disk on Laptop (PC2) and reinstalled win XP. Nada!

The solution, I installed NetBEUI on all PCs on the network. I'd still
like to know what was FUBAR in the first place though.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,

I've fixed it, but you probably won't be happy with my solution. I am
not as we should have been able to get things to work 'properly'.

I did partition the disk on Laptop (PC2) and reinstalled win XP. Nada!

The solution, I installed NetBEUI on all PCs on the network. I'd still
like to know what was FUBAR in the first place though.
Click to expand...
Doc
As you may remember, we communicated about my similar problem, which
Chuck helped me step through with a lengthy thread. I apologize for
not knowing the details of your own problem, but I did post details
of my solution in this group on 8/13, under the heading "NVIDIA
hidden firewall..."
I hope this may help you.
Best regards,

Jack
 
I was just thinking how wonderful life was, when JClark
Doc
As you may remember, we communicated about my similar problem, which
Chuck helped me step through with a lengthy thread. I apologize for
not knowing the details of your own problem, but I did post details
of my solution in this group on 8/13, under the heading "NVIDIA
hidden firewall..."
I hope this may help you.
Best regards,

Jack
Click to expand...

Hi Jack,

Many thanks for visiting this thread with your info. I followed 'your'
thread with interest.

The issue of the firewall has been mentioned and it is not present on
my system...I always declined nVidia's offer and always installed just
the ethernet drivers. No firewalls or their services or hooks into
LSP/TCP stack are present.

Though things are basically fixed here, it is very frustrating not
knowing what the real problem is and fixing that <g>.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
I was just thinking how wonderful life was, when JClark


Hi Jack,

Many thanks for visiting this thread with your info. I followed 'your'
thread with interest.

The issue of the firewall has been mentioned and it is not present on
my system...I always declined nVidia's offer and always installed just
the ethernet drivers. No firewalls or their services or hooks into
LSP/TCP stack are present.

Though things are basically fixed here, it is very frustrating not
knowing what the real problem is and fixing that <g>.
Click to expand...
Hi Guy,
I'm not trying to beat a dead horse here, but my point was that I was
sure, really sure I didn't have the NVIDIA firewall either, but it was
there, hidden in the Network Access Manager, a separate program from
the "NVIDIA drivers". So just a friendly reminder to check under
add\remove programs to be sure Network Access Manager isn't on your
system either.

As an aside, I remember hearing bad things about NETBUI, but I'm too
ignorant to remember what they were and too tired to research it.
Perhaps Chuck will enlighten us both on the subject.
Best regards and good luck.

Jack
 
Hi Chuck,

I've fixed it, but you probably won't be happy with my solution. I am
not as we should have been able to get things to work 'properly'.

I did partition the disk on Laptop (PC2) and reinstalled win XP. Nada!

The solution, I installed NetBEUI on all PCs on the network. I'd still
like to know what was FUBAR in the first place though.
Click to expand...

If using NetBEUI solved the problem, then the problem was, most likely, the
firewall (or an LSP / Winsock fix not tried). If nVidia hardware was involved,
then there is the problem. When you install the nVidia drivers, you install
some component that blocks SMBs. If you're still very frustrated not knowing
what the real problem is, then that's why.

If you continue to feel frustrated, let us know.
 
I was just thinking how wonderful life was, when Chuck
If you continue to feel frustrated, let us know.
Click to expand...

Oh I am said:
If using NetBEUI solved the problem, then the problem was, most
likely, the firewall (or an LSP / Winsock fix not tried).
Click to expand...

How can this affect the comms between only one PC and not all? I would
have exacted all comms with my nVidia PC to be affected.

Here's the output of 'netsh winsock show catalog' that you asked me to
do. Run on PC1 only, the one with the nVidia board. I have 'refreshed'
or rebuilt the winsock at least twice...after installing my Realtek
network card.


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1012
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1013
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] SEQPACKET 4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] DATAGRAM 4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_{9470EF23-A69A-4E94-A608-F7B0F055C364}] SEQPACKET 5
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -5
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_{9470EF23-A69A-4E94-A608-F7B0F055C364}] DATAGRAM 5
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -5
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_NdisWanNbfOut{5203C91D-6274-4523-9EDF-4372EFA5A4EB}]
SEQPACKET 6
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\Nbf_NdisWanNbfOut{5203C91D-6274-4523-9EDF-4372EFA5A4EB}]
DATAGRAM 6
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1020
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1021
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] SEQPACKET
3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1022
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] DATAGRAM
3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1023
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{83B38E2B-D649-4AF9-89B9-319D34AA386A}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1024
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{83B38E2B-D649-4AF9-89B9-319D34AA386A}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1025
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{881D645F-12DC-4C23-B008-7D423AF37EF0}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1026
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{881D645F-12DC-4C23-B008-7D423AF37EF0}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1027
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0




--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,

I'd be grateful if you could look over the output of 'netsh winsock
show catalog' in my previous message.

TIA.


--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,

I'd be grateful if you could look over the output of 'netsh winsock
show catalog' in my previous message.

TIA.
Click to expand...

Hi Guy,

I'll use the Winsock enumeration from my one workgroup computer, which has no
special network components. This is pretty close to baseline.

####### Start

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{17977DB7-58BE-4500-B84B-304D9D82FD31}] SEQPACKET 0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1038
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{17977DB7-58BE-4500-B84B-304D9D82FD31}] DATAGRAM 0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1039
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3B6F355E-0FDE-4618-8E02-725904C9E32E}] SEQPACKET 4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1040
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3B6F355E-0FDE-4618-8E02-725904C9E32E}] DATAGRAM 4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1041
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{ABE1143C-2029-4AE5-8894-2915F7A0F789}] SEQPACKET 1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1042
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{ABE1143C-2029-4AE5-8894-2915F7A0F789}] DATAGRAM 1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1043
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{481012E9-6F98-411D-A3E4-3839A42E481E}] SEQPACKET 2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1044
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{481012E9-6F98-411D-A3E4-3839A42E481E}] DATAGRAM 2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1045
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8E91B3C2-4AE1-48D1-A459-9F686EE93F81}] SEQPACKET 3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1046
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8E91B3C2-4AE1-48D1-A459-9F686EE93F81}] DATAGRAM 3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1047
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C56BAAC4-54FA-48E8-8EDC-C99FB4DF3CAD}] SEQPACKET 5
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1048
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -5
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C56BAAC4-54FA-48E8-8EDC-C99FB4DF3CAD}] DATAGRAM 5
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1049
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -5
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3DF3312A-3647-4CB2-A63F-9E5DC57C49F5}] SEQPACKET 6
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1050
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3DF3312A-3647-4CB2-A63F-9E5DC57C49F5}] DATAGRAM 6
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1051
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -6
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA) Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0

####### End

Both my computer, and yours, have the same number of components. We both have
the same complement of Description and Entry Type. We have one major
difference: My computer shows \Device\NetBT_Tcpip_ (NetBT transport) for MSAFD
NetBIOS; yours shows \Device\Nbf_NdisWanNbfOut (NetBEUI I believe) for that
description. All Catalog Entry IDs for the MSAFD NetBIOS are different too.

If we're going to compare our enumerations successfully, I think you'll have to
restore TCP/IP as the networking component, and remove NetBEUI. Then run thru
the LSP / Winsock repair process again.
<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

Then let's look at "browstat status" and Winsock enumerations as a pair.
 
Hi Chuck,
If we're going to compare our enumerations successfully, I think you'll have to
restore TCP/IP as the networking component, and remove NetBEUI. Then run thru
the LSP / Winsock repair process again.
Click to expand...

I don't know why, but the whole thing is working!

I did as you suggested above...no change.

I then ran the network setup wizard to 'clear the decks' as it were
and the whole network stopped dead. I could use shortcuts though, but
could not access the network via the workgroup name. Event log showed
7023 error, BUT a look in services showed the computer browser service
running. I had also made the error of disabling the firewall service
(see MSKB 889320).

I re-enabled the service and restarted the browser service and all was
well. I have written the above in case somebody else finds it helpful.

Chuck, I have enclosed the logs as you requested and I would be
grateful if you could give them a look over to see if anything
significant had changed. I swear <right hand goes up> that I have
never installed any component of the nVidia firewall software.

################browser status######



Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
Browsing is active on domain.
Master browser name is: TARDIS_2
Master browser is running build 2600
1 backup servers retrieved from master TARDIS_2
\\TARDIS_2
There are 3 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}

##########################################



#####################Winsock enumeration############



Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]
Provider ID:
{11058240-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 2
Protocol: 1000
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1025
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1026
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] SEQPACKET
3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1027
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FEDDA13E-F505-439E-91CB-6BF87A73BAD2}] DATAGRAM
3
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1028
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{83B38E2B-D649-4AF9-89B9-319D34AA386A}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1029
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{83B38E2B-D649-4AF9-89B9-319D34AA386A}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1030
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{881D645F-12DC-4C23-B008-7D423AF37EF0}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1031
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{881D645F-12DC-4C23-B008-7D423AF37EF0}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1032
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol
Provider ID:
{E02DAAF0-7E9F-11CF-AE5A-00AA00A7112B}
Name Space: 1
Active: 1
Version: 1


#############################################

Even though things are fixed <touches wood> I'd love to know why!

Check your mail <g>.


--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Hi Chuck,


I don't know why, but the whole thing is working!

I did as you suggested above...no change.

I then ran the network setup wizard to 'clear the decks' as it were
and the whole network stopped dead. I could use shortcuts though, but
could not access the network via the workgroup name. Event log showed
7023 error, BUT a look in services showed the computer browser service
running. I had also made the error of disabling the firewall service
(see MSKB 889320).

I re-enabled the service and restarted the browser service and all was
well. I have written the above in case somebody else finds it helpful.

Chuck, I have enclosed the logs as you requested and I would be
grateful if you could give them a look over to see if anything
significant had changed. I swear <right hand goes up> that I have
never installed any component of the nVidia firewall software.

################browser status######



Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
Browsing is active on domain.
Master browser name is: TARDIS_2
Master browser is running build 2600
1 backup servers retrieved from master TARDIS_2
\\TARDIS_2
There are 3 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}

##########################################



#####################Winsock enumeration############
Click to expand...
Even though things are fixed <touches wood> I'd love to know why!

Check your mail <g>.
Click to expand...

Guy,

I think we need to discuss what a firewall is. The legendary firewall would be
one that blocks specific network traffic. By default, it is open, and passes
all traffic.

Modern firewalls, used by more cautious network experts, permit only specified
network traffic. By default, they are closed, and pass no traffic.

My suspicion is that the nForce hardware firewall falls in the latter category.
If you don't run the firewall manager, it will pass only a minimum of traffic,
probably just enough for you to surf to the nVidia website and get software
upgrades.

Right now, you're running IPX/SPX, as well as NetBT. That's OK, as long as you
don't depend upon any firewalls, or other products that filter IP, to protect
you. IPX/SPX bypasses firewalls. IP, IPX/SPX, and NetBEUI are different
protocols. Read my comparison.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html
 
I was just thinking how wonderful life was, when Chuck
My suspicion is that the nForce hardware firewall falls in the latter category.
If you don't run the firewall manager, it will pass only a minimum of traffic,
probably just enough for you to surf to the nVidia website and get software
upgrades.
Click to expand...

I would have sworn 110% it was not installed. I always turned down the
offer to install them/it when asked said:
Right now, you're running IPX/SPX, as well as NetBT.
Click to expand...

I used WinSock XP Fix 1.2.exe from a link on your site IIRC. I did not
install anything else. Could the various LSP/WinSock rebuilding tools
not produce the same end result?

I had not used WinSock XP fix before on this PC, but used other
programs/methods several times. If the nVidia firewall was indeed the
culprit, the rebuilds did not fix the issue as it existed after all
the rebuilds.

The bindings to file sharing and client for networks shows only
TCP/IP. I cannot find IPX/SPX anywhere in order to uninstall it.

I'm going to do some TCP/IP building tool testing and see what
different results I get.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
I was just thinking how wonderful life was, when Chuck


I would have sworn 110% it was not installed. I always turned down the


I used WinSock XP Fix 1.2.exe from a link on your site IIRC. I did not
install anything else. Could the various LSP/WinSock rebuilding tools
not produce the same end result?

I had not used WinSock XP fix before on this PC, but used other
programs/methods several times. If the nVidia firewall was indeed the
culprit, the rebuilds did not fix the issue as it existed after all
the rebuilds.

The bindings to file sharing and client for networks shows only
TCP/IP. I cannot find IPX/SPX anywhere in order to uninstall it.

I'm going to do some TCP/IP building tool testing and see what
different results I get.
Click to expand...

Guy,

As I note in my article, various folks have written here in the past and pointed
out that, where tool A didn't do anything, tool B fixed the problem. But A and
B seems to change, with every report.

So look at the procedure that I outline. It's based upon experience here and in
various $payjob experiences.
<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

Now it's possible that the various procedures vary in effectiveness based upon
the uniqueness of each computer needing help.
<http://nitecruzr.blogspot.com/2005/10/computer-uniqueness.html>
http://nitecruzr.blogspot.com/2005/10/computer-uniqueness.html

I have had other folks here report as you do "I don't see network component X in
one place, though it shows up somewhere else". In some cases, you have to
install then uninstall. Then you end up running the entire LSP / Winsock
sequence.

So you have all of the diagnostics that I can recommend. Make changes, and test
after each change. And please let us know what you find out. Especially if you
read about it elsewhere.
 
I was just thinking how wonderful life was, when Chuck
So you have all of the diagnostics that I can recommend. Make changes, and test
after each change. And please let us know what you find out.
Click to expand...

Confirmed that all TCP/IP rebuilders all include IPX/SPX. Initially,
only one of my three PCs had it.

As you have informed me that it is a security risk vis-a-vis
firewalls, I have removed it on all PCs (slaps head as should have
remembered install in order to uninstall trick).

As all is working well, and I have got quite a bit of training, I
shall re-enable and reinstall the nVidia ethernet adaptor and see if
that buggers things up or not. I shall report back here either way.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
I was just thinking how wonderful life was, when Chuck


Confirmed that all TCP/IP rebuilders all include IPX/SPX. Initially,
only one of my three PCs had it.

As you have informed me that it is a security risk vis-a-vis
firewalls, I have removed it on all PCs (slaps head as should have
remembered install in order to uninstall trick).

As all is working well, and I have got quite a bit of training, I
shall re-enable and reinstall the nVidia ethernet adaptor and see if
that buggers things up or not. I shall report back here either way.
Click to expand...

All right, Guy! Have at it!
 
I was just thinking how wonderful life was, when Chuck
All right, Guy! Have at it!
Click to expand...

Sorry for the delay. nVidia ethernet being used with my LAN working
100%. Refused offer to install firewall components (as always).

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
 
Back
Top