Recommended Posts

this maybe belongs under xp home

i am unable to connect to the two xp home machines we have via explorer \\COMPUTER_NAME

i can connec fine via IP address

why is this?

i cant ping name either... (even though it shows up under network)

if i click on network in vista, all the computers show up, name and all

this drives me nuts

this is not an issue with the xp pro machines or other vista machines... just xp home

thank you

pj

Link to comment
https://www.neowin.net/forum/topic/636586-computername-not-accessible-ip-only/
Share on other sites

im away from the machines, cannot test now.. but will try...

the xp home machines CAN access the vistas by COMPUTERNAME but not vice=versa...

i really dont think it is a dns/cache problem (seeing as though this has never been an issue on any other machine... but is with the TWO xp home systems i have)

but will give it a go when i get home

any other ideas?

pj

  nazgul said:
Can those XP machines access the Vista machine by name? Can they access each other?

The first thing to try is clearing the DNS cache. Open up a command prompt, type in "ipconfig /flushdns", hit enter. See if you can get to them after that.

dns flush did not do anything...

pj

  pjrey said:
dns flush did not do anything...

pj

Try entering this at a command prompt: "nbtstat -A ip-of-the-pcs"

Be sure to make the A uppercase. Run this for each of the PCs you're trying to get to. This will tell you what the PC thinks the NetBIOS name of those PCs. If it comes back with no name, or the wrong name, you can run this command to clear the cache: "nbtstat -R" (again, be sure the R is uppercase).

^ exactly! ;)

Nor does dns have anything to with broadcasting for a netbios name.. The subnet or broadcast domain the machines are on could be an issue.

Is the name even valid for netbios? For example, I just named a machine "xp-pro7891123456" which is over the 15 character limit of netbios.. So I can not view it with its netbios name

C:\>net view \\xp-pro7891123456

System error 53 has occurred.

but I can view it by IP

Shared resources at \\192.168.1.168

Share name Type Used as Comment

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

test Disk

The command completed successfully.

There are lots of reasons why you might not be able to resolve a machine by netbios.. what workgroup they are in is not one of them, nor is what dns they are using.

The node type of the machine looking for them, and if your running wins or not - sure these are possible problems. Is netbios over tcp/ip enabled even?

What exact error do you get when you do from a command line net view \\computername

i find it odd that it is only a problem with the two xp home machines all the rest work fine (5 other xp pro machines, and one other vista, besides mine... all work just fine...)

the machine names of the two XP home machines are, ' family ' and ' chef '

i have tried accessing the XP home machines from other computers besides mine... the error is the same on the others as well

i will test net view \\chef when i get home on friday

pj

still no go

i can view it by IP only... netbios over tcp/ip is ENABLED (everything matches my setup on my laptop)

i did a nbtstat -A _COMPUTER_IP

and it came back with the correct name, chef UNIQUE REGISTERED

net view \\chef gives me error 53 no network path

i dont know what else to try

i goto properties on the xp home machine, it says the comptuer name, the NetBios name...

all checks out just fine...

any other ideas?

thanks

pj

(again, this happens only on the xp home machines.. )

Edited by pjrey

And these home machines are on the same network as the other machines? ie 192.168.?.x/24

And your not using wins on your network? And the machines are set to use broadcast to find names, ie what is the node type of the machines trying to use access \\chef

You do not have anything in your lmhost file that would point to the wrong place for this name?

What is the output of your nbtstat -c before and after you try and access net view \\chef

Sorry but here is not netbios (and please pull off netbios is security concern), not workgroup, i think is only authentication in the xp home (if i read correctly) cuz xp home not have the same target than pro (wich is desinged with a domain controller in the network), home is for a home environment wich is likely not have a domain controller and vista cant access to the xp home machine. Look to change the admin pass (i prefer to use this acc, less problems) in the vista pc and try but i need to remeber the xp home will ask the pass over and over (dont have the service to remember, i dont remember the name LOL)...to my is pointless cuz xp home is not good to network, a lot of problems to see others pcs and access.

Sorry for my english if any is wrong.

I dont understand the part wich vista not access the xp home...wich is the problem? cuz the poster say he cant access the xp home via vista (this is posted in the vista section and the poster wonders if is better to post in xp home)

