Solve : Another Day. Another Problem?

1.	Solve : Another Day. Another Problem?
Answer» I am attempting to set up a LAN between 2 computers. One of the running WIN2000, the other WIN98SE. Ihave an Ethernet card in each computer, and a connecting cable between them. When I go to the Command Prompt, I am able, from each computer, to PING the other, I've run "tracert" from each computer, and each recognizes the other. The problem arises when I try to Map a Network Drive. When I try this from the computer running WIN98SE there is no problem. When I try it from the computer running WIN2000, I am given various error mesages (dependending from whence I attempted the mapping) the GIST of them being that WIN2000 does not recognize that the other computer exists. The "tracert" command tells me what the other computer's name is, but the Map Network Drive command using that name tells me the server can't be found. Anyone have any ideas? Tom When you create a map drive, how are you typing the address? You might find that older computers may require that you type \\networkname\computer\folder Where, newer ones may only require \\computername\folder (Like, I am on the network Uber the computer I want to access is M16 and the folder is Documents, it would be \\M16\documents though the folder is not required.)Quote from: Zylstra on August 15, 2007, 07:11:52 PM When you create a map drive, how are you typing the address? You might find that older computers may require that you type \\networkname\computer\folder Where, newer ones may only require \\computername\folder (Like, I am on the network Uber the computer I want to access is M16 and the folder is Documents, it would be \\M16\documents though the folder is not required.) I don't think in this case the network has a name. Certainly not one I have assigned it, I have another pair of computers with the same configuration (Win2000.Win98SE), and have no problem connecting them without a network nameAll computers that access a network (excluding Linux, of couse) use either: A domain or A Workgroup Both of these are considered the network name. Right click My Computer, and click Properties Find the tab with your computer name, and change the workgroup to MSHOME on all your computers You dont need to use MSHOME as the name, it can be ANYTHING you want, like DEANSFAMILY (though, the name cant be very long) Once you are sure that all the network names are the same, then it should connect correctly. Quote from: Zylstra on August 15, 2007, 10:40:39 PM Once you are sure that all the network names are the same, then it should connect correctly. The Workgroup name on both computers in question is the same. That's why I'm able to connect from the WIN98SE one to the other. The question is: why won't the connection work the other way. I tried using the workgroup name in identifying the drive to be mapped,as you suggested (\\Workgroup\Computer\Drive) and got an error message that the path could not be found. TomHow long have you waited for the systems to 'see' eachother? I've experienced where it takes a while for the the network to 'wake up' and see everything. M$ says at least :15 minutes. Alan <>< Quote from: ale52 on August 16, 2007, 09:11:07 AM How long have you waited for the systems to 'see' eachother? I've experienced where it takes a while for the the network to 'wake up' and see everything. M$ says at least :15 minutes. Alan <>< I'm amazed at that, I've NEVER experienced such a delay. It always either works, or it doesn't; and when it doesn't it's usually because I've either done something wrong, or not done something I should have. In this case, the question is moot, since I've now been able to get both computers to recognize each other. Apparently in Win98, at least, the identification of the computer is case-sensitive. Once I had made sure that the computer name was in upper case on the 98 computer, and that I was identifying the computer whose drive I was attempting to map from the 2000 computer also in upper case, the problem went away, and each computer now sees the other. TomSo i guess we can say now that "Tom...you're a case sensitive guy"..... Quote from: patio on August 16, 2007, 07:34:02 PM So i guess we can say now that "Tom...you're a case sensitive guy"..... We could - but only if we want to MAKE a very bad pun. Tom

Answer»

I am attempting to set up a LAN between 2 computers. One of the running WIN2000, the other WIN98SE. Ihave an Ethernet card in each computer, and a connecting cable between them. When I go to the Command Prompt, I am able, from each computer, to PING the other, I've run "tracert" from each computer, and each recognizes the other.

The problem arises when I try to Map a Network Drive. When I try this from the computer running WIN98SE there is no problem. When I try it from the computer running WIN2000, I am given various error mesages (dependending from whence I attempted the mapping) the GIST of them being that WIN2000 does not recognize that the other computer exists. The "tracert" command tells me what the other computer's name is, but the Map Network Drive command using that name tells me the server can't be found.
Anyone have any ideas?
Tom
When you create a map drive, how are you typing the address?
You might find that older computers may require that you type \\networkname\computer\folder
Where, newer ones may only require \\computername\folder
(Like, I am on the network Uber the computer I want to access is M16 and the folder is Documents, it would be
\\M16\documents though the folder is not required.)Quote from: Zylstra on August 15, 2007, 07:11:52 PM

When you create a map drive, how are you typing the address?
You might find that older computers may require that you type \\networkname\computer\folder
Where, newer ones may only require \\computername\folder
(Like, I am on the network Uber the computer I want to access is M16 and the folder is Documents, it would be
\\M16\documents though the folder is not required.)

I don't think in this case the network has a name. Certainly not one I have assigned it, I have another pair of computers with the same configuration (Win2000.Win98SE), and have no problem connecting them without a network nameAll computers that access a network (excluding Linux, of couse) use either:
A domain
or
A Workgroup

Both of these are considered the network name.
Right click My Computer, and click Properties
Find the tab with your computer name, and change the workgroup to MSHOME on all your computers
You dont need to use MSHOME as the name, it can be ANYTHING you want, like DEANSFAMILY (though, the name cant be very long)
Once you are sure that all the network names are the same, then it should connect correctly. Quote from: Zylstra on August 15, 2007, 10:40:39 PM

Once you are sure that all the network names are the same, then it should connect correctly.

The Workgroup name on both computers in question is the same. That's why I'm able to connect from the WIN98SE one to the other. The question is: why won't the connection work the other way.

I tried using the workgroup name in identifying the drive to be mapped,as you suggested (\\Workgroup\Computer\Drive) and got an error message that the path could not be found.
TomHow long have you waited for the systems to 'see' eachother? I've experienced where it takes a while for the the network to 'wake up' and see everything. M$ says at least :15 minutes.

Alan <><

Quote from: ale52 on August 16, 2007, 09:11:07 AM

How long have you waited for the systems to 'see' eachother? I've experienced where it takes a while for the the network to 'wake up' and see everything. M$ says at least :15 minutes.
Alan <><

I'm amazed at that, I've NEVER experienced such a delay. It always either works, or it doesn't; and when it doesn't it's usually because I've either done something wrong, or not done something I should have.

In this case, the question is moot, since I've now been able to get both computers to recognize each other. Apparently in Win98, at least, the identification of the computer is case-sensitive. Once I had made sure that the computer name was in upper case on the 98 computer, and that I was identifying the computer whose drive I was attempting to map from the 2000 computer also in upper case, the problem went away, and each computer now sees the other.
TomSo i guess we can say now that "Tom...you're a case sensitive guy".....

Quote from: patio on August 16, 2007, 07:34:02 PM

Solve : Another Day. Another Problem?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment