Frustrated! Peer-to-Peer Problems

[ajskydiver]

Hi Guys,
I've been stumped...I'm trying to allow file and print sharing between two systems (Win2K and Win98SE).

Using MS Client, same workgroup, adapter, TCP/IP, file/print sharing enabled - Win98 machine.

Just as a test, I configured the Win2K machine with same IP address and it reported the error and logged it.

Both machines can see themselves in the workgroup, along with the shared folders.

And I can ping by name and actual ip both ways...that's about it.

Any suggestions?

Thanks,
AJ

 

[kyoshozx]

If you can ping the other machines usually means the network is working, basically it should be a configuration problem if you can't share files.
What are your exact problems? Is the win2k machine able to see the win98 machine's shares? Usually problem is win98 can't see win2k share because of permissions.
Well first if you want the win98 machine to access the win2k share, first you would need to create the same user that logs onto win98 on the win2k machine. This can be accomplished using computer managment in win2k, just add a new local user.

 

[ajskydiver]

I did add the user in Win2K--but the computers cannot see each others shared folders or devices (each sharing printers and a folder) at all...they can only ping!

I'm totally stuck--still no luck.

Why can they ping but not see each other?

~AJ

 

[alocurto]

what protocols and services are in the network setup for your ethernet card? Is Microsoft logon installed?

 

[alocurto]

Should have client for microsoft networks and File Printer sharing. I know netBEUI can help. BTW can anyone explain what netBEUI is exactly.

-alocurto

 

[lumberg]

Try typing in the UNC (universal naming convention) in the address bar of IE, or an open folder.
It will be a double backslash followed by the machine name of the machine you want to look at. Windows is often times retarded with network neighborhood, and just needs a kick start. This usually works for me. You may also want to check the bindings of the TCP/IP protocol to the file and print sharing for the network interface. I've had mine disabled automatically because of the dial up connection, as a security precaution.
NetBEUI can help, but it won't fix the "problem". It's a Microsoft proprietary protocol that is pretty much obsolete. Win2000 uses TCP/IP as it's default.
Make sure the workgroup name is exactly the same.


Good luck

PS-American Psycho was a killer movie

 

[ajskydiver]

I have checked all the above...I'll be reformatting and reinstalling everything on my GF's computer this afternoon...

I'll let you guys know what happens...thanks for all the input.

~AJ

 

[Superunknown]

NETBEUI is another protocol like TCP/IP except it is nonroutable, therefore if you enable it by itself without tcpip you wont see the internet. However on your local network it is perfect. If you enable TCPIP and NETBEUI on both machines you should be able to see each machine fine.

 

[puritan]

NetBEUI = Netbios Extended User Interface.

Basically NetBEUI is a layer 2 protocol that was developed by Microsoft for their Windows for Workgroups platform. It works great for a small LAN because it is actually faster than TCP/IP because you don't have to ARP for IP addresses before you send. Also, If you already have TCP/IP connectivity, NetBEUI won't get you anything more except a little bit of speed on the LAN that you won't even really notice. And you won't even see it unless you bind NetBEUI to the NIC first then IP second.

 

[ajskydiver]

I reformatted the problem machine and everything works beautifully now.

~AJ

Edit: Nothing like a fresh format and clean install to give you that just showered feeling.