\\computername not accessible, IP only

[pjrey]

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

[nazgul]

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.

[pjrey]

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

[Frank]

Can you ping the machines by IP address?

[pjrey]

yes, i can PING ip address of the xp home machines no problem (but NOT name)

i can do name or ip on the XP machines to xp pro/or vista no problem

pj

[cykosis]

That's a given considering he can connect to them fine by IP

*bah*.. that was to Frank, but you beat me with your reply

[hyde+]

different workgroups?

differnet dns addresses?

different subnet?

any one of them will cause that.

[pjrey]

sorry, should have specified that as well

same workgroup

same subment

same dns i think? how do i check that to make sure? they are connected through the same router

pj

[pjrey]

  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

[nazgul]

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

[pjrey]

thanks

will try that when i get back home!

pj

[+StevoFC MVC]

  hyedipin said:

different workgroups?

differnet dns addresses?

different subnet?

any one of them will cause that.

workgroups mean nothing and wouldn't cause that.

[+BudMan MVC]

^ 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

[pjrey]

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

[pjrey]

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 May 18, 2008 by pjrey

[+BudMan MVC]

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

[strugart]

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.

[+BudMan MVC]

what?? It is not a auth issue, since he is not getting an error 5 - but 53..

As to vista accessing xp home?? There is no issues with vista accessing either xp pro or home.

[strugart]

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.

[+BudMan MVC]

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

[Osiris]

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

[+BudMan MVC]

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

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 May 18, 2008 by BudMan

[Osiris]

Budman, that MVC tag is well earned.

[+BudMan MVC]

So what was your problem??

[pjrey]

  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 May 18, 2008 by pjrey