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

Dr Teeth

unread,

Aug 9, 2006, 4:46:54 PM8/9/06

to

I have three PCs on my LAN, all running Win XP SP2 fully patched.

The problem is that PC1 can not see PC2; PC3 can see PC2; PC1 can see
PC3. To get stuff to PC2, I had to send it via PC3. It is not quite as
simple as that though. That was the case last night before I tried
some further fixes after some Googling.

The hardware seems to be okay. I can ping 127.0.0.1 on all PCs.

Running ipconfig /all shows all data matching. I have run the
Networking wizard on PCs 1&2 without it making any difference,
rebooting after each time.

TCP/IP stacks have been rebuilt using an MS tool from here
http://support.microsoft.com/kb/299357/.

No firewalls active on the LAN.

I have also repaired the LAN connections.

Every parameter that I can think of has been checked and seems to be
the same on each PC.

All permissions are set to full with the same username on all PCs. PC
1+3 are NTFS and PC2 is FAT32

I changed the cables around at the back of my router without changing
the affected PCs.

In fact, I cannot find anything that has changed and the LAN has
worked well for months.

On PC2 clicking on My network Places > MSoft Windows Network > Mshome
produces a dialogue box which says that the list of servers for this
workgroup is not available. There is quite a delay before Mshome
appears.

Doing the same on PC1 and PC3 shows both PC1 and PC3. However, a
shortcut to PC2 is present on PC3 (actual location C:\Documents and
Settings\<user>\NetHood) which does give full access. Transferring
this shortcut to PC1 does not give access to PC2.

Occasionally, an entry for PC2 does show under Mshome, but clicking on
it produces an error saying the network path not being found.

The diagnostic problem is that one PC is not completely borked. It
would be easier to fix than the current situation.

Thank you for reading the above ramblings and hope that they make
enough sense for somebody to point me in the right direction. I'm
completely stumped. Selling my soul to 'the horned one' is my next
step!

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.

Anthony W

unread,

Aug 9, 2006, 5:35:00 PM8/9/06

to

Try a static IP on all 2 machines and setting up a host file in the
windows directory with the information on all 3 computers.

Tony

Dr Teeth

unread,

Aug 9, 2006, 5:59:42 PM8/9/06

to

I was just thinking how wonderful life was, when Anthony W

<techn...@yahoo.com> opened his gob and said:

>Try a static IP on all 2 machines and setting up a host file in the
>windows directory with the information on all 3 computers.

Hi Tony,

All three PCs have static IPs (sorry did not say so earlier). Could
you please give a tad more info on your HOST file idea.

The HOST file on all three PCs is identical and their location is
C:\WINDOWS\system32\drivers\etc on all PCs. The only line (not
commented out, natch) is:-
127.0.0.1 localhost.

A bit more info, I have found that I cannot disable the LAN connection
on PC2, but can on the others.

Chuck

unread,

Aug 10, 2006, 7:49:04 PM8/10/06

to

On Wed, 09 Aug 2006 22:59:42 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Anthony W
><techn...@yahoo.com> opened his gob and said:
>
>>Try a static IP on all 2 machines and setting up a host file in the
>>windows directory with the information on all 3 computers.
>
>Hi Tony,
>
>All three PCs have static IPs (sorry did not say so earlier). Could
>you please give a tad more info on your HOST file idea.
>
>The HOST file on all three PCs is identical and their location is
>C:\WINDOWS\system32\drivers\etc on all PCs. The only line (not
>commented out, natch) is:-
>127.0.0.1 localhost.
>
>A bit more info, I have found that I cannot disable the LAN connection
>on PC2, but can on the others.
>
>TIA.

Guy,

Maybe your symptoms are similar to the other thread. Let's see - why not
provide "browstat status", "ipconfig /all", "net config server", and "net config
workstation", from each computer, and we may be able to diagnose the problem.
Read this article, 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

--
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.

Dr Teeth

unread,

Aug 13, 2006, 5:45:43 PM8/13/06

to

Hi Chuck,

I've been out of town for a couple of days.

I will get back to you with the info that you requested as soon as I
can and I really appreciate your help.

Dr Teeth

unread,

Aug 14, 2006, 9:54:35 AM8/14/06

to

Hi Chuck,

Here's the info you requested. The node type shows as broadcast on PC
2 as I was trying some troubleshooting myself using your site.

I also have an NVidia motherboard here and uninstalled and reinstalled
my drivers here without any effect.

All Pcs are Win XP Pro, SP2, latest patches applied (i.e. including
those from last few days).

Sorry, but my Usenet client is word wrapping (line length limited to
70). I have uploaded the files to my web site if you prefer to read
them unwrapped; they're here http://www.drteeth.co.uk/lan

------------------------------------------------PC1follows------------------------------------------------------------

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{8DE02B6D-A536-44EE-B2DA-A74DA54A52E1}
Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{8DE02B6D-A536-44EE-B2DA-A74DA54A52E1}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{8DE02B6D-A536-44EE-B2DA-A74DA54A52E1}

Windows IP Configuration

Host Name . . . . . . . . . . . . : TARDIS_2

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller

Physical Address. . . . . . . . . : 00-15-F2-4C-D8-87

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254

Lease Obtained. . . . . . . . . . : 14 August 2006 13:58:10

Lease Expires . . . . . . . . . . : 14 August 2006 14:58:10

Computer name \\TARDIS_2
Full Computer name TARDIS_2
User name Guy

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{8DE02B6D-A536-44EE-B2DA-A74DA54A52E1}
(0015F24CD887)

Software version Windows 2002

Workstation domain WORKGROUP
Workstation Domain DNS Name (null)
Logon domain TARDIS_2

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

Server Name \\TARDIS_2
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{8DE02B6D-A536-44EE-B2DA-A74DA54A52E1}
(0015f24cd887)

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

-------------------------------------------------PC2 follows---------

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}

Windows IP Configuration

Host Name . . . . . . . . . . . . : laptop

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x
Family Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-0A-E4-47-A3-96

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254

Lease Obtained. . . . . . . . . . : 14 August 2006 14:16:07

Lease Expires . . . . . . . . . . : 14 August 2006 15:16:07

Computer name \\LAPTOP
Full Computer name laptop
User name Guy

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
(000AE447A396)

