cannot see computer in workgroup.

Ed,

That turedo tunneling bit is part of IPV6. Which is not installed as part of sp2, (Which I read from the link you sent me.) You have to go to Add remove progs>Networking>Details and tick Peer to Peer. Then if you uninstall SP2 it will still be installed until you go back to add/remove progs and manually remove it that way.

I will remove it but we were having problems well before I did install it so I dont think it will make a diference, perhaps just get everything back on the same field.

Im still not sure if I should enable netbios over tcp/ip or use netbios from dhcp server?

Quote:

---

Originally Posted by riddellcomp

You have lost me there. These pcs are all running XP pro.

---

Oh ignore me, confus-ed with myself ! :rolleyes: - but I can tell you it does do this with home, as I've got someone with exactly the same symptoms( so this "PC 1 does not see any computers on the network including itself or any shared files. PC 2 can see itself on the network but not PC1 or its files.
" hence my confusion - apologies ! Mixed the two up ! - I wonder what I told him ? :D), he went up to sp2 & turned all the peer to peer stuff on, thus using the same ipv 'whatever' & that fixed that..

Quote:

---

Okay we will have to remove IPV6 from PC 1.

---

So that should tie in with the very confus-ed reasoning above ! [shakes his head some more]

As for the netbios setting question, there's three options for wins, default, which is use netbios from your router as thats dhcp server here if available otherwise enable netbios over tcp/ip, or there's enable it anyway, or turn it off.

Try with it on (default).

Quote:

---

Originally Posted by Hudonsmith

..then dns is not your problem

---

If the quote below is still happening

Quote:

---

On PC2 I can ping PC 1 by IP and can access shared files from pc1.
But I cannot ping PC 1 by name.

---

Then local resolution is the issue.

PC2 is the wireless one & that looks at the isps, then local, so it'll just not find it, it wants to look at local, then isps dns ?

Quote:

---

If the quote below is still happening http://forums.windrivers.com/images/...t-top-left.gifQuote:http://forums.windrivers.com/images/...-top-right.gifhttp://forums.windrivers.com/images/...p-right-10.gifOn PC2 I can ping PC 1 by IP and can access shared files from pc1.
But I cannot ping PC 1 by name.

---

It sort of is. We cant access any shared files from PC1 either the last time we tried but i think it was a problem elsewhere as we were able to at one stage.

Quote:

---

Then local resolution is the issue.

PC2 is the wireless one & that looks at the isps, then local, so it'll just not find it, it wants to look at local, then isps dns ?

---

Yes thats what I thoughthttps://forums.windrivers.com/images.../2005/03/1.gifhttps://forums.windrivers.com/images.../2007/09/1.gif.
But how do we do that??????

Im still reading your informative article on name resolution and have learnt quite a bit. One question though..With name resolution what determines what method is used? EG.

• NetBIOS broadcasts
• HOSTS files
• LMHOSTS files
• Domain Name Server (DNS)
• Windows Internet Name Service (WINS)
• Dynamic DNS

Does the computer use all of these in order, only some of these or depends on the settings and if so where would this be set? I noticed on my own pc there is an option ticked under wins to enable lmhosts lookup. Just wondering why its ticked?

Quote:

---

Originally Posted by riddellcomp

It sort of is. We cant access any shared files from PC1 either the last time we tried but i think it was a problem elsewhere as we were able to at one stage...But how ..

---

& who's supposed to be confus-ed ?.. me ! (not you ;))

Go back to this can't 'ping by name' but can 'ping IP address' business & note the differences between where the two cases can & can't resolve (Since you took IPv6 off one of the ones involved, perhaps its worth re-quoting the ipconfig, ipconfig/all ? Its worth comparing them again anyway!) - its something there methinks ... - To tie it to your next question all these levels of resolution are subject to hierachy in that netbios looks to LMhosts, then I attempted a further explanation of that , realised I'm leaving you confus-ed by introducing loads of concepts instead of just answering :rolleyes: .. :D & say instead - read page 3 of the name resolution link I sent you there's a bit starting "Name Resolution at a Glance..."

Quote:

---

