Can't enable NetBIOS over TCP/IP

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have this kinda hokey network (Host is a XP Home SP1 - Client runs Win98)
that has worked fairly well for 4 years, aside from having to run the Wizard
once in a while 'cos it forgets its Workgroup name. Recently it stopped
working, and the Wizard can't fix it. Shared files only show up on the
machine they're stored on, packets are sent but none are rec'd and it
"Cannot connect network drive"s. I tried Repair this connection and got the
following message "The following steps of the repair operation failed:
Renewing the IP address., Purging and reloading the remote cache name table
of NetBT., Sending Name Release packets to WINS and then starting Refresh."
I have no idea what to do about any of these.

I ran ipconfig on the host. Here is the log:


Windows IP Configuration Host Name . . . . . . . . . . . . :
operator-83sp12 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 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3 Dhcp Enabled. .
.. . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158 Subnet Mask . . .
.. . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Here is the ipconfig.txt from the client:
Windows 98 IP Configuration Host Name . . . . . . . . . : PLAYROOM DNS
Servers . . . . . . . . : Node Type . . . . . . . . . : Broadcast NetBIOS
Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. .
.. . . : No NetBIOS Resolution Uses DNS : No0 Ethernet adapter : Description .
.. . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter NDIS5
Driver Physical Address. . . . . . : 00-04-5A-64-DE-61 DHCP Enabled. . . . .
.. . . : Yes IP Address. . . . . . . . . : 169.254.58.188 Subnet Mask . . . .
.. . . . : 255.255.0.0 Default Gateway . . . . . . : DHCP Server . . . . . .
.. . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server .
.. . : Lease Obtained. . . . . . . : 06 22 07 12:13:50 PM Lease Expires . . .
.. . . . :

Assuming that having NetBIOS over TCP/IP disabled is at least part of the
problem, I did this:
Control Panel>Network Connections>Local Area Connection\Properties\General
tab\This connection uses the following items\Internet
Protocol(TCP/IP)\Properties\General tab\Advanced button\WINS tab. WINS
addresses box is empty, Enable LMHOSTS lookup box is checked, NetBIOS setting
- Enable NetBIOS over TCP/IP is selected.

Is there somewhere else I must go to enable NetBIOS?
 
Pinging results from XP machine:

C:\> ping playroom >C:\pinglog1.txt
Ping request could not find host playroom. Please check the name and try
again.

C:\> ping 169.254.58.188 >C:\pinglog2.txt
Pinging 169.254.58.188 with 32 bytes of data:

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

Ping statistics for 169.254.58.188:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping operator-83sp12 >C:\pinglog3.txt


Pinging operator-83sp12 [169.254.127.158] with 32 bytes of data:

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

Ping statistics for 169.254.127.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging results from Win98 Machine:

C:\> ping playroom >C:\pinglog1.txt


Pinging playroom [169.254.58.188] with 32 bytes of data:

Reply from 169.254.58.188: bytes=32 time<10ms TTL=128
Reply from 169.254.58.188: bytes=32 time<10ms TTL=128
Reply from 169.254.58.188: bytes=32 time<10ms TTL=128
Reply from 169.254.58.188: bytes=32 time<10ms TTL=128

Ping statistics for 169.254.58.188:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping operator-83sp12 >C:\pinglog2.txt
Unknown host operator-83sp12.

C:\> ping 169.254.127.158 >C:\pinglog3.txt


Pinging 169.254.127.158 with 32 bytes of data:

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

Ping statistics for 169.254.127.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
 
I have this kinda hokey network (Host is a XP Home SP1 - Client runs Win98)
that has worked fairly well for 4 years, aside from having to run the Wizard
once in a while 'cos it forgets its Workgroup name. Recently it stopped
working, and the Wizard can't fix it. Shared files only show up on the
machine they're stored on, packets are sent but none are rec'd and it
"Cannot connect network drive"s. I tried Repair this connection and got the
following message "The following steps of the repair operation failed:
Renewing the IP address., Purging and reloading the remote cache name table
of NetBT., Sending Name Release packets to WINS and then starting Refresh."
I have no idea what to do about any of these.

I ran ipconfig on the host. Here is the log:


Windows IP Configuration Host Name . . . . . . . . . . . . :
operator-83sp12 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 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3 Dhcp Enabled. .
. . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158 Subnet Mask . . .
. . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Here is the ipconfig.txt from the client:
Windows 98 IP Configuration Host Name . . . . . . . . . : PLAYROOM DNS
Servers . . . . . . . . : Node Type . . . . . . . . . : Broadcast NetBIOS
Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. .
. . . : No NetBIOS Resolution Uses DNS : No0 Ethernet adapter : Description .
. . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter NDIS5
Driver Physical Address. . . . . . : 00-04-5A-64-DE-61 DHCP Enabled. . . . .
. . . : Yes IP Address. . . . . . . . . : 169.254.58.188 Subnet Mask . . . .
. . . . : 255.255.0.0 Default Gateway . . . . . . : DHCP Server . . . . . .
. . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server .
. . : Lease Obtained. . . . . . . : 06 22 07 12:13:50 PM Lease Expires . . .
. . . . :

Assuming that having NetBIOS over TCP/IP disabled is at least part of the
problem, I did this:
Control Panel>Network Connections>Local Area Connection\Properties\General
tab\This connection uses the following items\Internet
Protocol(TCP/IP)\Properties\General tab\Advanced button\WINS tab. WINS
addresses box is empty, Enable LMHOSTS lookup box is checked, NetBIOS setting
- Enable NetBIOS over TCP/IP is selected.

Is there somewhere else I must go to enable NetBIOS?

That SHOULD do it, as far as simply Enabling it. But their are other
prerequisites.

I bet that you have a service not running.
<http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html>
http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html

Should either computer have Internet access?
<http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html>
http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html
 