Software version Windows 2002

Workstation domain WORKGROUP
Workstation Domain DNS Name (null)
Logon domain LAPTOP

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

Server Name \\LAPTOP
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
(000ae447a396)

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

------------------------------PC3 follows----------------------

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}

Windows IP Configuration

Host Name . . . . . . . . . . . . : number_1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x
Family Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-50-FC-72-4E-B9

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254

Lease Obtained. . . . . . . . . . : 14 August 2006 14:06:25

Lease Expires . . . . . . . . . . : 14 August 2006 15:06:25

Computer name \\NUMBER_1
Full Computer name number_1
User name Guy

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
(0050FC724EB9)

Software version Windows 2002

Workstation domain WORKGROUP
Workstation Domain DNS Name (null)
Logon domain NUMBER_1

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

Server Name \\NUMBER_1
Server Comment

Software version Windows 2002
Server is active on
NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
(0050fc724eb9)
NetbiosSmb (000000000000)

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Okay Chuck, I hope I have not missed anything out. Needless to say, if
anything is not clear, just ask.

Chuck

unread,

Aug 14, 2006, 10:25:15 AM8/14/06

to

On Mon, 14 Aug 2006 14:54:35 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>Hi Chuck,

>
>Here's the info you requested. The node type shows as broadcast on PC
>2 as I was trying some troubleshooting myself using your site.
>
>I also have an NVidia motherboard here and uninstalled and reinstalled
>my drivers here without any effect.
>
>All Pcs are Win XP Pro, SP2, latest patches applied (i.e. including
>those from last few days).
>
>Sorry, but my Usenet client is word wrapping (line length limited to
>70). I have uploaded the files to my web site if you prefer to read
>them unwrapped; they're here http://www.drteeth.co.uk/lan

The word wrap on Usenet is normal, unfortunately. Thanks for your sensitivity
though.

Now, I will work on this with you, if you wish to continue. But I'll ask you to
read my nVidia article, and in particularly the link at the end, which goes to a
post in this forum, which refers to a second thread in this forum, that ended
just last week.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Dr Teeth

unread,

Aug 14, 2006, 11:30:40 AM8/14/06

to

I was just thinking how wonderful life was, when Chuck

<no...@example.net> opened his gob and said:

>Now, I will work on this with you, if you wish to continue. But I'll ask you to
>read my nVidia article, and in particularly the link at the end, which goes to a
>post in this forum, which refers to a second thread in this forum, that ended
>just last week.

I have read the article. I have uninstalled and reinstalled the latest
NVidia drivers and am downloading some previous drivers to see if they
will help.

I'm just puzzled why the problem is limited to two Pcs ( 1+2) on my
LAN whilst PCs 2+3 work 110% normally together.

Chuck

unread,

Aug 14, 2006, 12:06:00 PM8/14/06

to

On Mon, 14 Aug 2006 16:30:40 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>Now, I will work on this with you, if you wish to continue. But I'll ask you to
>>read my nVidia article, and in particularly the link at the end, which goes to a
>>post in this forum, which refers to a second thread in this forum, that ended
>>just last week.
>
>I have read the article. I have uninstalled and reinstalled the latest
>NVidia drivers and am downloading some previous drivers to see if they
>will help.
>
>I'm just puzzled why the problem is limited to two Pcs ( 1+2) on my
>LAN whilst PCs 2+3 work 110% normally together.

Guy,

Do you have nVidia on the others? Did you read the specific instructions
provided by Jack Clarke?

Chuck

unread,

Aug 14, 2006, 12:30:25 PM8/14/06

to

On Mon, 14 Aug 2006 16:30:40 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>Now, I will work on this with you, if you wish to continue. But I'll ask you to
>>read my nVidia article, and in particularly the link at the end, which goes to a
>>post in this forum, which refers to a second thread in this forum, that ended
>>just last week.
>
>I have read the article. I have uninstalled and reinstalled the latest
>NVidia drivers and am downloading some previous drivers to see if they
>will help.
>
>I'm just puzzled why the problem is limited to two Pcs ( 1+2) on my
>LAN whilst PCs 2+3 work 110% normally together.

Guy,

Did you read the specific instructions provided by Jack Clarke?

I see that Laptop and Number_1 both use Realtek. This makes me stronger suspect
that the problem starts with nVidia.

Dr Teeth

unread,

Aug 14, 2006, 6:31:37 PM8/14/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>Did you read the specific instructions provided by Jack Clarke?

I did not see any specific instructions from Jack. It's not just his
head that was spinning.

>I see that Laptop and Number_1 both use Realtek. This makes me stronger suspect
>that the problem starts with nVidia.

I have taken the nVidia completely out of the equation by uninstalling
the NV LAN drivers *and* disabling it in the BIOS. I installed a spare
Realtek card that I had hanging around and the result is the same.
Using the stock MSoft drivers ATM, about to update to latest Realtek
ones.

I shall keep things that way until things get sorted.

One thing that I have noticed with the PC2 (laptop) is that it is not
possible to disable the LAN connection. The 'error disabling
connection' box says that one or more protocols may be used that do
not support plug-and-play or it may have been initiated by another
user or account. This does not explain why PC3 can interact okay with
laptop though.

TIA.

Dr Teeth

unread,

Aug 14, 2006, 7:15:02 PM8/14/06

to

I was just thinking how wonderful life was, when Dr Teeth

<no.email.h...@tardis.com> opened his gob and said:

>I did not see any specific instructions from Jack. It's not just his
>head that was spinning.

Sorry for replying to myself. Chuck, Jacks comments did not apply as I
never installed NVIDIA Firewall and Forceware Network
Access Manager. During a recent uninstall and reinstall of the drivers
as a result of your thread with Jack, I made doubly sure that these
bits did not get installed.

A tad academic now as I'm Realtek powered <g>.

Chuck

unread,

Aug 14, 2006, 9:12:28 PM8/14/06

to

On Tue, 15 Aug 2006 00:15:02 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Dr Teeth

><no.email.h...@tardis.com> opened his gob and said:
>
>>I did not see any specific instructions from Jack. It's not just his
>>head that was spinning.
>
>Sorry for replying to myself. Chuck, Jacks comments did not apply as I
>never installed NVIDIA Firewall and Forceware Network
>Access Manager. During a recent uninstall and reinstall of the drivers
>as a result of your thread with Jack, I made doubly sure that these
>bits did not get installed.
>
>A tad academic now as I'm Realtek powered <g>.