I noticed on my own pc there is an option ticked under wins to enable lmhosts lookup. Just wondering why its ticked?

---

If you understand the link I think you'll know why :D (When netbios has failed to resolve by broadcast it looks to lmhosts as the next place to resolve, lmhosts are a way of having a master host list for a network, so all machines should check all other machines for different lists {enable mhosts lookup} & that might include machines beyond the broadcast scope {not on the same physical layer}..)

Ed,

I will read the entire article before I ask stupid questions but I think Im understanding it a litle more now.

I will have to put this network troubleshooting on hold as he is going to Queensland for a holiday tommorow and wont be back for a week. Its not going to beat me though and I am determined to fix the problem when he gets back. Thanks again for the help.

Conceptually I think its tricky to fathom whats going on as there's no 'one place' to do everything for netbios, & that might muck things up, as its very easy therefore to have something different somewhere & this is what using domains is all about ! One central point of control & administration not just per machine, but for all objects, with a peer to peer environment you don't have that & thats what IPv6 & these extra networking components are meant to help with - distributing info about shares correctly - :D didn't here !, it just muddled matters & me ! ;)

We'll have another go then when he gets back ?, though I think you may be able to fix it now ?, my guess is if you'd been hands on with this you'd have fixed it anyway by just experimenting ;)..

Okay what about if we were to set up a server/client network instead with PC 1 as the server and PC 2 and PC 3 as the clients? Can this be done easily enough and is it suited to this type of home network or more so for larger type networks??

For most home networks when they say sharing to me, I try & get them fixed up with an xp pro client that way you can turn off simple file sharing on that & use it to hold shared files & make any on the home clients read only (many might think this a touch 'over zealous' ;)) but read that labmice link (I'll repeat it ;) - xp secuity checklist - & its exactly what they say too :D !) -which is pretty much your 'server' suggestion .. :thumbs:

'Billy' generally is wanting to steer you towards a domain (so a 'real' server as it has central control ), but for 3 machines ? , you are having a laugh ! :devil:

You could of course just fix this how its setup now, (taking note of the earlier advice about s/w firewalls & already being behind a 'device' {your router} ;))

btw I kept finding myself using quotes to match 'billy speak' to realworld stuff - a 'server' is really a unit that distributes info or services to other units, billy uses it a bit different & usues it to include central control too, so his 'servers' have to have control of what they give out, in a peer to peer environment you just share & folks get stuff ..

Quote:

---

You could of course just fix this how its setup now, (taking note of the earlier advice about s/w firewalls & already being behind a 'device' {your router} ;))

---

Ed,

Im often left wondering if you know what to do to fix this but am trying to make me find the answer myself. A bit like my high school teacher used to do.https://forums.windrivers.com/images.../2007/09/1.gif You perhaps even remind me of Yoda...https://forums.windrivers.com/images.../2005/03/1.gifhttps://forums.windrivers.com/images.../2005/03/1.gif

I took note of the earlier advice about firewalls and removed Nortons completely. Was there something else I missed though?

I think the 'why' of why this isn't going correctly is in some setting somewhere's but we keep adding & removing things & you are 'remote controlling' someone else, so its hard to say exactly 'change this' or 'that' etc, I have to wait for reconfirmation of something, then you ask a conceptual question & I give you too much info & leave you confus-ed ;) & the whole things been 'meandering about' (like you say, like some 'educational exercise') for quite a bit longer than perhaps it should, because of that ;)

When he comes back, you want to either consider an xp pro client & use that for sharing, or concentrate on getting all the clients exactly the same in terms of netbios scope..

Its just a settings issue somewhere, I foolishly though having an idea of the why's might help ;)

Well cant you fly over and fix this then??? Its lovely here this time of year. A little humid perhaps as our wet season is just around the corner but its only 32C everyday and we have airconditioning.https://forums.windrivers.com/images.../2007/09/1.gifhttps://forums.windrivers.com/images.../2007/09/1.gif
Seriously though I agree with you it is hard to do this remotely. When he comes back we will take it from the start and I will untick simple file sharing and set it up like my own network, which I might add worked flawlessly and I had no trouble setting it up.