Browstat produces no output. I downloaded it from Durawell and Stanford
(both because I thought maybe the first one was corrupt - Pchuck says in his
blog that it's 40K and I only got 19K the first time, but I got 19K from the
2nd. site too). Does this mean something, or am I doing something wrong?
 
Chuck said:

Thanks for taking an interest, Chuck. PChuck's Network has been a Godsend
(This morning I didn't know I could Ping!)
You were right - ICF/ICS service was manual and stopped. Unfortunately,
starting it hasn't changed anything, and
Yes, the XP machine is connected to the internet right now, and I'm
experiencing no issues with the connection. Strange that the first run of
ipconfig included in my first post didn't list the connection - I just ran
ipconfig after starting the ICF/ICS service and the connection's listed now
(log attached).


Windows IP Configuration



Host Name . . . . . . . . . . . . : operator-83sp12

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 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.127.158

Subnet Mask . . . . . . . . . . . : 255.255.0.0

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

NetBIOS over Tcpip. . . . . . . . : Disabled



PPP adapter uniserve:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 207.200.152.119

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 207.200.152.119

DNS Servers . . . . . . . . . . . : 216.113.192.3

216.113.192.4

NetBIOS over Tcpip. . . . . . . . : Disabled

Too bad CPSServewon't diagnose XP Home - would it help to run it on the
Win98 machine? - is there an alternative that will work on XP Home?
 
Thanks for taking an interest, Chuck. PChuck's Network has been a Godsend
(This morning I didn't know I could Ping!)
You were right - ICF/ICS service was manual and stopped. Unfortunately,
starting it hasn't changed anything, and
Yes, the XP machine is connected to the internet right now, and I'm
experiencing no issues with the connection. Strange that the first run of
ipconfig included in my first post didn't list the connection - I just ran
ipconfig after starting the ICF/ICS service and the connection's listed now
(log attached).


Windows IP Configuration



Host Name . . . . . . . . . . . . : operator-83sp12

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 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.127.158

Subnet Mask . . . . . . . . . . . : 255.255.0.0

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

NetBIOS over Tcpip. . . . . . . . : Disabled



PPP adapter uniserve:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 207.200.152.119

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 207.200.152.119

DNS Servers . . . . . . . . . . . : 216.113.192.3

216.113.192.4

NetBIOS over Tcpip. . . . . . . . : Disabled

Too bad CPSServewon't diagnose XP Home - would it help to run it on the
Win98 machine? - is there an alternative that will work on XP Home?

You can run CPSServ on any Windows XP or Vista computer. But unfortunately, not
on Windows 9x - "services" don't exist on Windows 9x.

CPSServ will only show, remotely, services on Windows XP / Vista Pro. XP Home
doesn't run Remote Registry, that's all.

It's always a possible LSP / Winsock corruption (but you can diagnose that only
by fixing the problem).
<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

Beyond that, I'll suggest that you go over Troubleshooting Network
Neighbourhood.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html
 
Thanks for taking an interest, Chuck. PChuck's Network has been a Godsend
(This morning I didn't know I could Ping!)
You were right - ICF/ICS service was manual and stopped. Unfortunately,
starting it hasn't changed anything, and
Yes, the XP machine is connected to the internet right now, and I'm
experiencing no issues with the connection. Strange that the first run of
ipconfig included in my first post didn't list the connection - I just ran
ipconfig after starting the ICF/ICS service and the connection's listed now
(log attached).


Windows IP Configuration



Host Name . . . . . . . . . . . . : operator-83sp12

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 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.127.158

Subnet Mask . . . . . . . . . . . : 255.255.0.0

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

NetBIOS over Tcpip. . . . . . . . : Disabled



PPP adapter uniserve:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 207.200.152.119

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 207.200.152.119

DNS Servers . . . . . . . . . . . : 216.113.192.3

216.113.192.4

NetBIOS over Tcpip. . . . . . . . : Disabled

Too bad CPSServewon't diagnose XP Home - would it help to run it on the
Win98 machine? - is there an alternative that will work on XP Home?

You can run CPSServ on any Windows XP or Vista computer. But unfortunately, not
on Windows 9x - "services" don't exist on Windows 9x.

CPSServ will only show, remotely, services on Windows XP / Vista Pro. XP Home
doesn't run Remote Registry, that's all.

It's always a possible LSP / Winsock corruption (but you can diagnose that only
by fixing the problem).
<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

Beyond that, I'll suggest that you go over Troubleshooting Network
Neighbourhood.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

And rerun the Network Setup Wizard. Select:
This computer connects directly to the Internet. The other computers on my
network connect to the Internet through this computer.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost
 
Deleted for brevity by Simpleton

You can run CPSServ on any Windows XP or Vista computer. But unfortunately, not
on Windows 9x - "services" don't exist on Windows 9x.

CPSServ will only show, remotely, services on Windows XP / Vista Pro. XP Home
doesn't run Remote Registry, that's all.

It's always a possible LSP / Winsock corruption (but you can diagnose that only
by fixing the problem).
<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

Beyond that, I'll suggest that you go over Troubleshooting Network
Neighbourhood.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

And rerun the Network Setup Wizard. Select:
This computer connects directly to the Internet. The other computers on my
network connect to the Internet through this computer.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost

Re: cpsserv. I read (from your blog) "CPSServ does not diagnose XP Home, as
well as Win2000..." What you wrote was "CPSServ does not diagnose XP Home as
well as Win2000...". The comma makes all the difference! Log follows, with
additions, by me, inside asterisks because I went through the list in
Administrative Tools\Services and turned on pretty much all of them. After
seeing the CPSServ log, I went back and all those services CPSServ couldn't
find were listed as Started -Auto except RemoteRegistry ('cos I'm running XP
Home,right?) and Browser.

Start CPSServ V1.10 - OPERATOR-83SP12

Find Computer Browser ("browser")
No active service named browser found.

Find DHCP Client ("dhcp")
No active service named dhcp found. *Started-Auto*