Guy,

I don't think you quite got the experience that Jack related. He installed (or
un installed) drivers, but the drivers for the nVidia NIC were not the problem.
The problem was the firewall itself. And if you look upwards in the thread,
you'll see that I had him enumerate the winsock, as many firewalls are installed
with links in the LSP / Winsock. But no trace of the firewall was seen there.

So you may state that you're nVidia free, and maybe you are. But be very sure,
because Jack was sure for several days. And found out that he had been wrong,
and found nVidia to be the problem.

Anyway, it's your computer. I'm not looking at it with you. So if the problem
isn't the NIC, what's the problem?

Let's look at the updated diagnostics, to start. I install a network
diagnostics script, ccdiag.cmd, on each of my computers, something like
@echo off
@echo Start CCDiag for %computername% >c:\ccdiag.txt
ipconfig /all >>c:\ccdiag.txt
browstat status >>c:\ccdiag.txt
net config server >>c:\ccdiag.txt
net config workstation >>c:\ccdiag.txt
net share >>c:\ccdiag.txt
net view >>c:\ccdiag.txt
@echo End CCDiag for %computername% >>c:\ccdiag.txt
notepad c:\ccdiag.txt

Yet another PChuck script. Maybe it will help us though. I run CCDiag
periodically, when something funky is happening.
<http://nitecruzr.blogspot.com/2005/06/command-window.html>
http://nitecruzr.blogspot.com/2005/06/command-window.html

Dr Teeth

unread,

Aug 15, 2006, 4:21:47 PM8/15/06

to

Hi Chuck,

>So you may state that you're nVidia free, and maybe you are. But be very sure,
>because Jack was sure for several days. And found out that he had been wrong,
>and found nVidia to be the problem.

Even though sure I'm nVidia free [this PC is 6 months old and I have
never installed the firewall software only the ethernet drivers], I
enumerated the TCP/IP stack twice. Once using the command line on your
site and once using the software from MSKB 299357. I had previously
used WinSock XP Fix 1.2.exe as well (before we 'met').

>Anyway, it's your computer. I'm not looking at it with you. So if the problem
>isn't the NIC, what's the problem?

I realise that it is important that I follow a logical route for you
to be able to help me, so I will always do what you ask. I did notice
earlier today that PC1 and PC2 would not show any servers under the
workgroup name *unless* PC3 was switched on. A red herring or vital
clue <g>?

The text of the various ccdiag files are posted below as well as on my
web site www.drteeth.co.uk/lan, to avoid word-wrap.

-----------------PC1----------------------

Start CCDiag for TARDIS_2

Windows IP Configuration Host Name . . . . . . . . . . . . :
TARDIS_2 Primary Dns Suffix . . . . . . . : Node Type
. . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . .
. . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter

Local Area Connection 6: Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC Physical Address. . . . . . . . . :

00-50-FC-72-4E-BC Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . .
. . . . . : 192.168.1.2 Subnet Mask . . . . . . . . . . . :
255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254 DNS Servers .
. . . . . . . . . . : 192.168.1.254 Lease Obtained. . . . . . .

. . . : 15 August 2006 20:20:41 Lease Expires . . . . . . . . .
. : 15 August 2006 21:20:41

Status for domain WORKGROUP on transport

\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}

Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport

\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}

There are 1 domains in domain WORKGROUP on transport

\Device\NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}

Server Name \\TARDIS_2
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)

NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
(0050fc724ebc)

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Computer name \\TARDIS_2

Full Computer name TARDIS_2
User name Guy

Workstation active on
NetbiosSmb (000000000000)

NetBT_Tcpip_{9470EF23-A69A-4E94-A608-F7B0F055C364}
(0050FC724EBC)

Software version Windows 2002

Workstation domain WORKGROUP
Workstation Domain DNS Name (null)
Logon domain TARDIS_2

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

Share name Resource Remark

-------------------------------------------------------------------------------
E$ E:\ Default share
IPC$ Remote IPC
D$ D:\ Default share
C$ C:\ Default share
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin
Y$ Y:\ Default share
F$ F:\ Default share
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Tardis-2 D D:\
test_F F:\
Printer FaxModem (Photo Qualit Spooled Print to this device to
send a pho
Printer2 FaxModem Spooled Print to this device to
send a fax
Printer3 LPT1: Spooled Samsung ML-2250 Series
PCL 6
Printer4 LPT1: Spooled Samsung ML-2250 Series
Printer5 USB001 Spooled Canon i865
The command completed successfully.

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

End CCDiag for TARDIS_2

----------------PC2-----------------------------
Start CCDiag for LAPTOP

Windows IP Configuration Host Name . . . . . . . . . . . . :
laptop Primary Dns Suffix . . . . . . . : Node Type .
. . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . .

. . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter

Local Area Connection 2: Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC Physical Address. . . . . . . . . :
00-0A-E4-47-A3-96 Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . .
. . . . . : 192.168.1.3 Subnet Mask . . . . . . . . . . . :
255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254 DNS Servers .
. . . . . . . . . . : 192.168.1.254 Lease Obtained. . . . . . .

. . . : 15 August 2006 20:24:54 Lease Expires . . . . . . . . .
. : 15 August 2006 21:24:54

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{B267792A-DF96-41C7-A3CF-3E84C1FE17A0}

Software version Windows 2002

Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share
ADMIN$ C:\WINDOWS Remote Admin
IPC$ Remote IPC
Laptop C:\
SharedDocs C:\Documents and Settings\All Users\Documents

The command completed successfully.

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

End CCDiag for LAPTOP

---------------------------PC3--------------------
Start CCDiag for NUMBER_1

Windows IP Configuration Host Name . . . . . . . . . . . . :
number_1 Primary Dns Suffix . . . . . . . : Node Type
. . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . .

. . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter

Local Area Connection: Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC Physical Address. . . . . . . . . :
00-50-FC-72-4E-B9 Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . .
. . . . . : 192.168.1.4 Subnet Mask . . . . . . . . . . . :
255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254 DNS Servers .
. . . . . . . . . . : 192.168.1.254 Lease Obtained. . . . . . .

. . . : 15 August 2006 20:25:29 Lease Expires . . . . . . . . .
. : 15 August 2006 21:25:29

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
Browsing is active on domain.
Master browser name is: NUMBER_1
Master browser is running build 2600
1 backup servers retrieved from master NUMBER_1
\\NUMBER_1
There are 3 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{0DDD7A71-7618-4064-B188-E300B56CA41A}

Software version Windows 2002

Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin
C$ C:\ Default share
DVD on 1 H:\
Number_1 C:\ WinXP-NTFS
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

EPSON R300 USB001 Spooled EPSON R300
Printer Microsoft Document Ima Spooled Microsoft Office Document
Image Wr
The command completed successfully.

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

End CCDiag for NUMBER_1

TIA.

Chuck

unread,

Aug 15, 2006, 6:27:07 PM8/15/06

to

On Tue, 15 Aug 2006 21:21:47 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>Hi Chuck,

>
>>So you may state that you're nVidia free, and maybe you are. But be very sure,
>>because Jack was sure for several days. And found out that he had been wrong,
>>and found nVidia to be the problem.
>
>Even though sure I'm nVidia free [this PC is 6 months old and I have
>never installed the firewall software only the ethernet drivers], I
>enumerated the TCP/IP stack twice. Once using the command line on your
>site and once using the software from MSKB 299357. I had previously
>used WinSock XP Fix 1.2.exe as well (before we 'met').
>
>>Anyway, it's your computer. I'm not looking at it with you. So if the problem
>>isn't the NIC, what's the problem?
>
>I realise that it is important that I follow a logical route for you
>to be able to help me, so I will always do what you ask. I did notice
>earlier today that PC1 and PC2 would not show any servers under the
>workgroup name *unless* PC3 was switched on. A red herring or vital
>clue <g>?

