Re: Can't enable NetBIOS over TCP/IP


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

--
Cheers,
Chuck, MS-MVP [Windows - Networking]

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.

















.

Loading