Does anyone know which of the drivers listed at
http://www.realtek.com.tw/downloads...6&Software=True
would be suitable for use with Fedora Core 2?

the link below will download drivers that will work on XP, ME, 98SE, 2000

ftp://152.104.238.194/cn/nic/rtl8139abcd8130810xseries/rtlsetup-rtlnic(621)(0620).zip

(copy and paste into the address bar)

I've got my Windows set up OK, it's my FC2 Linux I want to network now and it's not clear which driver is for my distro.

from what i can find fedora is based on redhat, i dont knw which kernel though you'll need to find out, but ine of the following should work

this one for 2.4

ftp://202.65.194.18/cn/nic/rtl8139abcd8130810xseries/linux24x-8139cp(160).zip

or this one for 2.2

ftp://202.65.194.18/cn/nic/rtl8139abcd8130810xseries/linux22x-8139cp(100).zip

or this one for 1.2 - 2.2

ftp://202.65.194.18/cn/nic/rtl8139a.../netdrivers.tgz

Mine is 2.5, and there doesn't seem to be a driver listed for it.

Hi,

Both 2.4 and 2.6 series kernels come with support for most NICs. I've been using the 8139too module succesfully with both 2.4 and 2.6 kernels. If you're using a stock Fedora kernel my guess is you'll get going with

insmod 8139too

Of course vendor drivers may have extra features, but I haven't seen a need to try anything else.

Regards,
-u-

My kernel is 2.6 not 2.5 as I said previously. It probably doesn't need the drivers as you say upside but I'm having trouble networking to my W2k and W98 machines and thought I should check the NIC drivers. I also tried to network to a WinXP machine and that wouldn't respond either, I just keep getting the message that it can't find the network path.The TCP\IP settings are OK, sometimes the Windows can 'see' the Linux machine and sometimes it can't. The Linux machine doesn't 'see' anything on the network though. I'm using Samba but don't fully understand what is involved.

Hi again,

Try pinging the Linux host from the Windows host and vice versa. This will tell you if the network is configured correctly and whether there is an issue with firewall settings. If both can ping each other, I think you can safely assume the NIC is ok.

Samba is a lot more tricky! Start with the Win98, it's easier to deal with. Make sure you've got file and printer sharing on and share a folder or two. Then try to list shares on it from the Linux box anonymously. On the command line do

smbclient -L ip_address

Where ip_address is that of the Windows box. Hit enter if you're asked for a password. You should get information about the Windows machine: workgroup, OS and such, perhaps even a list of shares. If you don't even get that, file sharing is not configured properly on the windows box or there's a problem with the network and/or firewall.

To test authentication, do the same but with a user/password combo you know is good on the Windows box:

smbclient -L ip_address -U username -P password

If things are looking good you might want to use the linneighborhood program to connect to Windows shares, or use smbmount from the commandline if that is your thing.

To share files and folders from your Linux box, you have to configure the Samba server by editing /etc/samba/smb.conf either manually or using a graphical tool. I prefer manual editing because of the extra control. Make a copy of the original file! Edit the original or write your own. Here's a sample of things you should change to get started.

workgroup = WORKGROUP (or whatever you've got on your windows box)
security = share

This should let you connect to the /home directory of the user you're logging in as (see below for adding Samba passwords to Linux user accounts). If you want a global share add something like

[share]
comment = Shared for everyone
path = /home/share
browseable = yes
force user = nobody
read only = no
guest ok = yes
create mask = 0777

Save smb.conf. Now create a directory /home/share and make the owner nobody:

mkdir /home/share
chown nobody /home/share

Now get the new settings with

service samba reload

You should be able to see the Linux machine under WORKGROUP after a few minutes. On XP and probably Win98 you can connect directly if you're in a hurry. WindowsKey+R to open the Run dialog, then enter

\\ip_address\

Where ip_address is that of the Linux box, of course. You'll probably want to map shares as network drives, too.

It's also a good idea to add a user to Linux that has the same name as your Windows user. Then add the Windows password to it as root

smbpasswd -a username

Reload the configuration again and remember to keep accounts and passwords in sync!

Regards,
-u-

Hi upside
Pinging was successful both ways. Unfortunately I have to work the weekend so it will probably be Wednesday before I can try your suggestions - I'll let you know what happens.

Hi,
I am working in VB. I have used edit mask control to retrive data for date
can u tell me how to initialize the mask contol
for text we can initilize with
text1.text = ""

but for mask edit contorl which property we should put and how to initialize with 00/00/00