Guy,

All 3 computers recognise NUMBER_1 ("PC3") as the master browser, and all 3
computers are recognising each other's presence. The master browser must be on
for either TARDIS_2 or LAPTOP to see each other. You could make either TARDIS_2
or LAPTOP a backup browser, but as soon as you were to carry that computer away
from the network, so it were to lose connectivity with NUMBER_1, it would elect
itself a master browser. You would end up with a workgroup with 2 master
browsers, ie a segmented workgroup.

Other than that, right now I can see no other problem.

Your original problem reported stated that The problem is that PC1 can not see
PC2; PC3 can see PC2; PC1 can see PC3. That is but 3 relationships out of 6.
How about PC2 to PC1 and PC3, and PC3 to PC1.

Check and make sure that NetBT is consistently set on all 3 computers.
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Or, if you like, we can do relational analysis.
<http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html>
http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html

Take the following code (everything INSIDE the "#####" lines). Please DO NOT
include ANY portion of the "#####" lines. (Please verify computer names and ip
addresses).

1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
3. Run it by Start - Run - "c:\cdiag".
4. Wait patiently.
5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=TARDIS_2 192.168.1.2
set FullTarget2=LAPTOP 192.168.1.3
set FullTarget3=NUMBER_1 192.168.1.4
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.1.254
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets Analysis %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets Analysis %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

##### End CDiag Assembled Code

Dr Teeth

unread,

Aug 16, 2006, 4:12:26 PM8/16/06

to

Hi Chuck,

>All 3 computers recognise NUMBER_1 ("PC3") as the master browser, and all 3
>computers are recognising each other's presence. The master browser must be on
>for either TARDIS_2 or LAPTOP to see each other. You could make either TARDIS_2
>or LAPTOP a backup browser, but as soon as you were to carry that computer away
>from the network, so it were to lose connectivity with NUMBER_1, it would elect
>itself a master browser. You would end up with a workgroup with 2 master
>browsers, ie a segmented workgroup.
>
>Other than that, right now I can see no other problem.

How does one make a PC a master browser? I was not aware that such a
thing existed and am sure (as much as I can be at any rate) that any
two of my PCs could be on and connect/interact 100% with each other,
i.e. a 'master' was not needed.

>Your original problem reported stated that The problem is that PC1 can not see
>PC2; PC3 can see PC2; PC1 can see PC3. That is but 3 relationships out of 6.
>How about PC2 to PC1 and PC3, and PC3 to PC1.

Not exactly correct. PC1 can see both PC2 and PC3. It can only browse
PC3, trying to browse PC2 results in an error, screen captured here:
www.drteeth.co.uk/lan/LANerror.jpg. This also happens when PC2 tries
to connect to PC1; again, the name of the PC is visible. I have
uploaded a diagram of the problem, www.drteeth.co.uk/lan/LANprob.jpg.

>Check and make sure that NetBT is consistently set on all 3 computers.

I can confirm that it is set to 'enabled' on all PCs, I changed them
all from the default.

Here's the outputs of the cdiag.txt files, as usual, I have uploaded
them to my site. In future, do you prefer files here (word-wrapped) or
au naturelle on my web site?

-----------------PC1-------------------------------
CDiagnosis V1.40
Start diagnosis for TARDIS_2
Full Targets TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.254

Over All Analysis

Enumerate Shares

Share name Resource Remark

-------------------------------------------------------------------------------
E$ E:\ Default share
IPC$ Remote IPC
D$ D:\ Default share

Y$ Y:\ Default share

print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

F$ F:\ Default share
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Tardis-2 D D:\

