Windows networking question

[kallend 2,027]

I have a network at home with 4 computers of various vintage, and they all talk to each other except for the one running Windows 2000. I cannot log onto it from the XP Pro or Win 98 computers. It will let me log on to them, however.

I had exactly the same problem in my office a couple of years ago - nothing would connect to the WIN2000 machine although it would connect to them.

Is this a coincidence, or is there some fundamental incompatibilty with Win2000?

I'd update the 2000 machine to XP Pro except it belongs to my SO, and she doesn't want to do that.

...

The only sure way to survive a canopy collision is not to have one.

[flyangel2 2]

Geek talk is hot

Need a shower to cool off now!

May your trails be crooked, winding, lonesome, dangerous, leading to the most amazing view. May your mountains rise into and above the clouds. - Edward Abbey

[Armour666 0]

do you log on to your XP nd 2000 box with a password ? XP and 2000 by default wont let other machines conect to it if the passwords are blank.

SO this one time at band camp.....

"Of all the things I've lost I miss my mind the most."

[bob.dino 1]

When you say "connect", do you mean "map a drive"?

Is the 2K machine behind a firewall of any sort (hardware or software)?

Can you

ping name_of_2k_machine

from the XP machine?

[kris2extreme 0]

have you enabled the Guest account in the user settings?

[kallend 2,027]

Quote

Geek talk is hot

Need a shower to cool off now!

Just thinking about it gives me ****.

...

The only sure way to survive a canopy collision is not to have one.

[kallend 2,027]

Quote

do you log on to your XP nd 2000 box with a password ? XP and 2000 by default wont let other machines conect to it if the passwords are blank.

I set all the passwords and user names the same on all machines. No blanks.

...

The only sure way to survive a canopy collision is not to have one.

[kallend 2,027]

Quote

have you enabled the Guest account in the user settings?

Yes, did that too.

...

The only sure way to survive a canopy collision is not to have one.

[kallend 2,027]

Quote

When you say "connect", do you mean "map a drive"?

Is the 2K machine behind a firewall of any sort (hardware or software)?

Can you

ping name_of_2k_machine

from the XP machine?

The 2k machine shows up when I view the network, but it demands a password and always claims the password I give is incorrect. However, the passwords are exactly the same on all machines.

I gave up for tonight, I'll try the ping tomorrow.

...

The only sure way to survive a canopy collision is not to have one.

[legorowbot 0]

When it asks for a username and password, try using name_of_win2k_machine\username instead of just the username. even though the usernames and passwords are the same, the accounts are tied to the machines, so user1 on machine1 doesn't equal user1 on machine2.

Why does it say "Append signature to post" when I don't have a signature?

[jsaxton 0]

Make sure that you have tcp/ip enabled on all the computers.
If memory serves me correctly, the default network protocol pre-200 was netbios.

If you really get stuck send me an IM, after all, I owe you for the Physics lesson ;)

[kallend 2,027]

Quote

Make sure that you have tcp/ip enabled on all the computers.
If memory serves me correctly, the default network protocol pre-200 was netbios.

If you really get stuck send me an IM, after all, I owe you for the Physics lesson ;)

It is. Each works independently just fine, and connects just fine to the router and the outside world.

...

The only sure way to survive a canopy collision is not to have one.

[jsaxton 0]

So what EXACTLY are you trying to do and what:
1) are the exact actions you are taking
2) what you observe
3) the expected results

Please feel free to include screen shots

[bob.dino 1]

Quote

When it asks for a username and password, try using name_of_win2k_machine\username instead of just the username. even though the usernames and passwords are the same, the accounts are tied to the machines, so user1 on machine1 doesn't equal user1 on machine2.

Yup. This is the correct next step.

If you can see the machine and it's demanding a password then it's not a connectivity problem.

[kallend 2,027]

Quote

Quote

When it asks for a username and password, try using name_of_win2k_machine\username instead of just the username. even though the usernames and passwords are the same, the accounts are tied to the machines, so user1 on machine1 doesn't equal user1 on machine2.

Yup. This is the correct next step.

If you can see the machine and it's demanding a password then it's not a connectivity problem.

It doesn't ask for a user name. It says "You must supply a password to make this connection"

Then I supply the only password that I know (the one that works when I log onto the machine directly, both as named user, as "msdefault", and as "Administrator"), and it says "The password you supplied is incorrect, try again".

So what other passwords are there?

...

The only sure way to survive a canopy collision is not to have one.

[beowulf 1]

When you map the drive there is a selection for connecting as a different user. Try that. It should allow you to change the user name. Like the other poster said try computer_name\user_name

[beowulf 1]

If that doesn't work then try opening a DOS window and typing in net use x: \\computer_name\share_name

Then it should ask for user name and password/.

[kallend 2,027]

Quote

When you map the drive there is a selection for connecting as a different user. Try that. It should allow you to change the user name. Like the other poster said try computer_name\user_name

Are you referring to the machine I'm trying to connect TO, or the one I'm connecting FROM?

...

The only sure way to survive a canopy collision is not to have one.

[kallend 2,027]

Quote

If that doesn't work then try opening a DOS window and typing in net use x: \\computer_name\share_name

Then it should ask for user name and password/.

And what is x?

This seems a real hassle for something that is supposed to be easy. All my other PCs networked trivially easily.

...

The only sure way to survive a canopy collision is not to have one.

[beowulf 1]

yes the computer that I am referring to is the computer you are connecting to.

x is the drive letter being assigned to the mapped drive. You don't have to use x you could use any letter that isn't being used. You shouldn't be able to use A, B, C, or D, but any other letter will most likely be free.

[kallend 2,027]

Quote

yes the computer that I am referring to is the computer you are connecting to.

x is the drive letter being assigned to the mapped drive. You don't have to use x you could use any letter that isn't being used. You shouldn't be able to use A, B, C, or D, but any other letter will most likely be free.

FIXED IT!

In "Administrative Tools" -> "Local Security Policy" -> "Local Policies" --> "User Rights Assignments" --> "Access this computer from the Network", no-one was allowed access from the network!

...

The only sure way to survive a canopy collision is not to have one.

[beowulf 1]

cool

amazing how it's always the last thing you think of!

[kallend 2,027]

Quote

cool

amazing how it's always the last thing you think of!

...

The only sure way to survive a canopy collision is not to have one.

[justinb138 0]

Quote

cool

amazing how it's always the last thing you think of!

Of course it's always the last thing you think of. If you found the problem, you wouldn't still be thinking about it.

[beowulf 1]

yeah yeah I know cheesy joke. But sometimes I can't help myself.