Simple Networking Problem Win98 to Win Me on Peer to Peer

[MuffD]

All I'm trying to is share folders between the two. I already shared the folders that I wanted to be able to be seen. Now, when I try to map the drives, it does not see the computer. I am also typing in the correct path as well. I enabled file and print sharing on both pcs.Do I need to make user accounts on both pcs as well?

thanks for your input

 

[Panther505]

No just ensure that Netbeui is installed on both systems.. If it is not the you cannot "see" the other machine. use the ipaddy to ping the other system on the network then attempt to ping by the machine name. If you cannot ping using the name then you probably do not have Netbeui installed

 

[obenton]

Before you map the drives you must have the network configured and running. Good instructions at http://ourworld.compuserve.com/homepages/J_Helmig/

 

[MuffD]

Thanks guys!

 

[willhart]

I think panther has it wrong you do not need netbuei at all. The only protocol that you need is TCP/IP. I think Panther was getting that confused with NetBIOS which is apart of TCP/IP. Make sure all of the computer are on the same subnet basically all ip's have to say something like 123.123.123.X. All the computer on the network have to have the same numbers where it says 123. Where it says X is where each computer has its own unique # 1-255. When you check that make sure when you click on Identification I think in win98 all of the computers have the same workgroup name.

Good Luck!!!

 

[mgpaulus]

You do not NEED netbeui for a local net. However, Netbeui is the protocol of choice for small Windows networks. It is very fast. However, it is for small networks only, as it is NOT routable. But for small, single segment lans, netbeui is a very good choice. netbios over tcp/ip has a lot of overhead for windows networking. Try netbeui and see what you think.

 

[Panther505]

mgpaulus- you are entirely correct. With only 2 system netbeui would really be the best.. I would ensure that the 2 systems can talk. if he cannot ping then he needs to ensure that the systems are on the same subnet. also it would be to his benifit to "hardcode" the IPaddress to ensure that both machines are able to talk....


muffstah - check to see if the systems will talk. If not then force the IP addys using any range with the preferred being the class "c" that MS uses 192.168.0.- with the subnet of 255.255.255.0 . Reboot the systems then from a command window try to ping the IP addy and then try to ping the machine name..