And a good fix always concern to go over wich the pcs says, maybe the pc say error 53 but is that correct, and why?

This is wich respect to you position in the forum, of course.

To be honest I can not make heads are tails of your post.. In general vista has no issues accessing XP home or Pro, it seemed to me you were trying to say vista has known issues with accessing xp, etc.

He can access it using IP -- so how is it a auth issue? If it was an access denied problem they would get error 5, not 53

All remote access to xp home is SFS, so WTF does the admin password have to do with anything??

Error 53 is normally a name resolution issue!

http://www.microsoft.com/technet/prodtechn...g.mspx?mfr=true

We need to understand how he is doing name resolution.. Does he have dns or wins running, does he have entries in his lmhost file? How are his clients trying to resolve -- ie what node type are they set at.

If he is just trying to broadcast for names -- are these machines on the same segment.

It clearly has nothing to do with AUTH, since he states he can access the shares using \\ipaddress

I have a similar issue on 3 vista machines on the local network. Tried most/all of the suggestions here and to no result. Doesnt really bother me accessing them via ip-addresses but I wonder if it represents a problem

A problem in your setup yes. Out of the box you put 2 computers on the same network, allow for the traffic on their firewalls - and setup file sharing. With no other method of name resolution -- they will broadcast for the netbios names.

If this is not working on your network - then you have dicked something up, or have something mis configured or blocked by firewalls, etc.

I can duplicate the problem quite easy.. I setup a machine to use P-node and pointed it to a wins server that is OFF. Now the machine will not broadcast for name ie \\computername

post-14624-1211121645_thumb.jpg

Here is info on how netbios name resolution works

http://technet.microsoft.com/en-us/library...27013.aspx#EFAA

Another way I can duplicate this problem is to only allow port 445 on the machines firewall vs allowing 137 UDP as well.. This will allow to access \\ipcomputername but not \\computername

But this does not allow for nbtstat -A to work.. So it would seem the OP could be on different segments.

Edited by BudMan
  BudMan said:
So what was your problem??

how do i check node type.. it says unique...

i cannot run net view \\chef

i cannot ping chef

i can run net view \\ip of chef

and ping ip of chef

tell me what to try

wins is not enabled, netbios is

i tried with firewall off

i ran nbtstat -c on the chef system

it showed the IP of the computer, and 2 connections, me and NAS harddrive...

yes, they are all within 192.168.1.X

i am able to ping chef ON the chef machine... but i cannot ping chef on my system (vista), or any other (running xp pro)

i dont know what else to look for/try

thanks for posting

pj

EDIT: when i just do NET VIEW (no ip or host) it shows my NAS drives and chef (from my vista laptop)

its showing up

if i do net view chef

i get an error 53.