Printer FaxModem (Photo Qualit Spooled Print to this device to
send a pho
Printer2 FaxModem Spooled Print to this device to
send a fax
Printer3 LPT1: Spooled Samsung ML-2250 Series
PCL 6
Printer4 LPT1: Spooled Samsung ML-2250 Series
Printer5 USB001 Spooled Canon i865
The command completed successfully.

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

Full Targets Analysis TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1

Target TARDIS_2

"TARDIS_2 ping TARDIS_2"

Pinging TARDIS_2 [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view TARDIS_2"

Shared resources at TARDIS_2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target 192.168.1.2

"TARDIS_2 ping 192.168.1.2"

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 192.168.1.2"

Shared resources at 192.168.1.2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target LAPTOP

"TARDIS_2 ping LAPTOP"

Ping request could not find host LAPTOP. Please check the name and try
again.

"TARDIS_2 net view LAPTOP"

Target 192.168.1.3

"TARDIS_2 ping 192.168.1.3"

Pinging 192.168.1.3 with 32 bytes of data:

Request timed out.

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"TARDIS_2 net view 192.168.1.3"

Target NUMBER_1

"TARDIS_2 ping NUMBER_1"

Pinging NUMBER_1 [192.168.1.4] with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view NUMBER_1"

Shared resources at NUMBER_1

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 192.168.1.4

"TARDIS_2 ping 192.168.1.4"

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 192.168.1.4"

Shared resources at 192.168.1.4

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 127.0.0.1

"TARDIS_2 ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.254

Target www.yahoo.com

"TARDIS_2 ping www.yahoo.com"

Pinging www.yahoo.akadns.net [209.73.186.238] with 32 bytes of data:

Reply from 209.73.186.238: bytes=32 time=116ms TTL=54

Reply from 209.73.186.238: bytes=32 time=112ms TTL=51

Reply from 209.73.186.238: bytes=32 time=108ms TTL=51

Reply from 209.73.186.238: bytes=32 time=115ms TTL=51

Ping statistics for 209.73.186.238:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 108ms, Maximum = 116ms, Average = 112ms

Target 66.94.230.32

"TARDIS_2 ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Reply from 66.94.230.32: bytes=32 time=179ms TTL=51

Reply from 66.94.230.32: bytes=32 time=181ms TTL=51

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 179ms, Maximum = 181ms, Average = 180ms

Target 192.168.1.254

"TARDIS_2 ping 192.168.1.254"

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for TARDIS_2

--------------------------------PC2-----------------------
CDiagnosis V1.40
Start diagnosis for TARDIS_2
Full Targets TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.254

Over All Analysis

Enumerate Shares

Share name Resource Remark

-------------------------------------------------------------------------------
E$ E:\ Default share
IPC$ Remote IPC
D$ D:\ Default share

Y$ Y:\ Default share

print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin

C$ C:\ Default share

F$ F:\ Default share
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Tardis-2 D D:\

Printer FaxModem (Photo Qualit Spooled Print to this device to
send a pho
Printer2 FaxModem Spooled Print to this device to
send a fax
Printer3 LPT1: Spooled Samsung ML-2250 Series
PCL 6
Printer4 LPT1: Spooled Samsung ML-2250 Series
Printer5 USB001 Spooled Canon i865
The command completed successfully.

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

Full Targets Analysis TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1

Target TARDIS_2

"TARDIS_2 ping TARDIS_2"

Pinging TARDIS_2 [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view TARDIS_2"

Shared resources at TARDIS_2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target 192.168.1.2

"TARDIS_2 ping 192.168.1.2"

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 192.168.1.2"

Shared resources at 192.168.1.2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target LAPTOP

"TARDIS_2 ping LAPTOP"

Ping request could not find host LAPTOP. Please check the name and try
again.

"TARDIS_2 net view LAPTOP"

Target 192.168.1.3

"TARDIS_2 ping 192.168.1.3"

Pinging 192.168.1.3 with 32 bytes of data:

Request timed out.

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"TARDIS_2 net view 192.168.1.3"

Target NUMBER_1

"TARDIS_2 ping NUMBER_1"

Pinging NUMBER_1 [192.168.1.4] with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view NUMBER_1"

Shared resources at NUMBER_1

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 192.168.1.4

"TARDIS_2 ping 192.168.1.4"

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 192.168.1.4"

Shared resources at 192.168.1.4

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 127.0.0.1

"TARDIS_2 ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TARDIS_2 net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.254

Target www.yahoo.com

"TARDIS_2 ping www.yahoo.com"

Pinging www.yahoo.akadns.net [209.73.186.238] with 32 bytes of data:

Reply from 209.73.186.238: bytes=32 time=116ms TTL=54

Reply from 209.73.186.238: bytes=32 time=112ms TTL=51

Reply from 209.73.186.238: bytes=32 time=108ms TTL=51

Reply from 209.73.186.238: bytes=32 time=115ms TTL=51

Ping statistics for 209.73.186.238:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 108ms, Maximum = 116ms, Average = 112ms

Target 66.94.230.32

"TARDIS_2 ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Reply from 66.94.230.32: bytes=32 time=179ms TTL=51

Reply from 66.94.230.32: bytes=32 time=181ms TTL=51

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 179ms, Maximum = 181ms, Average = 180ms

Target 192.168.1.254

"TARDIS_2 ping 192.168.1.254"

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for TARDIS_2

------------------------------PC3------------------------
CDiagnosis V1.40
Start diagnosis for NUMBER_1
Full Targets TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.254

Over All Analysis

Enumerate Shares

Share name Resource Remark

-------------------------------------------------------------------------------
IPC$ Remote IPC
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
ADMIN$ C:\WINDOWS Remote Admin
C$ C:\ Default share
DVD on 1 H:\
Number_1 C:\ WinXP-NTFS
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

EPSON R300 USB001 Spooled EPSON R300
Printer Microsoft Document Ima Spooled Microsoft Office Document
Image Wr
The command completed successfully.

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

Full Targets Analysis TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1

Target TARDIS_2

"NUMBER_1 ping TARDIS_2"

Pinging TARDIS_2 [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view TARDIS_2"

Shared resources at TARDIS_2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target 192.168.1.2

"NUMBER_1 ping 192.168.1.2"

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=3ms TTL=64

Reply from 192.168.1.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 3ms, Average = 0ms

"NUMBER_1 net view 192.168.1.2"

Shared resources at 192.168.1.2

Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Print to this device to send a photo
quality fax.
Printer2 Print Print to this device to send a fax.
Printer3 Print Samsung ML-2250 Series PCL 6
Printer4 Print Samsung ML-2250 Series
Printer5 Print Canon i865
SharedDocs Disk
Tardis-2 D Disk
The command completed successfully.

Target LAPTOP

"NUMBER_1 ping LAPTOP"

Pinging LAPTOP [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view LAPTOP"

Shared resources at LAPTOP

Share name Type Used as Comment

-------------------------------------------------------------------------------
Laptop Disk
SharedDocs Disk
The command completed successfully.

Target 192.168.1.3

"NUMBER_1 ping 192.168.1.3"

Pinging 192.168.1.3 with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view 192.168.1.3"

Shared resources at 192.168.1.3

Share name Type Used as Comment

-------------------------------------------------------------------------------
Laptop Disk
SharedDocs Disk
The command completed successfully.

Target NUMBER_1

"NUMBER_1 ping NUMBER_1"

Pinging number_1 [192.168.1.4] with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view NUMBER_1"

Shared resources at NUMBER_1

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 192.168.1.4

"NUMBER_1 ping 192.168.1.4"

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view 192.168.1.4"

Shared resources at 192.168.1.4

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 127.0.0.1

"NUMBER_1 ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"NUMBER_1 net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.254

Target www.yahoo.com

"NUMBER_1 ping www.yahoo.com"

Pinging www.yahoo.akadns.net [209.73.186.238] with 32 bytes of data:

Request timed out.

Reply from 209.73.186.238: bytes=32 time=121ms TTL=51

Reply from 209.73.186.238: bytes=32 time=108ms TTL=51

Reply from 209.73.186.238: bytes=32 time=103ms TTL=54

Ping statistics for 209.73.186.238:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 103ms, Maximum = 121ms, Average = 110ms

Target 66.94.230.32

"NUMBER_1 ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Request timed out.

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Request timed out.

Reply from 66.94.230.32: bytes=32 time=181ms TTL=51

Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:

Minimum = 180ms, Maximum = 181ms, Average = 180ms

Target 192.168.1.254

"NUMBER_1 ping 192.168.1.254"

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for NUMBER_1

Thanks for your continued support.

Chuck

unread,

Aug 16, 2006, 9:30:12 PM8/16/06

to

On Wed, 16 Aug 2006 21:12:26 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>Hi Chuck,

Guy,

Attached here is fine, generally. Google will provide this for us, with no
problem.

But you could provide us CDiag log for Laptop, instead of for TARDIS_2 twice.

Now the browser issue, and master browser elections, are a lot of fun to deal
with. The NT browser is a peer-peer service, with a master browser being
elected by all of the computers running the browser service. Master browser
conflicts arise when more than one computer elects itself a master browser. Or
sometimes there is no browser to become the master browser. Read my article for
details please.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

Dr Teeth

unread,

Aug 17, 2006, 3:23:09 PM8/17/06

to

I was just thinking how wonderful life was, when Chuck

<no...@example.net> opened his gob and said:

>But you could provide us CDiag log for Laptop, instead of for TARDIS_2 twice.

I wondered when I'd get caught out with that one! here's CDiag log for
Laptop:-

CDiagnosis V1.40
Start diagnosis for LAPTOP

Full Targets TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.254

Over All Analysis

Enumerate Shares

Share name Resource Remark

-------------------------------------------------------------------------------
C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC
Laptop C:\
SharedDocs C:\Documents and Settings\All Users\Documents

The command completed successfully.

Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\LAPTOP
\\NUMBER_1
\\TARDIS_2
The command completed successfully.

Full Targets Analysis TARDIS_2 192.168.1.2 LAPTOP 192.168.1.3 NUMBER_1
192.168.1.4 127.0.0.1

Target TARDIS_2

"LAPTOP ping TARDIS_2"

Ping request could not find host TARDIS_2. Please check the name and
try again.

"LAPTOP net view TARDIS_2"

Target 192.168.1.2

"LAPTOP ping 192.168.1.2"

Pinging 192.168.1.2 with 32 bytes of data:

Request timed out.

Ping statistics for 192.168.1.2:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

"LAPTOP net view 192.168.1.2"

Target LAPTOP

"LAPTOP ping LAPTOP"

Pinging laptop [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"LAPTOP net view LAPTOP"

Shared resources at LAPTOP

Share name Type Used as Comment

-------------------------------------------------------------------------------
Laptop Disk
SharedDocs Disk
The command completed successfully.

Target 192.168.1.3

"LAPTOP ping 192.168.1.3"

Pinging 192.168.1.3 with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"LAPTOP net view 192.168.1.3"

Shared resources at 192.168.1.3

Share name Type Used as Comment

-------------------------------------------------------------------------------
Laptop Disk
SharedDocs Disk
The command completed successfully.

Target NUMBER_1

"LAPTOP ping NUMBER_1"

Pinging NUMBER_1 [192.168.1.4] with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"LAPTOP net view NUMBER_1"

Shared resources at NUMBER_1

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 192.168.1.4

"LAPTOP ping 192.168.1.4"

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"LAPTOP net view 192.168.1.4"

Shared resources at 192.168.1.4

Share name Type Used as Comment

-------------------------------------------------------------------------------
DVD on 1 Disk
EPSON R300 Print EPSON R300
Number_1 Disk WinXP-NTFS
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.

Target 127.0.0.1

"LAPTOP ping 127.0.0.1"

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

"LAPTOP net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment

-------------------------------------------------------------------------------

Laptop Disk
SharedDocs Disk
The command completed successfully.

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.254

Target www.yahoo.com

"LAPTOP ping www.yahoo.com"

Pinging www.yahoo.akadns.net [209.73.186.238] with 32 bytes of data:

Reply from 209.73.186.238: bytes=32 time=119ms TTL=54

Reply from 209.73.186.238: bytes=32 time=118ms TTL=54

Reply from 209.73.186.238: bytes=32 time=119ms TTL=51

Reply from 209.73.186.238: bytes=32 time=118ms TTL=51

Ping statistics for 209.73.186.238:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 118ms, Maximum = 119ms, Average = 118ms

Target 66.94.230.32

"LAPTOP ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=180ms TTL=51

Reply from 66.94.230.32: bytes=32 time=179ms TTL=51

Reply from 66.94.230.32: bytes=32 time=192ms TTL=51

Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 179ms, Maximum = 192ms, Average = 182ms

Target 192.168.1.254

"LAPTOP ping 192.168.1.254"

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

End diagnosis for LAPTOP

Hope it helps.

Thanks.

Chuck

unread,

Aug 18, 2006, 1:32:48 AM8/18/06

to

On Thu, 17 Aug 2006 20:23:09 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>But you could provide us CDiag log for Laptop, instead of for TARDIS_2 twice.
>
>I wondered when I'd get caught out with that one! here's CDiag log for
>Laptop:-

<SNIP>

>Hope it helps.
>
>Thanks.

That it does. The problem - and it's symmetrical - is between LAPTOP and
TARDIS_2. Neither can access the other, in any of 4 tests each. Look at CDiag
for LAPTOP, Target TARDIS_2. Look at CDiag for TARDIS_2, Target LAPTOP.
# Ping by name. Name resolution problem.
# Net View by name. No display (you'll probably see errors in the command
window).
# Ping by IP address. Request times out.
# Net View by IP address. No display (you'll probably see errors in the command
window).

With pings being blocked, both ways, this points to either a physical (cabling /
router) or logical (firewall) problem. Let's test logically, and do this very
methodically please. Read thru instructions first.
1) Swap router ports for 2 cables - say NUMBER_1 and LAPTOP. See if the problem
moves.
2) Swap router ports for NUMBER_1 and LAPTOP back, then swap NUMBER_1 and
TARDIS_2. See if the problem moves.
3) Swap router ports for NUMBER_1 and TARDIS_2 back, then swap Ethernet cables
between NUMBER_1 and LAPTOP. See if the problem moves.
4) Swap Ethernet cables for NUMBER_1 and LAPTOP back, then swap NUMBER_1 and
TARDIS_2. See if the problem moves.

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.

If it's a firewall, we'll think of some more tests. Just do this very
deliberately.

Chuck

unread,

Aug 18, 2006, 11:48:22 AM8/18/06

to

On Thu, 17 Aug 2006 20:23:09 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>But you could provide us CDiag log for Laptop, instead of for TARDIS_2 twice.
>
>I wondered when I'd get caught out with that one! here's CDiag log for
>Laptop:-

<SNIP>

>Hope it helps.
>
>Thanks.

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.

Dr Teeth

unread,

Aug 18, 2006, 11:59:47 AM8/18/06

to

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.

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.

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>.

Chuck

unread,

Aug 18, 2006, 12:37:21 PM8/18/06

to

On Fri, 18 Aug 2006 16:59:47 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>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.
>
>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.
>
>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>.

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

Dr Teeth

unread,

Aug 18, 2006, 12:37:59 PM8/18/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>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.

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].

