networking win2000 and win98

[Gelatinous_blob]

I have a system running on windows 2000 pro and a system running on win98 first addition.

When i open network places on the win2000 system i can see the other computer and folders but i can't copy files to it. When i open the computer icon it takes awhile for the folder to show up.

When i open network neighbourhood from the win98 system i can see the win2k machine and see the shared folder but cannot open it.

I have file and printer sharing enabled on both systems.

How do i set up my win2k and win98 machines to work together or should i just upgrade the win98 machine to win2k?

win2k machine:

celeron 415mhz
160mb ram
40gb hd

win98 machine:

pentium 133mhz
48mb ram
3gb hd + 1 gb hd

[cpugeniusmv]

if you can see the files from the other computer, but cannot write...i'm assuming that you have shared the folders on the computer, but in 'read-only' mode. on the computer with the files, right click on the shared folder (or root of drive c if that is what you're doing) and make sure that 'full access' or something similar is checked.

[phalkon30]

Have you shared both hard drives with full acess?

One protocol that may help you is Netbios, I believe it helps transfer information between 98 and NT machines

Other protocols you may want, tcp/ip, and ipx/spx

I think there was a very simple solution to this, I've done it before at lan partys, but I can't remember offhand what it was, try those, reboot both, and let us know what happens

[Krell]

cpugeniusmv

phalkon30


Did you bother to research that at all?



i can see the other computer and folders but i can't copy files to it

i can see the win2k machine and see the shared folder but cannot open it.

This isnt TCP/IP guys . . . cmon . . . .


darkdragon . . . dont even start !

[nasrules]

Originally posted by Krell
cpugeniusmv

phalkon30


Did you bother to research that at all?


who got told!!!!!!!!!!!!!! lol

[zaphodiv]

>[browsing w98 from w2k] i can't copy files to it
Check share setting as cpugenius and phalkon suggest.

> When i open network neighbourhood from the win98 system
>i can see the win2k machine and see the shared folder but cannot open it.
What error message do you get here?

I got out a drive that boots win98 and tried this myself.

w98, valid ip address. client for MS networks, Family login
and File&printer sharing installed. Client for MS networks
as primary logon. Share level access control, c: shared

win2k, default install, drive shared with full control for
administrator only(default, set up when logged on as admin)

Both computers in the same workgroup and in the same ip subnet.

The result I got is that the win2k machine can see the drive on
the win98 machine.

From the 98 machine, when logged on as 'laptop'
1)with default settings on win2k it asks for a password for
\\tookay\IPC$

2)After granting access for user Guest on the 2k box it works.
Guest coivers any username that isn't specifically set up as
a user on the 2k machine (or the authentication server in a company
setup with centralised authentication).

From the win98 machine when logged on to windows as administrator
(no password), it asks for a password for IPC$ and works if
I give it the password for the admin user on the 2k machine
(which has a password).

(Aside: I would have sworn win98 had an option to map a network drive
using a different username but I don't seem to have it. different
primary logon?)

[zaphodiv]

Windows networking, horrible, legacy, rant rant, blah blah blah.

>This isnt TCP/IP guys

There are two part to windows networking
NETBIOS which links machine names to MAC or IP addresses
and makes machines and folders appear in network neighbourhood.

SMB (renamed CIFS a while ago for extra confusion) which
allows the actual access to files and printers.

Windows networking can run directly on top of ethernet or
on top of internet protocol (ports 135, 137, 139 +some others in 2k?)

By default win98 and 2k will try to use NETBIOS over TCP
first and raw NETBIOS second.

if you have TCP/IP installed you need to have all the machines
in the same subnet ie if you have a subnet mask of 255.255.255.0
then the machines have to have ip's with the same first three
octets eg both in 192.168.0.x

The machines should have the same subnet mask (eg 255.255.0.0 versus
255.255.255.0 is bad). NETBIOS over IP uses broadcast packets
so the machines have to agree about what their broadcast address is
(defined by ip+netmask).

Blob, do you have a personal firewall on the machines BTW?

In my experiance making windows networking function is half voodoo
and random fiddling but having TCP/IP installed with usable
addresses generally seems to work better.

[Krell]

After granting access for user Guest on the 2k box it works.
Guest coivers any username that isn't specifically set up as
a user on the 2k machine (or the authentication server in a company
setup with centralised authentication).

From the win98 machine when logged on to windows as administrator
(no password), it asks for a password for IPC$ and works if
I give it the password for the admin user on the 2k machine
(which has a password).



Thx zaphodiv, now your getting at it. I sent him some link this morning just before passing out. The machines can obviously see each other, so the networking is pretty much a given.

The issue then is permissions. THAT's what W2000 and up is for, security.

[cpugeniusmv]

AHHHHHHHH...

once again, my answer above was one of those early in the morning :S:S:S

/me smacks himself around a bit with a large trout

[endersgame21]

Originally posted by cpugeniusmv
AHHHHHHHH...

once again, my answer above was one of those early in the morning :S:S:S

/me smacks himself around a bit with a large trout
LOL. I think you have been spending a little too much time in the IRC room.

!cheese

[zaphodiv]

I should mention security.
>win98 first addition
Hang on, dosn't that have the netbios bug that allows passwords to be bypassed?
I hope you have patched that machine before connecting it to the internet.

>After granting access for user Guest on the 2k box it works.

My machine is behind a NAT so this is safe.
If the machine is connected directly to the internet you do not want to
allow guest access. Not all all ISP's block incoming connections to
the windows networking ports. Read only guest access will allow
anyone on the internet to clog your bandwidth while they copy
your mp3 collection and your interesting documents. Write access
will result in anything from viruses to hackers using your machine
as a bounce point for evilness.

I generally don't mention this little problem as the hundreds of thousands
of machines out there with drive C: world writeable are not going to
be fixed anytime soon, it is better if the kids don't know about it.