Find TCP/IP NetBIOS Helper ("lmhosts")
No active service named lmhosts found. *Started-Auto*


Find Remote Registry ("remoteregistry")
No active service named remoteregistry found.

Find Server ("server")
No active service named server found. *Started-Auto*

Find WF / ICS ("sharedaccess")
No active service named sharedaccess found. *ICF/ICS Started-Auto*

Find Workstation ("workstation")
No active service named workstation found. *Started-Auto*

End CPSServ V1.10 - OPERATOR-83SP12

BTW, the link you have for SysInternals downloads has changed. It's
www.microsoft.com\technet\sysinternals\Networking\PsTools.mspx

On to the next step - Troubleshooting Network Neighbourhood. There's
something about RestrictAnonymous - mine was set to 2. It's changed to 0 now.

Ran the Wizard as per instructions (I should tell you that I have 1394
connection for my camcorder, that the Wizard insists on bridging if I let it
pick what's best, so I have to manually select my internet connection). New
ipconfig and ping logs follow. Interesting that the Win98 machine can now
find the XP machine by name, but not vice versa.

XP machine logs:


Windows IP Configuration



Host Name . . . . . . . . . . . . : operator-83sp12

Primary Dns Suffix . . . . . . . :

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

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.1

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

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

NetBIOS over Tcpip. . . . . . . . : Disabled

C:\> ping playroom >pinglog1.txt
Ping request could not find host playroom. Please check the name and try
again.



C:\>ping 192.168.0.237 >pinglog2.txt
Pinging 192.168.0.237 with 32 bytes of data:

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

Ping statistics for 192.168.0.237:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Win98 Machine logs:



Windows 98 IP Configuration

Host Name . . . . . . . . . : PLAYROOM.mshome.net
DNS Servers . . . . . . . . : 192.168.0.1
Node Type . . . . . . . . . : Mixed
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter
NDIS5 Driver
Physical Address. . . . . . : 00-04-5A-64-DE-61
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.237
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 06 23 07 10:06:21 PM
Lease Expires . . . . . . . : 06 30 07 10:06:21 PM



C:\>ping operator-83sp12 >pinglog1.txt
Pinging operator-83sp12.mshome.net [192.168.0.1] with 32 bytes of data:

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

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Are we there yet?

Cheers yourself, and thanks again.
Ric
 
Deleted for brevity by Simpleton

You can run CPSServ on any Windows XP or Vista computer. But unfortunately, not
on Windows 9x - "services" don't exist on Windows 9x.

CPSServ will only show, remotely, services on Windows XP / Vista Pro. XP Home
doesn't run Remote Registry, that's all.

It's always a possible LSP / Winsock corruption (but you can diagnose that only
by fixing the problem).
<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

Beyond that, I'll suggest that you go over Troubleshooting Network
Neighbourhood.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

And rerun the Network Setup Wizard. Select:
This computer connects directly to the Internet. The other computers on my
network connect to the Internet through this computer.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost

Re: cpsserv. I read (from your blog) "CPSServ does not diagnose XP Home, as
well as Win2000..." What you wrote was "CPSServ does not diagnose XP Home as
well as Win2000...". The comma makes all the difference! Log follows, with
additions, by me, inside asterisks because I went through the list in
Administrative Tools\Services and turned on pretty much all of them. After
seeing the CPSServ log, I went back and all those services CPSServ couldn't
find were listed as Started -Auto except RemoteRegistry ('cos I'm running XP
Home,right?) and Browser.

Start CPSServ V1.10 - OPERATOR-83SP12

Find Computer Browser ("browser")
No active service named browser found.

Find DHCP Client ("dhcp")
No active service named dhcp found. *Started-Auto*

Find TCP/IP NetBIOS Helper ("lmhosts")
No active service named lmhosts found. *Started-Auto*


Find Remote Registry ("remoteregistry")
No active service named remoteregistry found.

Find Server ("server")
No active service named server found. *Started-Auto*

Find WF / ICS ("sharedaccess")
No active service named sharedaccess found. *ICF/ICS Started-Auto*

Find Workstation ("workstation")
No active service named workstation found. *Started-Auto*

End CPSServ V1.10 - OPERATOR-83SP12

BTW, the link you have for SysInternals downloads has changed. It's
www.microsoft.com\technet\sysinternals\Networking\PsTools.mspx

On to the next step - Troubleshooting Network Neighbourhood. There's
something about RestrictAnonymous - mine was set to 2. It's changed to 0 now.