Dr Teeth

unread,

Aug 18, 2006, 12:40:33 PM8/18/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>What firewalls are "disabled"?

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.

unread,

Aug 19, 2006, 6:21:03 PM8/19/06

to

I was just thinking how wonderful life was, when JClark

<jcl...@nomail.invalid> opened his gob and said:

>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

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>.

JClark

unread,

Aug 19, 2006, 9:26:37 PM8/19/06

to

On Sat, 19 Aug 2006 23:21:03 +0100, Dr Teeth
<no.email.h...@tardis.com> wrote:

>I was just thinking how wonderful life was, when JClark
><jcl...@nomail.invalid> opened his gob and said:
>
>>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
>
>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>.

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

Chuck

unread,

Aug 19, 2006, 9:35:50 PM8/19/06

to

On Fri, 18 Aug 2006 22:26:45 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>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.

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.

Dr Teeth

unread,

Aug 20, 2006, 6:02:16 AM8/20/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>If you continue to feel frustrated, let us know.

Oh I am <g>.

>If using NetBEUI solved the problem, then the problem was, most
>likely, the firewall (or an LSP / Winsock fix not tried).

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

Dr Teeth

unread,

Aug 22, 2006, 3:48:08 PM8/22/06

to

Hi Chuck,

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

TIA.

