Re: NetBios over TCP/IP

OK, I have the following: the 8 steps above, cdiag output from laptop -
stalled at the enumeration step,
Other items I have tried and the results from them, and cdiag output from
desktop.

For each of these 4 host personalities, x:
main - ping no response, net view error 53
192.168.1.100 - ping OK, net view error 53
t30 - ping OK - net view "The server service is not started"
192.168.1.101 - ping OK, net view error 53

----------------------------
Cdiag - laptop:
CDiagnosis V1.34
Start diagnosis for T30

Enumerate Shares

The Server service is not started.

Is it OK to start it? (Y/N) [Y]:

----------------------
Tried other steps:
----------------------
To fix a corrupted LSP / Winsock in Windows XP pre-SP2:

1 Backup and delete the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
2 Reboot.
3 Open the network connections folder, right click your network connection,
and click Properties.
4 Click Install | Protocol | Add.
5 Click "Have Disk...", type "\windows\inf" in the box, and click OK.
6 Click "Internet Protocol (TCP/IP)", then click OK.
7 Reboot.

No effect, same error - not accessible... not have permission...
----------------------
netsh winsock reset catalog
- >command not found
----------------------
Using Microsoft Article ID : 299357

netsh int ip reset c:\resetlog.txt
->checking for another fwkern instance...
and creted the log - seemed to complete, but no effect
----------------------
uninstalled and re-installed the network card - no effect
----------------------
Using Microsoft Article ID : 811259

netdiag /test:winsock /v
->all tests passed except:
NetBT transports tests.......Failed
Lists of NetBT transports currently configured:
[FATAL] No NetBT transports are configured.
->??? not sure what to do with this information
----------------------
Used the Msinfo32 program
Components/Network/Protocol.
Additional items were present (e.g.MSAFD nwlnkipx [IPX])
Other items were as recommended
----------------------
cdiag output for desktop computer:

CDiagnosis V1.34
Start diagnosis for MAIN

Enumerate Shares


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

H$ H:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

J$ J:\ Default share

Movies J:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Workfile H:\
Printer3 My Documents\*.pdf Spooled Creates Adobe PDF

Printer4 USB001 Spooled hp officejet 6100 series

Printer5 LPT1: Spooled HP LaserJet 8000 Series PS

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\MAIN

The command completed successfully.


Full Targets main 192.168.1.100 t30 192.168.1.101 127.0.0.1

Target main

"MAIN ping main"

Pinging Main [192.168.1.100] with 32 bytes of data:Reply from 192.168.1.100:
bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms

TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:

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

Shared resources at main



Share name Type Used as Comment

-------------------------------------------------------------------------------
Movies Disk
Printer3 Print Creates Adobe PDF
Printer4 Print hp officejet 6100 series
Printer5 Print HP LaserJet 8000 Series PS
SharedDocs Disk
Workfile Disk
The command completed successfully.


Target 192.168.1.100

"MAIN ping 192.168.1.100"

Pinging 192.168.1.100 with 32 bytes of data:Reply from 192.168.1.100:
bytes=32 time<1ms TTL=128Reply from 192.168.1.100: bytes=32 time<1ms

TTL=128Reply from 192.168.1.100: bytes=32 time<1ms TTL=128Reply from
192.168.1.100: bytes=32 time<1ms TTL=128Ping statistics for 192.168.1.100:

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

Shared resources at 192.168.1.100



Share name Type Used as Comment

-------------------------------------------------------------------------------
Movies Disk
Printer3 Print Creates Adobe PDF
Printer4 Print hp officejet 6100 series
Printer5 Print HP LaserJet 8000 Series PS
SharedDocs Disk
Workfile Disk
The command completed successfully.


Target t30

"MAIN ping t30"

Ping request could not find host t30. Please check the name and try again.
"MAIN net view t30"


Target 192.168.1.101

"MAIN ping 192.168.1.101"

Pinging 192.168.1.101 with 32 bytes of data:Request timed out.Request timed
out.Request timed out.Request timed out.Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
"MAIN net view 192.168.1.101"


Target 127.0.0.1

"MAIN 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=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from

127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms
TTL=128Ping 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
"MAIN net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
Movies Disk
Printer3 Print Creates Adobe PDF
Printer4 Print hp officejet 6100 series
Printer5 Print HP LaserJet 8000 Series PS
SharedDocs Disk
Workfile Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"MAIN ping www.yahoo.com"

