HELP!!! Win2KPRO OS can't get into 98 Box Drives Over The Network

[RiceDiGiZ]

Any Solutions?

It can't be the cables or nic. This is because this computer is on a dual boot (WIN2KPRO & WIN ME). I have no problems when i boot to Win Me, i can get into networked drives. But when i boot to win2kpro i can't get in networked drives.

I can see the computers on network neighborhood but i can't get in drives

Please help Thanks!

 

[cz]

If your Win98 machine has NetBEUI protocol installed you have to enable "NetBEUI over TCP" on your Win2K workstation. Otherwise you would not be able to use shared resources.

 

[RiceDiGiZ]

It has netbui

 

[cz]

You can open the property folder of "My Network Places", open the property page of "Local Area Connection", then open the property of TCP/IP protocol. Click on the "Advanced..." button, click on "WINS" tab, and click on "Enable NetBIOS over TCP/IP". That should do it.

 

[RiceDiGiZ]

i had it enable

 

[cavingjan]

What kind of sharing is being enabled on the 98 boxes?

 

[Dyngoe]

Hi,
Does this sound like your problem:
WinME works fine sorrect?
Win2k can see the outher PC in the Network Neighborhood, but fails when trying to open shared resources? You probably can ping the address of the second PC, but not the name of the other PC. If you check under Device Manager, you will see that your NIC is sharing resources with your onboard RAID, correct? Yes, this is ACPI and it works for almost everything, but maybe not here.
I had this same problem. My NIC was in slot 2 and everything seemed OK. However, my system froze everytime I tried to open a shared resource, whether through Network Neighborhood, or through Windows Explorer. I knew my cables were clean and I also knew my drivers were OK. What I had to do was remove ACPI from my system. I serched for info and figured out that it was better to reinstall than to try and remove ACPI, so I did. IT WORKED! Yes, I had to do a complete reinstall, but we all do that regularly, right? I'm not alone I think. I assumed that my problem was with my onboard RAID (Highpoint on BX133 RAID. Try other solutions before this, of course, but it may be the only fix. It was the only thing that worked for me. Good luck.
As Always,
D

 

[RiceDiGiZ]

Ok i try that thanks

 

[RiceDiGiZ]

Nope its not sharing resources