Edited by pjrey
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft will finally stop shoving Edge down your throat, on one condition by David Uzondu Avid Windows users must be familiar with the dirty tactics Microsoft employs to push its Edge browser. It's a song as old as time; remember when Internet Explorer was primarily used as a tool to download Chrome or Firefox because it was the only thing available? Shortly after IE died, Edge inherited that legacy, becoming the browser you often had to use just to get the browser you actually wanted. Even Microsoft knows this: For years, we have endured the relentless pop-ups after updates, third parties being blocked from changing the default browser on Windows 11, banners appearing when you dare visit a competitor's download page, a fake "how to uninstall Edge" guide, and links within Windows apps that just had to open in Edge, regardless of your set preferences. Microsoft has announced it is dialing back some of this aggressive behavior, promising a reprieve from the constant Edge bombardment. But (and it's a pretty big but) this only applies if you're in the EEA. This shift isn't Microsoft suddenly having a profound change of heart and deciding to respect user choice out of the goodness of its heart. No, this is all thanks to the Digital Markets Act, a major EU rule that targets big online platforms, what they call "gatekeepers", because these companies have a huge impact on how the digital market works. So, what is actually changing for users in the EEA? For starters, Microsoft Edge will not prompt you to set it as the default browser unless you actually open it directly, like by clicking its icon on the taskbar. This specific change started rolling out with Edge version 137.0.3296.52. Other Microsoft apps will also stop bugging you to reinstall Edge if you dared to remove it, with updates for this rolling out in June to Windows 10 and 11. And speaking of default browsers, this is where a significant improvement lies. Previously, hitting "Set default" for your browser in Windows was half baked, only grabbing basic web links like http and https and HTML files. Now, if you're in the EEA, setting your default browser will also cover more obscure link types like ftp and "read," plus a wider array of web-related file formats such as .mht, .svg, .xml, and even .pdf files, provided your chosen browser says it can handle them. The Bing app and those Windows Widgets, which previously had a nasty habit of ignoring your browser choice, will also start opening web links in your default browser. Hallelujah. Users in the EEA will also gain the ability to uninstall the Microsoft Store entirely later this year, though apps previously installed from it will still receive updates. Windows Search is also getting an upgrade in the EEA. Right now, searching from the taskbar mostly just sends you to Bing, no matter what browser you use. But for users in the EEA, other apps will be able to plug into Windows Search and show web results too. If an app registers as a web search provider, it'll start working as soon as you install it. You'll also be able to see results from multiple providers in the search interface, not just Bing. The usual scoping tabs will still be there if you want to filter things, but the default view will be more varied. And yes, you'll even be able to reorder the providers in Settings. These changes are already in Windows Insider builds and are expected to roll out to Windows 10 and 11 in early June.
    • A few things I am wondering about for S3: A.  What's Pike doo gonna look like this time around....yea I've watched the trailers & it looks poofed up, but still.... B. When will the unintelligible, physco-babbling Pelia go away (or at least learn how to speak English properly, without that crappy, slurred accent that sounds like she's on crack, Mary Jane, & LSD at the same time) ?  Hopefully Scotty's arrival will mean her departure is near.... C.  When do we get to see more of the stunningly gorgeous No. 1, preferably in regular/civilian clothes that show off her physical attributes better ? D. Is Spock EVER gonna get laid properly, human style ?  I feel certain that Christine could make any Vulcan-human horizontal bomp a thing to remember for a LONG time  E.  Can we PLEEEEEEZE get rid of the hatchet-head/buzz cut hair styles on Ortega & anyone else that has it....  But otherwise, as Pike says:  HIT IT !  
    • RIP Hotlips..... IMHO, her best scenes were the few where she dared to let her REAL feminine side show through from underneath all that crappy, worn-torn soldier facade that she had to keep up with...she instantly lit up every room or situation where she was featured !
    • Helium Converter 3.3.69.0 by Razvan Serea Helium Converter is a free Windows utility for converting audio files between formats such as MP3, FLAC, AAC, WMA, OGG, and WAV. It supports batch conversion, preserves or updates tag information, and offers features like volume normalization. With a simple interface, it's ideal for users who need to convert large music libraries quickly and efficiently while retaining metadata. Helium Converter key features: Supports file formats: MP3, MP4, FLAC, AAC, M4A, WMA, WAV, OGG, OPUS, APE.... Batch conversion for large music libraries Preserves and edits metadata (ID3, Vorbis Comments, etc.) Volume normalization to equalize loudness Album art extraction and embedding Drag-and-drop interface for quick file selection Adjustable encoding parameters (bitrate, sample rate, channels) Uses internal codecs for consistent performance Supports CUE sheets for split track conversion File renaming based on tags during export Unicode support for international file and tag names Logging of conversion processes for troubleshooting Multi-core CPU support for faster conversions Download: Helium Converter 3.3.69.0 | 25.1 MB (Freeware) Links: Helium Converter Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Since it's been quite a while since the last episode aired, would it be fair (or cruel) to refer to Peggy as a MILF, or even a SMILF ?  HAHAHAHAHAHA
  • Recent Achievements

    • One Year In
      WaynesWorld earned a badge
      One Year In
    • First Post
      chriskinney317 earned a badge
      First Post
    • Week One Done
      Nullun earned a badge
      Week One Done
    • First Post
      sultangris earned a badge
      First Post
    • Reacting Well
      sultangris earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      172
    2. 2
      ATLien_0
      124
    3. 3
      snowy owl
      123
    4. 4
      Xenon
      118
    5. 5
      +Edouard
      93
  • Tell a friend

    Love Neowin? Tell a friend!