Author Topic: XP Home, cannot access itself by using IP  (Read 2387 times)

Offline Normunds

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
XP Home, cannot access itself by using IP
« on: September 08, 2005, 06:27:22 AM »
My objective is being able to use shared resources on this XP Home box. I could see them at some time... Problem is -- I fail to access the box even locally by IP, for example \\10.0.0.1, while I see it when i enter it's name \\packardbell

Symptoms & tried things:
1) I can ping this computer either by name or by IP. If I use "net view \\packardbell" locally, it shows the list of shares, if "net view \\10.0.0.1" - it produces error 1231 (but the error messages are in French, so they do not ring the bell anyway here). BTW, if I run "net view \\packardbell" from remote machine I get error 53.
2) i can see the shares locally if I type in explorer address bar \\packardbell, but not if I type \\10.0.0.1
I do not really care to use NetBIOS names, IP would be fine for me, but that's exactly what fails.
3)I have NetBIOS over TCP/IP explicitly enabled in LAN connection, yet when I run "ipconfig /all" it shows it as disabled.
4) when I run "nbtstat -n" I get the French equivalent of "Failed to access NetBT Driver -- NetBT may not be loaded". I found two bits of advice: 1) that I need admin account to run this -- I have it 2) HKLM\System\CurrentControlSet\Services\NetBT Start value should be 2; changed it to 2 -- no effect. BTW its marked to depend on service Tcpip only.
As for admin rights, I got another mention of this when I was installing ZoneAlarm -- when it nicely finished installing and everything closed, I saw a popup that said that the program failed to update all parameters in registry and that I should switch to an admin account and re-do the installation. Well, I have an admin account... On XP Home it's pretty simple. I tried to create another account and use (to run nbtstat -n) it with the same results.
5) tried disabling, then uninstalling firewall. No effect. Still running Symantec Antivirus.
6)I can map locally the shared drive \\packardbell\dvd-rw, but not as \\10.0.0.1\dvd-rw; besides I cannot map from this (bad) computer shared resources on other machines even when using "login as different user". And it happens so quick I suspect it does not really attempt to search. On the other hand in other cases when i tried to map drives on other machines from the bad box, it sort of pretended trying to connect to other machine, but asked for username/password and did not accept the correct one no matter what.
7) and yes, I have another machine in that workgroup. On both machines I see only the local one. Neither is aware of another computer in the workgroup. Both are on the same switch.

I have read and tried a number of interesting suggestions in the thread:
Networking 2 XP, but all that were solution to different problems.

I'm sure that if i manage enable this computer see itself by IP, I should be able to do that also remotely. But no luck. Yet

Offline Normunds

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
XP Home, cannot access itself by using IP
« Reply #1 on: November 12, 2005, 06:10:56 PM »
it seems the problem must have been caused by some spyware or something that had modified registry. Not me, right?

I noticed that I was getting 4311 NetBT error upon loading. And I was lucky to stumble upon a post, where the guy found somebody had modifyied bindings for NetBT... So it was:
HKLM\SYSTEM\CurrentControlSet\Services\NetBT\TransportBindName -- I got it empty for some reason. When I entered "\Device\" as I had it on other XP box the problem disappeared.

Cheers, Normunds

Offline haka

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
XP Home, cannot access itself by using IP
« Reply #2 on: December 02, 2005, 08:25:22 PM »
Thanks for the tip,

I had a problem where my XP machine stopped connecting to the network, but could still ping
and be pinged from other computers.


When I ran repair on the local area connection Status box -> Support tab -> Repair - I got errors.

When I ran "nbtstat -a" from command promt it always failed with an netbt error.

Tried everything to get it to work.

Setting HKLM\SYSTEM\CurrentControlSet\Services\NetBT\TransportBindName to value "/Devce" finally fixed it.

Also presume it was spyware  caused it.