Chuck

unread,

Aug 22, 2006, 9:32:43 PM8/22/06

to

On Tue, 22 Aug 2006 20:48:08 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>Hi Chuck,

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

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

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.

Dr Teeth

unread,

Aug 23, 2006, 4:23:02 PM8/23/06

to

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.

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############

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: 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>.

Chuck

unread,

Aug 23, 2006, 9:29:30 PM8/23/06

to

On Wed, 23 Aug 2006 21:23:02 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>Hi Chuck,

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

>
>Check your mail <g>.

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

Dr Teeth

unread,

Aug 24, 2006, 3:12:45 PM8/24/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>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.

I would have sworn 110% it was not installed. I always turned down the
offer to install them/it when asked, honest <g>.

>Right now, you're running IPX/SPX, as well as NetBT.

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.

Chuck

unread,

Aug 24, 2006, 4:20:12 PM8/24/06

to

On Thu, 24 Aug 2006 20:12:45 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>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.
>
>I would have sworn 110% it was not installed. I always turned down the
>offer to install them/it when asked, honest <g>.
>
>>Right now, you're running IPX/SPX, as well as NetBT.
>
>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.

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.

Dr Teeth

unread,

Aug 24, 2006, 4:47:19 PM8/24/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>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.

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.

Chuck

unread,

Aug 24, 2006, 8:31:24 PM8/24/06

to

On Thu, 24 Aug 2006 21:47:19 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>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.
>
>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.

All right, Guy! Have at it!

Dr Teeth

unread,

Aug 27, 2006, 10:24:50 AM8/27/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>All right, Guy! Have at it!

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

unread,

Aug 28, 2006, 5:00:50 AM8/28/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>Don't play games please, I
>love jokes, as much as you, but not now.

I'm not, Chuck.

From what you have said there are *only two* options.

1) "as I have said REPEATEDLY, it appears that the "firewall" is

normally closed, not normally open. If you don't install the NAM, and
configure the firewall to PASS SMBs, judging from Jack's threads, you
won't have Windows Networking."

You have also said repeatedly that the firewall is installed silently.

I contend that the above is not the case as according to you, I have
the firewall is installed closed (default) and I have just not
installed the software to configure it. Therefore, again according to
you, my LAN should not be working, but IT IS, perfectly, quickly, and
110%.

Surely the firewall would stop all comms, not just bork a connection
to one PC leaving the other working perfectly as was my case?

Also, as was the case here, the LAN was working and suddenly stopped
without any drivers being installed.

2) No firewall is installed.

If you go back to Jack, you will see that he DID install these extras,
which, according to Jack, ARE the firewall software itself and a
config program, which he was able to uninstall it separately.

>Don't play games please, I love jokes, as much as you, but not now.

Come on Chuck...<g>.

Chuck

unread,

Aug 28, 2006, 10:26:39 AM8/28/06

to

On Mon, 28 Aug 2006 10:00:50 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

