seeing other PC on network

[Guest]

Hi,

I have just installed my Christmas present and it works mostly!

PC1 windows2000 sp4 (CAT5 internet cable connection to router)

PC2 win XP (speedtouch 120g wireless USB card)

Router Speedtouch 580 (4 port ethernet switch & ADSL modem & 11g
wireless)

Both PCs can share the broadband connection and send email - ALL GOOD

Both PCs have the same login name and password.

But PC1 I can't access files on PC2 and vias versa.

I want to share files and printers.

I have both C: Drives set to share in my computer

Do I need net buie on both system?

Does anyone have any ideas?

Thanks

 

[Herb Martin]

"seeing" is an imprecise term but most people
meen "doesn't appear in Network Neighborhood
(or Places)"

Hi,

I have just installed my Christmas present and it works mostly!

Merry Christmas and Happy Holidays.

PC1 windows2000 sp4 (CAT5 internet cable connection to router)
PC2 win XP (speedtouch 120g wireless USB card)
Router Speedtouch 580 (4 port ethernet switch & ADSL modem & 11g
wireless)

Both PCs can share the broadband connection and send email - ALL GOOD
Both PCs have the same login name and password.
But PC1 I can't access files on PC2 and vias versa.
I want to share files and printers.

Do the two machine live on the same SUBNET (probably
the first three octets of the IP addresses?) If not, you
will not see them in the browser but can still connect...
see below.

Such routers can either make one subnet EACH for the
wireless and wired Ethernet, or many of them can bridge
the two into ONE network. (The latter is better if you
only have two machines and the router has this option.)

I have both C: Drives set to share in my computer
Good.

Do I need net buie on both system?
No.

Does anyone have any ideas?

Yes.

Open a command prompt (and leave it open forever
if you wish to be a true network guru.)

ping NameOfOtherMachine

ping IP.add.re.ss
(of other machine -- use actually IP address)

Also if those don't work:

tracert IP.add.re.ss
(of other machine -- use actually IP address)

net view \\nameNameOfOtherMachine
net view \\IP.add.re.ss
(of other machine)

You may have to get the IP by typing:

ipconfig /all

If you send that to a text file for each machine
you can post the text here for us to view if you
don't solve the problem.

If any of these work you can probably do this:

net view * \\NameOrAddressOfOtherMachine\ShareName

or...

net view * \\NameOrAddressOfOtherMachine\ShareName *
/user:ServerName\username

Sharename equals the name you used for the C drive.
(if you are depending on the default HIDDEN share of
C$ you will not see this or the machine in the browser
until you create a non-hidden share.)

With same username and password in a workgroup,
you should not need to provide the username and
password but that eliminates another varible.

Post your results if this doesn't get you working the
way you wish....

 

[Guest]

Sorry I mean,

I can see the other PC in network neighbourhood but when I double click
on it I get a permission denied error message.

 

[Herb Martin]

Sorry I mean,

Not an issue for me, and now you understand
why being explitic is so important (or we will

I can see the other PC in network neighbourhood but when I double click
on it I get a permission denied error message.

Ok, that means Browsing works, name resolution
works (since you get back a DENIAL, not a Not
Found type error), and that only the permission is
a problem.

And it also eliminates network issues (and should
confirm to you that NetBEUI is unnecessary.)

What permissions did you put on the share?
Especially for the username you are expecting to
work across both systems?

Try the explicit connection methods anyway, the
ones where you use "* /user:ServerName\Username" e.g.,

net user * \\ServerName\ShareName * user:ServerName\Username

Doing this eliminiates (or isolates) failure to authenticate.

Are the Workgroup names the same?

It used to be (NT4-ish timeframe) that same name,
same password in a workgroup would get you
auto-authenticated with that name.

I believe the workgroup name had to be the same
too though. (System Control panel.)
(Not sure about this though.)

 

[Guest]

Thanks for the reply.

I gave up on win XP and reformatted the disc and put on win2k. Took most
of the day to put on all the latest patches mind you

Well now it works some of the time.

Some times I can see the files on the other system other times I can't!

Very strange.

I will explain it in a new thread so as not to contuse anyone.

Thanks for the help

 

[Herb Martin]

Thanks for the reply.

I gave up on win XP and reformatted the disc and put on win2k. Took most
of the day to put on all the latest patches mind you

Well, that was pretty silly -- I have to say it -- as these
systems are largely the same, especially on the net and
the most likely difference that might cause you connectivity
problems we could have explained.

Win2000 == NT 5.0
WinXP == NT 5.1 (same but better)

Well now it works some of the time.

You probably have just recreated the same problems
or something similar.

Re-installing is almost always a poor choice despite
the advise that beginners receive frequently from tyros
and self-appointed pundits.

Some times I can see the files on the other system other times I can't!

If you would only explain clear the exact symtomps,
someone here can almost always find the solution.

[The last time you were apprently using the word "see"
to mean connect without receiving an permission denied
error.]

Most problems are easy to fix and almost all of them
have happened to thousands of other people.

Very strange.

I will explain it in a new thread so as not to contuse anyone.

Did you even try the command line suggestions we gave
you?

You waste our time when you won't stick with a
problem as we try to help.

But that is your choice.

 

[Guest]

Sorry for wasting your time.

But I have had lots of trouble with this XP system and SP2 didn't help.

I just thought it would be quicker to go back to win2k.

sp2 was a bit of a train wreck and I was fed up with it.

But I did learn some stuff so it was not a total waste of time but I do
take your point.

The installation under win2k went smoothly.

Thanks again.

Thanks for the reply.

I gave up on win XP and reformatted the disc and put on win2k. Took most
of the day to put on all the latest patches mind you

Well, that was pretty silly -- I have to say it -- as these
systems are largely the same, especially on the net and
the most likely difference that might cause you connectivity
problems we could have explained.

Win2000 == NT 5.0
WinXP == NT 5.1 (same but better)

Well now it works some of the time.

You probably have just recreated the same problems
or something similar.

Re-installing is almost always a poor choice despite
the advise that beginners receive frequently from tyros
and self-appointed pundits.

Some times I can see the files on the other system other times I can't!

If you would only explain clear the exact symtomps,
someone here can almost always find the solution.

[The last time you were apprently using the word "see"
to mean connect without receiving an permission denied
error.]

Most problems are easy to fix and almost all of them
have happened to thousands of other people.

Very strange.

I will explain it in a new thread so as not to contuse anyone.

Did you even try the command line suggestions we gave
you?

You waste our time when you won't stick with a
problem as we try to help.

But that is your choice.