Ran the Wizard as per instructions (I should tell you that I have 1394
connection for my camcorder, that the Wizard insists on bridging if I let it
pick what's best, so I have to manually select my internet connection). New
ipconfig and ping logs follow. Interesting that the Win98 machine can now
find the XP machine by name, but not vice versa.

XP machine logs:


Windows IP Configuration



Host Name . . . . . . . . . . . . : operator-83sp12

Primary Dns Suffix . . . . . . . :

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

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.1

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

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

NetBIOS over Tcpip. . . . . . . . : Disabled

C:\> ping playroom >pinglog1.txt
Ping request could not find host playroom. Please check the name and try
again.



C:\>ping 192.168.0.237 >pinglog2.txt
Pinging 192.168.0.237 with 32 bytes of data:

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

Ping statistics for 192.168.0.237:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Win98 Machine logs:



Windows 98 IP Configuration

Host Name . . . . . . . . . : PLAYROOM.mshome.net
DNS Servers . . . . . . . . : 192.168.0.1
Node Type . . . . . . . . . : Mixed
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter
NDIS5 Driver
Physical Address. . . . . . : 00-04-5A-64-DE-61
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.0.237
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . : 192.168.0.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 06 23 07 10:06:21 PM
Lease Expires . . . . . . . : 06 30 07 10:06:21 PM



C:\>ping operator-83sp12 >pinglog1.txt
Pinging operator-83sp12.mshome.net [192.168.0.1] with 32 bytes of data:

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

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Are we there yet?

Cheers yourself, and thanks again.
Ric

You're closer, Ric. You're getting DHCP settings, and you have a 192.168.0/24
subnet.

Here's the problem with operator-83sp12
NetBIOS over Tcpip. . . . . . . . : Disabled

Windows 98 only uses NetBT name resolution - Direct Hosting is only for Windows
2000 and up.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

So now we gotta figure out why NetBT isn't Enabling.
 
Deleted for brevity by Simpleton


You're closer, Ric. You're getting DHCP settings, and you have a 192.168.0/24
subnet.

Here's the problem with operator-83sp12

Windows 98 only uses NetBT name resolution - Direct Hosting is only for Windows
2000 and up.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

So now we gotta figure out why NetBT isn't Enabling.

So who made the mud stickier as I get closer? The above link took me to
somewhere that told me to run net share. Admin$ and 1 other share (Sorry, I
was up at 3:30 this morning, after working on this 'til 11:15 last night. My
memory isn't great, but it won't get better from here, so I'll remember what
I can - I gotta get up at 2:30 tomorrow) are missing - most likely a virus
got me. print$, IPC$, SharedDocs, and Printer are there.

I followed another link, downloaded and ran Computer Associates' online scan
(That's the site that precisely decribed the symptoms) and it found nothing.
Disappointing, but not surprising - I have run WebRoot's SpySweeper with the
same result, and Norton runs 24-7, does a full scan at 2:00 am every day, and
has found nothing - not that that means much.

I did a reboot to Safe Mode with Networking, ran net share again - same
result. If Admin$ is restored at boottime, something's knocking it out and I
can't find it. Either that or it's not restored. How can I figure out which?

This problem may be leaving the confines of this discussion and going down
the "Woe is me, I got a virus" path. I'll take it to another group with
regret, as this one has been the only reason I got to this point (More
likely, I'll just format and re-install, but I don't like to quit that easy).
A couple of questions remain.

Why does browstat status produce no output? It's not just too fast - I
redirected it and the file's empty.

Why does CPSServ list all those services as "not found", when Administrative
Tools\Services show them all as started?

Following links (Again, sorry - I searched the History and CANNOT find them)
I found KB 889320 (Refers to event ID 7023 - Browser terminates after 5
minutes if Windows Firewall is turned off). My Windows Firewall is turned
off 'cos I don't need it on the LAN and it conflicts with Norton on the
internet, and this is supposed to be an SP2 problem (Like, what isn't?).
I look in my Event log and there's a few Error 7023s in there, but when I
double-click them, the description is "The System Restore Service terminated
with the following error. Access is denied". Yes, System Restore hasn't
worked since about the time the network cratered, but it's not the first
time. It's pretty flaky, and I don't depend on it. I had thought that
Access Denied messages from System Restore and from the Workgroup may be
linked, but I'm still not able to nail it down (this Admin$ thing has me
going - I got to find it).
Any thoughts on why Event ID 7023 has 2 different descriptions? Which one
should I believe?

While in Event Viewer, I see 34 instances today alone of Error 4311 (NetBT -
Initialization failed because driver device could not be created). LAN
Status shows 2h 35m connected, 453 packets sent, 29 rec'd. I never pinged it
in that time, so something's going on. If not connectivity, then what? How
does Send and Receive happen if NetBT initialization failed?

Viruses aside, (although I do think I had/have one - I just haven't found it
yet) I ain't done.

Seeya, Ric.
P.S. In Mission, BC it's 9:53 pm. Real brain function returns Saturday
around noon :<)
 
So now we gotta figure out why NetBT isn't Enabling.
How do we do that? Glad to hear I'm getting closer, but I'm running into
stuff I don't know how to interpret.

I'm a lost cause during the week - Standard "Work too hard, paid too
little". Gotta do what y'gotta do.

CPSServ says services not found, yet Services says they are started. WTF?
(Sorry, I have teenagers - that's what they type when stuff puzzles them)

Browstat status produces no output. Browstat vw 1 produces "Browser only
has 0 transports and you asked for transport 1". Browstat vw 0 produces "The
browser is not bound to transport 0"

Where's the entry/file that contains the information displayed by running
Net Share? Are the the correct entries/lines available so I can see if mine
are wrong? Am I barking up the wrong tree? I found a reference to a
registry entry -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters,
AutoSharServer=1. This value does not exist in my registry. Should it be?
Is it spelled correctly? Will it make a difference? I typed Net Share
Admin$ - the share now appears, but still no folders in the Network Drive
(Properties shows Z: as Disconnected Network Drive - type RAW).

LAN status shows it being connected for almost 3 days, 13,000 packets sent,
3500 rec'd.

I hate to quit without understanding all what happened and how to fix it,
but I want the network up soon.
 
Hey, Ric and Chuck,

I have (had!) the same problem that Ric has. I have two wired pc's with Win2K, and one wireless with WinXP. I've been following everybody's instructions, but nothing has enabled NetBIOS. Ric mentioned that he looked into Event Viewer and saw:
Initialization failed because the
driver device could not be created.
I searched, and found a Microsoft site:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/4390.mspx?mfr=true

I can't find exactly what that page describes, but the key words were:
If enabling the bindings does not correct the
problem, remove the TCP/IP protocol completely,
and then reinstall it.

Ric, I did that and now my machines are connected and NetBIOS over TCP/IP is not disabled (via ipconfig). Furthermore, when I run CPSServ (PSTools), the data are not blank.

I thank you two for carrying on your conversation, and helping me solve my problem. If/when you're successful, Ric, please let me know.

bye,
-jim
(e-mail address removed)





EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
Hey, Ric and Chuck,

I have (had!) the same problem that Ric has. I have two wired pc's with Win2K, and one wireless with WinXP. I've been following everybody's instructions, but nothing has enabled NetBIOS. Ric mentioned that he looked into Event Viewer and saw:
Initialization failed because the
driver device could not be created.
I searched, and found a Microsoft site:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/4390.mspx?mfr=true

I can't find exactly what that page describes, but the key words were:
If enabling the bindings does not correct the
problem, remove the TCP/IP protocol completely,
and then reinstall it.

Ric, I did that and now my machines are connected and NetBIOS over TCP/IP is not disabled (via ipconfig). Furthermore, when I run CPSServ (PSTools), the data are not blank.

I thank you two for carrying on your conversation, and helping me solve my problem. If/when you're successful, Ric, please let me know.

bye,
-jim
(e-mail address removed)

Thanks for pointing that out, Jim. In a problem like this, at this stage, the
proper thing to do is indeed to reset the network stack. I start with my
article about the LSP / Winsock, and TCP after that. Ric, you're welcome to try
the next step in whatever order pleases you.
<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
 
Deleted for brevity by Simpleton
Thanks for pointing that out, Jim. In a problem like this, at this stage, the
proper thing to do is indeed to reset the network stack. I start with my
article about the LSP / Winsock, and TCP after that. Ric, you're welcome to try
the next step in whatever order pleases you.
<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

Sorry I've been absent - another week from hell - 4 pieces of equipment,
$68,500 - Transfer of ownership and insurance, $10,000 - Hours spent prodding
previous owner into making repairs to said equipment (agreed to in May)and
doing paperwork, not counted - Finally getting Office Manager to get mechanic
to return his calls with news that repairs are finished and equipment is
ready to run (at 10:45pm PDT when, in order to run it properly, I needed to
get up at 2:30 am), priceless.

That said, I did spend some time in front of this machine. Thanks for
joining us, Jim. Your being able to solve your problem by looking at mine
gives us all hope, and thanks for the links.

Unfortunately the article you mentioned is specific to Win 2000, and wasn't
much help, although you did mention removing and re-installing TCP/IP. I
tried that from the LAN Properties General tab and got some unexpected stuff.

Chuck, it gave me the option of installing TCP/IP version 6, with a blurb
about it being the latest, greatest and so on. What's that about? I don't
know how to find out if I might be running version 7 and it's still messed
up. Should I install version 6 (after I get whatever version I got right now
to work properly)? I just nuked it and reinstalled whatever was there
before. Didn't work, but it led me to somewhere that talked about resetting
TCP/IP, which caught my eye when reading your piece titled "Problems with the
LSP/Winsock layer in your Network". I think it's what Jim was talking
about. Chuck, don't bury Kb 299357 so far down the list - it's simple and
it works so good - I should have done it sooner. I include the logfile.

I did find Kb Article 842715, which is so drowned out with MS carry-on about
malicious code and format and reinstall Windows it's just about unreadable,
where it talks about the registry entries AutoShareServer and AutoShareWks.
Contained therein:

"b. Locate and then click the following registry sub-key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. If the AutoShareServer and AutoShareWks DWORD values in the
LanmanServer\Parameters sub-key are configured with a value data of 0, change
that value to 1.

Note If these values do not exist, you do not have to create them because
the default behavior is to automatically create the administrative shares."

Not true. Having been unable to create the C$ share using net share (it
worked to create Admin$, and it persists through reboot, yet net share simply
said C$ didn't exist), I created these 2 entries and C$ is now listed in the
output of net share, and persists through reboot. You're right, Chuck - I am
getting closer. Closer to solving the problem maybe, closer to understanding
it?...not so much.

Norton ran a full scan this morning (I told you, I think,that it does every
day) - found nothing.

My Network Places now contains MSHOME, down one level is operator-83sp12,
down one level is all the shares (printer, shared docs, etc) that weren't
there on Friday, but Playroom isn't there.

New results from diagnostics... great news from browstat status and cpsserv,
at least. Not so great from ping.

Start CPSServ V1.10 - OPERATOR-83SP12

Find Computer Browser ("browser")

Checking \\OPERATOR-83SP12...
Found browser on:

\\OPERATOR-83SP12


Find DHCP Client ("dhcp")

Checking \\OPERATOR-83SP12...
Found dhcp on:

\\OPERATOR-83SP12


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\OPERATOR-83SP12...
Found lmhosts on:

\\OPERATOR-83SP12


Find Remote Registry ("remoteregistry")

Checking \\OPERATOR-83SP12... No active service named remoteregistry found.


Find Server ("server")

Checking \\OPERATOR-83SP12...
Found server on:

\\OPERATOR-83SP12


Find WF / ICS ("sharedaccess")

Checking \\OPERATOR-83SP12...
Found sharedaccess on:

\\OPERATOR-83SP12


Find Workstation ("workstation")

Checking \\OPERATOR-83SP12...
Found workstation on:

\\OPERATOR-83SP12

End CPSServ V1.10 - OPERATOR-83SP12

C:\>browstat status

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
Browsing is active on domain.
Master browser name is: OPERATOR-83SP12
Master browser is running build 2600
1 backup servers retrieved from master OPERATOR-83SP12
\\OPERATOR-83SP12
There are 1 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : operator-83sp12
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

PPP adapter uniserve:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 207.200.152.233
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 216.113.192.3
216.113.192.4
NetBIOS over Tcpip. . . . . . . . : Disabled

So I see I'm not there yet. :<{ Oh well... The radio button in
LANProperties\TCP/IP\Properties\...\WINS had changed back to "Default" by
itself. I changed it back to "Enable NetBIOS over TCP" without result.

C:\>ping Playroom
Ping request could not find host playroom. Please check the name and try
again.


C:\>ping 192.168.0.237
Pinging 192.168.0.237 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.237:

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

I did this a few times - it doesn't always lose them all, but always lost 2
or more.


C:\>ping operator-83sp12

Pinging operator-83sp12 [169.254.127.158] with 32 bytes of data:

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

Ping statistics for 169.254.127.158:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

It's 1:00 am - I gotta get some sleep. If I missed anything important
(besides the fact that my computer's messed up!), tell me. I'll check in
tomorrow night, and post whatever's missing.

Thanks, Ric.
 
Deleted for brevity by Simpleton
Thanks for pointing that out, Jim. In a problem like this, at this stage, the
proper thing to do is indeed to reset the network stack. I start with my
article about the LSP / Winsock, and TCP after that. Ric, you're welcome to try
the next step in whatever order pleases you.
<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

Sorry I've been absent - another week from hell - 4 pieces of equipment,
$68,500 - Transfer of ownership and insurance, $10,000 - Hours spent prodding
previous owner into making repairs to said equipment (agreed to in May)and
doing paperwork, not counted - Finally getting Office Manager to get mechanic
to return his calls with news that repairs are finished and equipment is
ready to run (at 10:45pm PDT when, in order to run it properly, I needed to
get up at 2:30 am), priceless.

That said, I did spend some time in front of this machine. Thanks for
joining us, Jim. Your being able to solve your problem by looking at mine
gives us all hope, and thanks for the links.

Unfortunately the article you mentioned is specific to Win 2000, and wasn't
much help, although you did mention removing and re-installing TCP/IP. I
tried that from the LAN Properties General tab and got some unexpected stuff.

Chuck, it gave me the option of installing TCP/IP version 6, with a blurb
about it being the latest, greatest and so on. What's that about? I don't
know how to find out if I might be running version 7 and it's still messed
up. Should I install version 6 (after I get whatever version I got right now
to work properly)? I just nuked it and reinstalled whatever was there
before. Didn't work, but it led me to somewhere that talked about resetting
TCP/IP, which caught my eye when reading your piece titled "Problems with the
LSP/Winsock layer in your Network". I think it's what Jim was talking
about. Chuck, don't bury Kb 299357 so far down the list - it's simple and
it works so good - I should have done it sooner. I include the logfile.

I did find Kb Article 842715, which is so drowned out with MS carry-on about
malicious code and format and reinstall Windows it's just about unreadable,
where it talks about the registry entries AutoShareServer and AutoShareWks.
Contained therein:

"b. Locate and then click the following registry sub-key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. If the AutoShareServer and AutoShareWks DWORD values in the
LanmanServer\Parameters sub-key are configured with a value data of 0, change
that value to 1.

Note If these values do not exist, you do not have to create them because
the default behavior is to automatically create the administrative shares."

Not true. Having been unable to create the C$ share using net share (it
worked to create Admin$, and it persists through reboot, yet net share simply
said C$ didn't exist), I created these 2 entries and C$ is now listed in the
output of net share, and persists through reboot. You're right, Chuck - I am
getting closer. Closer to solving the problem maybe, closer to understanding
it?...not so much.

Norton ran a full scan this morning (I told you, I think,that it does every
day) - found nothing.

My Network Places now contains MSHOME, down one level is operator-83sp12,
down one level is all the shares (printer, shared docs, etc) that weren't
there on Friday, but Playroom isn't there.

New results from diagnostics... great news from browstat status and cpsserv,
at least. Not so great from ping.

Start CPSServ V1.10 - OPERATOR-83SP12

Find Computer Browser ("browser")

Checking \\OPERATOR-83SP12...
Found browser on:

\\OPERATOR-83SP12


Find DHCP Client ("dhcp")

Checking \\OPERATOR-83SP12...
Found dhcp on:

\\OPERATOR-83SP12


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\OPERATOR-83SP12...
Found lmhosts on:

\\OPERATOR-83SP12


Find Remote Registry ("remoteregistry")

Checking \\OPERATOR-83SP12... No active service named remoteregistry found.


Find Server ("server")

Checking \\OPERATOR-83SP12...
Found server on:

\\OPERATOR-83SP12


Find WF / ICS ("sharedaccess")

Checking \\OPERATOR-83SP12...
Found sharedaccess on:

\\OPERATOR-83SP12


Find Workstation ("workstation")

Checking \\OPERATOR-83SP12...
Found workstation on:

\\OPERATOR-83SP12

End CPSServ V1.10 - OPERATOR-83SP12

C:\>browstat status

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
Browsing is active on domain.
Master browser name is: OPERATOR-83SP12
Master browser is running build 2600
1 backup servers retrieved from master OPERATOR-83SP12
\\OPERATOR-83SP12
There are 1 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : operator-83sp12
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

PPP adapter uniserve:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 207.200.152.233
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 216.113.192.3
216.113.192.4
NetBIOS over Tcpip. . . . . . . . : Disabled

So I see I'm not there yet. :<{ Oh well... The radio button in
LANProperties\TCP/IP\Properties\...\WINS had changed back to "Default" by
itself. I changed it back to "Enable NetBIOS over TCP" without result.

C:\>ping Playroom
Ping request could not find host playroom. Please check the name and try
again.


C:\>ping 192.168.0.237
Pinging 192.168.0.237 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.237:

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

I did this a few times - it doesn't always lose them all, but always lost 2
or more.


C:\>ping operator-83sp12

Pinging operator-83sp12 [169.254.127.158] with 32 bytes of data:

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

Ping statistics for 169.254.127.158:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

It's 1:00 am - I gotta get some sleep. If I missed anything important
(besides the fact that my computer's messed up!), tell me. I'll check in
tomorrow night, and post whatever's missing.

Thanks, Ric.

Ric,

IPV6 is an "improvement" to IP, which expands upon the current "IPV4" addressing
scheme ("nnn.nnn.nnn.nnn"). IPV6 and Windows XP file sharing are a known
problem though, so do not install IPV6 if you want to do file sharing.

Now it's good that you at least have Operator able to see its own services, now
you gotta concentrate on seeing Playroom. With Playroom being Windows 98, you
won't have services though, so CPSServ has reached the limits of its
effectiveness for you.

So lets work on one problem at a time.

You can't ping 192.168.0.237 from Operator, because Operator is on 169.254.n.n.

Host Name . . . . . . . . . . . . : operator-83sp12
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158

Did you disable ICS on Operator? Having reset TCP/IP, and hopefully NOT
installed IPV6, you have to go back and rerun the Network Setup Wizard
"This computer connects directly to the Internet. The other computers on my
network connect to the Internet through this computer."
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost

You need to get Operator providing DHCP again, and that's with it running ICS.
So work on that next.

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Chuck said:
Deleted for brevity by Simpleton
Thanks for pointing that out, Jim. In a problem like this, at this stage, the
proper thing to do is indeed to reset the network stack. I start with my
article about the LSP / Winsock, and TCP after that. Ric, you're welcome to try
the next step in whatever order pleases you.
<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

Sorry I've been absent - another week from hell - 4 pieces of equipment,
$68,500 - Transfer of ownership and insurance, $10,000 - Hours spent prodding
previous owner into making repairs to said equipment (agreed to in May)and
doing paperwork, not counted - Finally getting Office Manager to get mechanic
to return his calls with news that repairs are finished and equipment is
ready to run (at 10:45pm PDT when, in order to run it properly, I needed to
get up at 2:30 am), priceless.

That said, I did spend some time in front of this machine. Thanks for
joining us, Jim. Your being able to solve your problem by looking at mine
gives us all hope, and thanks for the links.

Unfortunately the article you mentioned is specific to Win 2000, and wasn't
much help, although you did mention removing and re-installing TCP/IP. I
tried that from the LAN Properties General tab and got some unexpected stuff.

Chuck, it gave me the option of installing TCP/IP version 6, with a blurb
about it being the latest, greatest and so on. What's that about? I don't
know how to find out if I might be running version 7 and it's still messed
up. Should I install version 6 (after I get whatever version I got right now
to work properly)? I just nuked it and reinstalled whatever was there
before. Didn't work, but it led me to somewhere that talked about resetting
TCP/IP, which caught my eye when reading your piece titled "Problems with the
LSP/Winsock layer in your Network". I think it's what Jim was talking
about. Chuck, don't bury Kb 299357 so far down the list - it's simple and
it works so good - I should have done it sooner. I include the logfile.

I did find Kb Article 842715, which is so drowned out with MS carry-on about
malicious code and format and reinstall Windows it's just about unreadable,
where it talks about the registry entries AutoShareServer and AutoShareWks.
Contained therein:

"b. Locate and then click the following registry sub-key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c. If the AutoShareServer and AutoShareWks DWORD values in the
LanmanServer\Parameters sub-key are configured with a value data of 0, change
that value to 1.

Note If these values do not exist, you do not have to create them because
the default behavior is to automatically create the administrative shares."

Not true. Having been unable to create the C$ share using net share (it
worked to create Admin$, and it persists through reboot, yet net share simply
said C$ didn't exist), I created these 2 entries and C$ is now listed in the
output of net share, and persists through reboot. You're right, Chuck - I am
getting closer. Closer to solving the problem maybe, closer to understanding
it?...not so much.

Norton ran a full scan this morning (I told you, I think,that it does every
day) - found nothing.

My Network Places now contains MSHOME, down one level is operator-83sp12,
down one level is all the shares (printer, shared docs, etc) that weren't
there on Friday, but Playroom isn't there.

New results from diagnostics... great news from browstat status and cpsserv,
at least. Not so great from ping.

Start CPSServ V1.10 - OPERATOR-83SP12

Find Computer Browser ("browser")

Checking \\OPERATOR-83SP12...
Found browser on:

\\OPERATOR-83SP12


Find DHCP Client ("dhcp")

Checking \\OPERATOR-83SP12...
Found dhcp on:

\\OPERATOR-83SP12


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\OPERATOR-83SP12...
Found lmhosts on:

\\OPERATOR-83SP12


Find Remote Registry ("remoteregistry")

Checking \\OPERATOR-83SP12... No active service named remoteregistry found.


Find Server ("server")

Checking \\OPERATOR-83SP12...
Found server on:

\\OPERATOR-83SP12


Find WF / ICS ("sharedaccess")

Checking \\OPERATOR-83SP12...
Found sharedaccess on:

\\OPERATOR-83SP12


Find Workstation ("workstation")

Checking \\OPERATOR-83SP12...
Found workstation on:

\\OPERATOR-83SP12

End CPSServ V1.10 - OPERATOR-83SP12

C:\>browstat status

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
Browsing is active on domain.
Master browser name is: OPERATOR-83SP12
Master browser is running build 2600
1 backup servers retrieved from master OPERATOR-83SP12
\\OPERATOR-83SP12
There are 1 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{6236BCCA-530E-4445-A8A2-9BF83D900506}

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : operator-83sp12
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

PPP adapter uniserve:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 207.200.152.233
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 216.113.192.3
216.113.192.4
NetBIOS over Tcpip. . . . . . . . : Disabled

So I see I'm not there yet. :<{ Oh well... The radio button in
LANProperties\TCP/IP\Properties\...\WINS had changed back to "Default" by
itself. I changed it back to "Enable NetBIOS over TCP" without result.

C:\>ping Playroom
Ping request could not find host playroom. Please check the name and try
again.


C:\>ping 192.168.0.237
Pinging 192.168.0.237 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.237:

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

I did this a few times - it doesn't always lose them all, but always lost 2
or more.


C:\>ping operator-83sp12

Pinging operator-83sp12 [169.254.127.158] with 32 bytes of data:

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

Ping statistics for 169.254.127.158:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

It's 1:00 am - I gotta get some sleep. If I missed anything important
(besides the fact that my computer's messed up!), tell me. I'll check in
tomorrow night, and post whatever's missing.

Thanks, Ric.

Ric,

IPV6 is an "improvement" to IP, which expands upon the current "IPV4" addressing
scheme ("nnn.nnn.nnn.nnn"). IPV6 and Windows XP file sharing are a known
problem though, so do not install IPV6 if you want to do file sharing.

Now it's good that you at least have Operator able to see its own services, now
you gotta concentrate on seeing Playroom. With Playroom being Windows 98, you
won't have services though, so CPSServ has reached the limits of its
effectiveness for you.

So lets work on one problem at a time.

You can't ping 192.168.0.237 from Operator, because Operator is on 169.254.n.n.

Host Name . . . . . . . . . . . . : operator-83sp12
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-18-69-ED-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.127.158

Did you disable ICS on Operator? Having reset TCP/IP, and hopefully NOT
installed IPV6, you have to go back and rerun the Network Setup Wizard
"This computer connects directly to the Internet. The other computers on my
network connect to the Internet through this computer."
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html#ICSHost

You need to get Operator providing DHCP again, and that's with it running ICS.
So work on that next.

Sorry to be gone so long. I bought a machine (XP Pro SP2 with COA and CD),
and have been busy trying to keep as much important stuff as possible,
without taking any remnants of any exploit, for July 22nd. (month-end for
June) when I put the new machine into service.

I created a new administrator account, with a new password, then deleted the
old account (told you I'd been busy - amazing how much stuff went missing
when that account was deleted! Apart from a phone no. - in an Outlook
Express local folder named "Stuff to Keep" that completely disappeared -
everything's back to normal. Too bad about the phone no. - a guy who had some
parts for my kid's '65 Valiant. I know where he lives - 1 1/2 hours away,
but the last time I talked to him he was moving 1500 miles away and he didn't
say when. Oh, well. Maybe - if I've got some time - I'll go for a drive.

No, I did not install IPV-6.

For no reason I can discern, Playroom is now fully accessible from Operator.
It just showed up in Network Neighbourhood 2 days ago, and works as good as
it ever did. For as long as it lasts, I don't have a problem - I can access
my accounting program and my bookkeeper/wife (oh, boy) has a ton of
catching-up to do.

Operator is now not accessible from Playroom. It's in Network Neighbourhood,
but clicking it gets a Win98 msg box saying "\\Operator-83-sp12 is not
accessible. The computer or sharename could not be found. Make sure you
typed it correctly, and try again."

Chuck, in my last post, Ping couldn't resolve the name Playroom, but you
misread the ipconfig output. Pinging Operator-83sp12 (169.254.127.158)
worked fine. 192.168.0.237 is Playroom. All the packets were lost.

Now the name Playroom is being resolved, but Playroom can't resolve the name
Operator-83sp12.

As long as Playroom stays accessible from Operator, I'll leave the new
machine out, and try to figure this out. It's 9:30 - I have to get some
sleep. I'll run the diagnostics tomorrow and post the results.

I tell myself, "There's an easy way out of this."
I ask myself, " Why don't you take it?"
I know the answer. 'Cos I will understand if I don't quit. I came on
something talking about something called Process Explorer and
SeRestorePrivelege, which I have never heard of, but I'll bet it has
something to do with why System Restore won't work. Don't have time to
follow it now.

http://dev.newswhat.com/amsg/micros...k/[email protected]

I will understand (when - not if - I have time!).

Thanks for getting me this far, Ric.
 
Sorry to be gone so long. I bought a machine (XP Pro SP2 with COA and CD),
and have been busy trying to keep as much important stuff as possible,
without taking any remnants of any exploit, for July 22nd. (month-end for
June) when I put the new machine into service.

I created a new administrator account, with a new password, then deleted the
old account (told you I'd been busy - amazing how much stuff went missing
when that account was deleted! Apart from a phone no. - in an Outlook
Express local folder named "Stuff to Keep" that completely disappeared -
everything's back to normal. Too bad about the phone no. - a guy who had some
parts for my kid's '65 Valiant. I know where he lives - 1 1/2 hours away,
but the last time I talked to him he was moving 1500 miles away and he didn't
say when. Oh, well. Maybe - if I've got some time - I'll go for a drive.

No, I did not install IPV-6.

For no reason I can discern, Playroom is now fully accessible from Operator.
It just showed up in Network Neighbourhood 2 days ago, and works as good as
it ever did. For as long as it lasts, I don't have a problem - I can access
my accounting program and my bookkeeper/wife (oh, boy) has a ton of
catching-up to do.

Operator is now not accessible from Playroom. It's in Network Neighbourhood,
but clicking it gets a Win98 msg box saying "\\Operator-83-sp12 is not
accessible. The computer or sharename could not be found. Make sure you
typed it correctly, and try again."

Chuck, in my last post, Ping couldn't resolve the name Playroom, but you
misread the ipconfig output. Pinging Operator-83sp12 (169.254.127.158)
worked fine. 192.168.0.237 is Playroom. All the packets were lost.

Now the name Playroom is being resolved, but Playroom can't resolve the name
Operator-83sp12.

As long as Playroom stays accessible from Operator, I'll leave the new
machine out, and try to figure this out. It's 9:30 - I have to get some
sleep. I'll run the diagnostics tomorrow and post the results.

I tell myself, "There's an easy way out of this."
I ask myself, " Why don't you take it?"
I know the answer. 'Cos I will understand if I don't quit. I came on
something talking about something called Process Explorer and
SeRestorePrivelege, which I have never heard of, but I'll bet it has
something to do with why System Restore won't work. Don't have time to
follow it now.

http://dev.newswhat.com/amsg/micros...k/[email protected]

I will understand (when - not if - I have time!).

Thanks for getting me this far, Ric.

Take it one step at a time, Ric.

Process Explorer is an excellent research tool, mostly for knowing what's going
on in the computer in general.
<http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html>
http://nitecruzr.blogspot.com/2006/04/watching-what-your-computer-is-doing.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [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.
 
Back
Top