Windows98 and Caldera Linux connection

I need to connect my windows 98 computer with my Linux box (Caldera 2.2). I do not have experience with linux.
Can somebody describe to me the necessary steps needed to configure the Samba Server? . I tried following the steps described by the Caldera Website, but the result was that the linux box showed up only one time in network neighborhood, and then completly vanished. I ping the linux box with no results at all. I know my cabling and nics work because I can connect when using windows 98 and NT.
wagenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lewisgCommented:
If you can't ping you can't samba...

Please post:
* machine IP's and netmasks
* results of ifconfig on linux box
* exact text of pings in both directions (win>linux, linux>win)
* NIC makes and models, nic kernel module in linux with any parameters
* linux distribution
0
biardCommented:
Does the login name on the win98 machine mesh with a valid user account on the linux box?  And are the ip addresses set correctly?  And the net mask and gateway?  Post the output from the following:

route

ifconfig -a

0
gregmessCommented:
Pinging a machine's Ip address is just about the simplest form of netwroking there is. (I know just go with it k?) If you can't ping then TCP/IP is not correctly setup on one or both machines. Very likely your TCP/IP is setup correctly on the Linux box and not on the windows box. Windows defaults to netbeui and doen't install TCP by default. Even if you install TCP Windows doesn't make it obvious that you need to set the IP address of subnet mask. Get ping working and then visit
http://us2.samba.org/samba/oreilly/using_samba/ 
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

wagenAuthor Commented:
Here, are my configurations:
Win98 machine Ip.192.168.0.6
netmask 255.255.255.0
Linux machine Ip. 192.168.0.11
netmask 255.255.255.0
RESULTS OF IFCONFIG IN LINUX AS FOLLOWS:
[root@unix13 /root ]# ifconfig
Link encap: Local Loopback
inet encap: Local Loopback
inet addr: 127.0.0.1 mask: 255.0.0.0
UP LOOPBACK RUNNING MTU: 3924 Metric: 1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 frame:0

etho Link encap: Ethernet Hwaddr 00:50:BA:A2:93:51
inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX Packets:40 errors:0 dropped:0 overruns:0 frame:0
TX Packets:40 errors:0 dropped:0 overruns:0 frame:0
Collisions:0 txqueuelen:100
Interrups:10 Base address:0xdf00

PINGS: from win98 C:Ping 192.168.0.11
                  C:Ping unix13
       from Linux: Ping 192.168.0.6
                   Ping P1a6f6
NETWORK CARD IN BOTH MACHINES:
D-LINK DE-528 PCI
COMMENT: THIS TWO MACHINES PERFECTLY CONNECT UNDER WIN/95, NT WORKSTATION, NT SERVER, WIN98, BUT BY NO MEANS BETWEEN WINDOWS 98 AND CALDERA LINUX 2.2
LINUX KERNEL 2.2.5.
THE Workgroup= WORKGROUP in both machines (win98 and linux).
Any help would be greatly appreciated.
Thanks in advance to all of you...
0
themCommented:
Get swat working on the caldera box.

Below are instructions for Red Hat, Caldera should be close:

Anyway here is how to use it. When I say to edit a file use your favorite
text editor.

1) become root
2) cd /etc
3) Edit the inetd.conf file
4) find the line:

swat      stream  tcp     nowait.400      root /usr/sbin/swat swat

(note the above line is contained wholly on a single line). It may have a # in front of it. If it does remove the #, if the line is not there copy it exactly as I have it into the file. Save and exit the file.

5) edit the services file, find the line (usally the last line in the file):

swat              901/tcp                         # Add swat service used via inetd

(note the above line is contained wholly on a single line). If the line has a # in front of it remove the #, if the line does not exist add it exactly as above. Save and exit the file.

6) At a root promp type

# /etc/rc.d/init.d/inet stop <CR>
# /etc/rc.d/init.d/inet start <CR>

7) Start X running if it is not already and start netscape
8) go to the following URL: http://localhost:901

You will be presented with a password prompt enter root and the root password. (Only do this from the from the machine you are configuring because you are using the root password)

Now you will be at a menu prompt from which you can configure SAMBA. The first page is help files which explain the usage of SAMBA across the top there are 7 icons:
HOME, GLOBALS, SHARES, PRINTERS, STATUS, VIEW, and PASSWORD

You are on the HOME page, click on GLOBALS. Here you can set the workgroup SAMBA will show up in, the machines netbios name, server string and other items. Most important is the Security options. If you network is using encrypted passwords on windows (Win 98 and Nt do by default, Win 95 does if you have added SP3 I think) make sure to set the encrypted passwords to yes. You can read the help files for the rest of the of this page. Commit the changes before leaving this page.

The Shares icon will let you share out sections of the filesystem as desired. Also commit changes before leaving this page.

If you selected encrypted passwords go to the status icon and restart both smbd and nmbd. Now go to the password Icon and using the server password Management area enter your user name and password, do this for each user on the box. SAMBA will make encrypted passwords when you do this.

At this point all should be well and you should be able to get a share mounted from windows.

Good Luck
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
biardCommented:
Like he said, if you can't ping, you can't SAMBA.
0
lewisgCommented:
When you type ping 192.168.0.11 on the windows box EXACTLY what is the reply?

When you type ping 192.168.0.6 on the linux box EXACTLY what is the reply?

Do the RX or TX counters increase in either case?
0
karim1Commented:
Hi,

Did you setup a router ?

maybe that the only thing you need.

give the results for
route in the linux box

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.