So was this the first time that you re installed the drivers? As you said
earlier:

"Refused offer to install firewall components (as always)."

Any idea what you did this time that worked? If the nVidia drivers are able to
configure themselves properly in some cases, but not others, it would help a lot
of people to know this.

I'm hoping that you didn't re install IPX/SPX or NetBEUI, for instance.

Dr Teeth

unread,

Aug 28, 2006, 12:15:43 PM8/28/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>So was this the first time that you re installed the drivers? As you said
>earlier:
>"Refused offer to install firewall components (as always)."

I have never installed these extra bits, and my LAN has worked fine in
the past. I just reinstalled the drivers to get you the verbatim
message that popped up. Jack inferred that he could uninstall the
firewall separately from the nVidia ethernet drivers. The only time I
have installed drivers is to update them.

>Any idea what you did this time that worked?

No, I'm puzzled. However, in a previous posting you asked me to run a
command which would show the components of the WinSock stack and LSPs.
No nVidia component was present. I am not convinced that any firewall
is installed if one refuses to install the 'extras', which to my
reading, is the firewall itself. I am more than happy to run the
executable (without installing anything, natch) and give you a listing
of its contents and try to supply you with the contents of any text
file (e.g.*.inf) to help you see what would be installed.

>If the nVidia drivers are able to
>configure themselves properly in some cases, but not others, it would help a lot
>of people to know this.

AFAIAA, I only installed and only have the ethernet drivers installed,
and not any firewall nor firewall component. How can we check this
once and for all and stay friends <vbg>?

>I'm hoping that you didn't re install IPX/SPX or NetBEUI, for instance.

No way. That would be a cheat. I did not reinstall IPX/SPX or NetBEUI.
All is working as it did and as it should and I don't know why.

Chuck

unread,

Aug 28, 2006, 1:04:05 PM8/28/06

to

On Mon, 28 Aug 2006 17:15:43 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>So was this the first time that you re installed the drivers? As you said
>>earlier:
>>"Refused offer to install firewall components (as always)."
>
>I have never installed these extra bits, and my LAN has worked fine in
>the past.

The original title of this thread is "I'd sell my soul...". You did have
problems at one time?

>>Any idea what you did this time that worked?
>
>No, I'm puzzled. However, in a previous posting you asked me to run a
>command which would show the components of the WinSock stack and LSPs.
>No nVidia component was present. I am not convinced that any firewall
>is installed if one refuses to install the 'extras', which to my
>reading, is the firewall itself. I am more than happy to run the
>executable (without installing anything, natch) and give you a listing
>of its contents and try to supply you with the contents of any text
>file (e.g.*.inf) to help you see what would be installed.

The firewall, Guy, is part of the hardware. You have an nVidia nForce Ethernet
controller with an embedded hardware firewall. I haven't figured out why some
systems show Winsock entries for nVidia components.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
<http://www.nvidia.com/object/IO_13034.html>
http://www.nvidia.com/object/IO_13034.html

>>If the nVidia drivers are able to
>>configure themselves properly in some cases, but not others, it would help a lot
>>of people to know this.
>
>AFAIAA, I only installed and only have the ethernet drivers installed,
>and not any firewall nor firewall component. How can we check this
>once and for all and stay friends <vbg>?

I only argue with my friends. You have Ethernet drivers from what product?

>>I'm hoping that you didn't re install IPX/SPX or NetBEUI, for instance.
>
>No way. That would be a cheat. I did not reinstall IPX/SPX or NetBEUI.
>All is working as it did and as it should and I don't know why.

Well, I had to ask. I'd bet that cleaning up the network stack removed a
problem. Maybe some nVidia drivers, when installed on an otherwise correctly
setup system, will allow SMBs. I don't know.

You and Jack aren't the first folks to have problems, when an nVidia component
is involved - read the nVidia forum discussions. The more folks who do analyse
your problems, as you and Jack have done, the better chance we have of nailing
down the problem itself. And that's why I'm asking.

Dr Teeth

unread,

Aug 28, 2006, 4:06:40 PM8/28/06

to

I was just thinking how wonderful life was, when Chuck
<no...@example.net> opened his gob and said:

>The firewall, Guy, is part of the hardware. You have an nVidia nForce Ethernet
>controller with an embedded hardware firewall.

I thought that it only worked if drivers were installed.

> You have Ethernet drivers from what product?

nVidia nForce Networking Controller.

>You and Jack aren't the first folks to have problems, when an nVidia component
>is involved - read the nVidia forum discussions. The more folks who do analyse
>your problems, as you and Jack have done, the better chance we have of nailing
>down the problem itself. And that's why I'm asking.

Of course you should ask.

Chuck

unread,

Aug 28, 2006, 6:08:33 PM8/28/06

to

On Mon, 28 Aug 2006 21:06:40 +0100, Dr Teeth <no.email.h...@tardis.com>
wrote:

>I was just thinking how wonderful life was, when Chuck

><no...@example.net> opened his gob and said:
>
>>The firewall, Guy, is part of the hardware. You have an nVidia nForce Ethernet
>>controller with an embedded hardware firewall.
>
>I thought that it only worked if drivers were installed.
>
>> You have Ethernet drivers from what product?
>
>nVidia nForce Networking Controller.
>
>>You and Jack aren't the first folks to have problems, when an nVidia component
>>is involved - read the nVidia forum discussions. The more folks who do analyse
>>your problems, as you and Jack have done, the better chance we have of nailing
>>down the problem itself. And that's why I'm asking.
>
>Of course you should ask.

You installed nVidia drivers. The drivers let your nVidia nForce Ethernet
controller / hardware firewall work. What specific functions are activated when
you install "Ethernet drivers", and / or "firewall drivers", are at the
discretion of nVidia. Both the Ethernet and firewall controllers are on the
same board - the nVidia nForce.

What we know (based upon what nVidia tells us) is that the nForce contains an
ISCA certified hardware firewall. Anything else that we know is based upon what
nVidia customers like Jack and you have observed.
<http://www.nvidia.com/object/IO_13034.html>
http://www.nvidia.com/object/IO_13034.html

I just spent a few minutes briefly searching the nVidia web site, to see if
there's a release log for the nVidia drivers, and no luck. So I have no idea
what, if anything has been changed. Let's just be thankful that you are now
happy.