Pinging www.yahoo.akadns.net [68.142.226.36] with 32 bytes of data:Reply
from 68.142.226.36: bytes=32 time=110ms TTL=51Reply from 68.142.226.36:

bytes=32 time=112ms TTL=51Reply from 68.142.226.36: bytes=32 time=107ms
TTL=51Reply from 68.142.226.36: bytes=32 time=106ms TTL=51Ping

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

Maximum = 112ms, Average = 108ms
Target 66.94.230.32

"MAIN ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32
time=24ms TTL=52Reply from 66.94.230.32: bytes=32 time=21ms

TTL=52Reply from 66.94.230.32: bytes=32 time=21ms TTL=52Reply from
66.94.230.32: bytes=32 time=23ms TTL=52Ping statistics for 66.94.230.32:

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

"MAIN ping 192.168.1.1"

Pinging 192.168.1.1 with 32 bytes of data:Reply from 192.168.1.1: bytes=32
time<1ms TTL=150Reply from 192.168.1.1: bytes=32 time<1ms

TTL=150Reply from 192.168.1.1: bytes=32 time<1ms TTL=150Reply from
192.168.1.1: bytes=32 time<1ms TTL=150Ping statistics for 192.168.1.1:

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 MAIN


"Chuck" wrote:

On Mon, 20 Feb 2006 18:59:26 -0800, John Gregory
<JohnGregory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Mon, 20 Feb 2006 11:02:32 -0800, John Gregory
<JohnGregory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Sun, 19 Feb 2006 19:22:27 -0800, John Gregory
<JohnGregory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Jeffrey Randow [MVP]" wrote:

I think that this is a bug. It is probably enabled, but ipconfig will
be showing it as disabled...

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300986&sd=tech
and see if you have NetBIOS over TCP/IP connectivity.

Have a pleasant day.

--
Jeffrey Randow (jeffreycentex@xxxxxxxxx)
Windows Networking MVP
http://www.networkblog.net


On Sun, 19 Feb 2006 15:04:27 -0800, John Gregory
<JohnGregory@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I enabled NetBIOS over TCP/IP for the LAN connection that I am using (the
wireless connection is disabled). The end result is the same, ipconfig/all
shows NetBIOS over TCP/IP - disabled.

I tried uninstalling both the LAN and wireless adapters, reinstalled them
(disabling the wirelees which I do not use at home). Again, same result.

I can see other computers on my network, but they can not see me.

Any other ways to enable NetBIOS over TCP/IP ?

Thank you for your help

"Steve Winograd [MVP]" wrote:

In article <etmhv193ccr0htqp56abhae5925g2f97ts@xxxxxxx>, "Jeffrey
Randow [MVP]" <jeffreycentex@xxxxxxxxx> wrote:
From the ChicagoTech FAQ:

I have enable NetBIOS over TCP/IP but ipconfig /all shows NetBIOS over
TCP/IP disable.

For some reasons, you have enabled NetBIOS over TCP/IP on W2K/XP but
using ipconfig /all still shows NetBIOS over TCP/IP disable. The
alternative solution will be installing NetBEUI to all computers.

http://www.chicagotech.net/nettroublshooting.htm#I%20have%20enable%20NetBIOS%20over%20TCP/IP%20but%20ipconfig%20/all%20shows%20NetBIOS%20over%20TCP/IP%20disable.

Have a pleasant day.

Hi, Jeffrey. I recommend not installing NetBEUI. It's an unsupported
protocol in Windows XP, which means that Microsoft hasn't tested it,
doesn't guarantee that it will work, and doesn't give technical
support on it. In my experience, installing a second network protocol
in Windows XP is likely to cause even more problems.

To the original poster: Make sure that you're enabling NetBIOS over
TCP/IP on the right connection, and set it to "Enable", not "Default".
If that doesn't solve the problem, try un-installing and re-installing
the network adapter in Device Manager.

If you do install NetBEUI, un-bind file sharing from TCP/IP on all
computers, as I show here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

I followed the instuctions on the article, and did not achieve anything
usefull. Ipconfig/all still shows NetBios over TCP/IP - disabled, and the
nbtstat results are "NetBT is not bound to any devices". Unfortunately, the
article does not say what to do with this particular piece of information.

I can ping it with both the IP and computer name and get an immediate reply,
tracert with both the IP and computer name also shows a connection in one hop
which is as expected.

net view gives me an error 53. I tried LSP Fix, and it shows everything is
OK, I am still looking. I still think this may be related to the disabled
NetBios over TCP/IP, but am still looking.

John,

If Jeffrey is right, and NBT is in fact enabled, even though it shows in
ipconfig as disabled, you could have 1 or 2 other problems. Any of these
problems could block name resolution.

One of the most common causes of this problem would be a misconfigured or
overlooked personal firewall, or other security component. There are several
other possibilities too, and any might be the cause of your problem. Read this
article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Note that LSP-Fix is only one of several LSP repair procedures. Depending upon
the state of your Winsock, any one of the repairs may work better (or only) than
the others.
<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

As I was going through the diagnostic steps suggested, I noticed that from
the desktop, I can see the workgroup and the desktop computer, but not the
laptop (the one that has NetBios over Tcp/IP disabled. The funny thing is
that I see exactly the same from the laptop - the laptop does not even show
up in the workgroup when looking at itself.

I still get the same no access error when I try to access the desktop from
the laptop.

I also used the Winsock replacement tool as well. As for a personal
firewall, I have not been able to find one, the Norton anti-virus does not
seem to have a firewall built in. I am out of ideas where to look next.

I ran Cdiag, but it never seemed to finish. Are there more detailed
instructions for the use of this tool? (I am rapidly getting into new
territory for my current experience level)

Thank you for your help with this

John,

I'm still learning how to write instructions for using CDiag. Right now, see:
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>
http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html

Let's see what's wrong. Can you post your copy of CDiag.cmd, that you are
running, here?

What version of NAV do you have? Is it part of Norton Internet Security?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

I have the NAV Corporate edition, version 9.0.0.338. I have also ran the
Everest program, and it did not find any Firewall programs running. I ran
the Cdiag on both computers - it finished successfully on the desktop, but is
still running on the laptop. As you requested, I have entered the code below.

Thank you again for your help with this.

My pleasure, John.

The code looks spot on. If it hasn't finished running yet, it's either hung,
stalled, or has exited and you didn't notice. No way it takes over 5 minutes to
run.

I think you still have a problem with your network - either the Winsock, or
TCP/IP itself. You said that you tried LSP-Fix and "the Winsock replacement
tool". That's 2 out of 6 possible procedures. Many times, the last in the 6
produces results. Once or twice, someone has tried all 6, one supposedly made
changes, and they've tried all 6 again, whereupon another of the 6 finished the
repair, in the second pass. Be persistent.

Or try doing the commands in CDiag by hand.
For each of these 4 host personalities, x:
main 192.168.1.100 t30 192.168.1.101
"ping " x
"net view " x
IOW, do 8 tests, and report on the failures. If nothing odd in those 8, then
I'll disassemble the other tests so we can try them by hand.

Take a look at the CDiag output from the desktop, to see what I'm discussing.

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

.

Relevant Pages

  • Re: SQLSMS - Cannot Connect SQL Server 2000
    ... On the right-side make sure TCP/IP is enabled. ... I take it the NewXP computer can ping the laptop by both IP ... Rick Byham, SQL Server Books Online ...
    (microsoft.public.sqlserver.setup)
  • Re: File and print sharing problems
    ... You're missing half the point of CDiag - including the names, ... Now when I try to map a folder from my desktop to my laptop (wanderer) I ... results with no WINS server on the laptop. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Selling my soul to the devil is the next step...
    ... Look at CDiag ... for LAPTOP, Target TARDIS_2. ... Swap router ports for NUMBER_1 and LAPTOP back, ... Swap router ports for NUMBER_1 and TARDIS_2 back, ...
    (microsoft.public.windowsxp.network_web)
  • Re: One-way connection: networked XP/2000 PCs
    ... >>>though...CHERYL can ping itself, it just can't connect to itself via ... From CDiag earlier: ... >CHERYL had no problem pinging itself. ... I posted both logs. ...
    (microsoft.public.windowsxp.network_web)
  • Re: One-way connection: networked XP/2000 PCs
    ... >>re-running the original 3 I had tried). ... Here is an example of trying to ping itself: ... > "CHERYL ping CHERYL" ... Well, after running the CDiag scripts earlier, I uninstalled NIS per your ...
    (microsoft.public.windowsxp.network_web)