Networking a Windows ME and RedHat Linux 7.0

On the windows machine, go Start/Run/winipcfg. Does it list an IP address?

The Linksys router that you are using, assigns IP addresses. It's default address is 192.168.1.1. Your card should be something like this 192.168.1.2 or 192.168.1.3 . If it is not, I would change (on the Windows machine), the IP address to be one of these values.

Your linux box should be in the same range run ifconfig and you can see what it assigned it.

You can also tell your router what IP's to use.

Don't worry about your webserver now. Set up your share and then we will go from there.

But what is wrong with the windows?
It shuts down when i try to add it as a network connection.

Has networking worked before on this machine? If not you probably have a resource conflict with the NIC and another system device. Do this:
Press the Start Button
Go to Programs
Accessories
System Information
IRQ's

Cut and paste that information here.

Networking has not worked here before.

IRQ 0 System timer OK
IRQ 1 Microsoft Keyboard OK
IRQ 2 Programmable interrupt controller OK
IRQ 3 Linksys Lnepci II Ethernet PCI Adapter OK
IRQ 3 ACPI IRQ Holder for PCI IRQ Steering OK
IRQ 4 Communications Port (COM1) OK
IRQ 6 Standard Floppy Disk Controller OK
IRQ 7 ECP Printer Port (LPT1) OK
IRQ 8 System CMOS/real time clock OK
IRQ 9 SCI IRQ used by ACPI bus OK
IRQ 9 Conexant PCI Modem Enumerator OK
IRQ 9 Intel(r) 82801AA USB Universal Host Controller OK
IRQ 9 ACPI IRQ Holder for PCI IRQ Steering OK
IRQ 10 Creative Sound Blaster AudioPCI 64V (WDM) OK
IRQ 10 Intel 82801AA SMBus Controller OK
IRQ 10 ACPI IRQ Holder for PCI IRQ Steering OK
IRQ 11 Intel(r) 82810E Graphics Controller OK
IRQ 11 ACPI IRQ Holder for PCI IRQ Steering OK
IRQ 12 WheelMouse2 (PS/2) OK
IRQ 13 Numeric data processor OK
IRQ 14 Intel 82801AA Bus Master IDE Controller OK
IRQ 14 Primary IDE controller (dual fifo) OK
IRQ 15 Intel 82801AA Bus Master IDE Controller OK
IRQ 15 Secondary IDE controller (dual fifo) OK

Is that what you wanted?

OK
I have this computer hooked up... I fixed it and the networking wizard hooked it up.
It won't, however, see the Linux.
Do I need a client program to see the Linux and share the files?
Thanks

Okay, here is what you need:

Windows side

• Client for MS networking
• TCP/IP bound to NIC
• Computer Name

  Linux Side

• smb server should be started. This can be verified by ps aux
• user name that is the same as the logon name on your Windows ME system.
• Some directory to share.

If you can't see Linux from Windows, more than likely your samba server is not started. There could be several reasons for this. One is that it encountered errors in smb.conf and couldn't load. Check your log files to find errors. Another could be that samba is not installed. Still another could be that the IP addresses and/or workgroups are not the same.

Check your log files, log.smb & log.nmb & sometimes you will have a log called log.[user name].

Fortunately once you get Samba setup, Apache is a breeze to get going.

When I go to Network Places on the windows ME, it says "unable to access network"
What's wrong?

Well I fixed that problem myself
But, when I go to add network place, and put in \\comuptername
it asks for a password
I do not know what this password is or where to find it
Please help!

Here is what you have:

Linux - adduser = name of user that you login to your windows box. The password for this user will be the one that it is asking you for.

Also make sure about the encrypted password option.

I'm a bit confused what you said to do
Where do I type that?
command line?
in smb.conf?

At the command line in Linux.

Well I found out that the problem is, Windows ME won't allow a plain text password for networking...
I am supposed to add a registry file, but that didn't work, or I didn't do it correctly... any other suggestions?

You don't need to edit your registry.

All you need to do is make sure that the following line is uncommented (take out the # sign in front) in smb.conf.

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes

Trust me on this one. I have only done it a couple of hundred times.

tried that
doesn't work

Do me a favor. Cut and paste your /etc/smb.conf file here. I will look at it and see if I can determine the problem.

here it is:
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = @home

# server string is the equivalent of the NT Description field
server string = Samba Server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 192.168.1.20 192.168.1.21

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
printing = lprng

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
max log size = 0

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server or
# security = domain
; password server =

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /usr/bin/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = yes
writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
[CC231795-A]
comment = Shared Files
path = /home/CC231795-A
guest ok = yes
writable = yes
share modes =yes

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = yes
printable = yes

# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
[public]
path = /usr/somewhere/else/public
public = yes
only guest = yes
writable = yes
printable = yes

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

[parrabal]
available=yes
browseable=yes
path=/
guest only=no
writeable=yes
only user=no
public=yes

Try making these changes:

# Un-comment the following and create the netlogon directory for Domain Logons
[CC231795-A]
comment = Shared Files
path = /home/CC231795-A
guest ok = yes
browseable = yes
writable = yes
remove this line share modes =yes
valid users = (your username)

Be sure to run smbd SIGHUP

Post back if you still are having problems. It will be later tonight before I can get back to you.

Ok...
Somehow I managed to FTP into the linux from the windows, and I don't know how.
I reinstalled, and I can't FTP again.
I FTPd from the linux to this windows, and transferred a few files, but when I do
lynx localhost
it says "You do not have permission to access / on this server"

A couple of things to try.

(1.) You have three files located in the etc directory.
hosts - gives system name and any other servers on your network.
hosts.allow - says who can logon your system.
hosts.deny - says who can't logon your system.
Generally the way it is done is to deny all in hosts.deny and allow only you in hosts.allow.

It could be a permission problem. To check this go to your ftp directory and type in ls -l . This will tell you who the owner and group of this directory is. You can change the ownership by:
chown yourusername /home/ftp
chgrp yourusergroup /home/ftp

Let me know how this works.

Any luck on setting up the samba share?

Well, I wasn't sure what to do with the host.allow and hosts files.
No luck with samba share
I am trying to compare my old httpd.conf file but it says my disk is invalid...
I'll try again
What do I do with chown username /home/web
what username do I do? root?

hosts.deny ALL:ALL

hosts.allow
#Allow localhost
ALL : 127.0.0.1
# Allow my other box to connect to any service
ALL : IP address of Windows machine

If your ftp directory is root, then you will not be able to upload files to it. You can change it to nobody to allow anyone to do anything.

httpd.conf has nothing to do with ftp. ftp is controlled by the inetd daemon.

I'm still getting "403 Permission Denied"

Explain it to me again.

How are you trying to connect through a ftp program or web browser? Please give me the details.

I'm trying to run Apache
I have httpd started (I think)
I configured it
When I type:
lynx localhost
it says, "Error 403: http forbidden"
I've changed permissions, I've changed httpd.conf many times
I need to get this fixed!

Your apache directory is most likely set to root.

To see if apache is running (which it is, otherwise you won't get the 403 error). Type is ps aux | less . This shows all of your running processes. the | less part slows down the output so it doesn't scroll off of the screen. q will quit.

For Apache, you will have several running processes, a root process and several child processes.

Apache has a serverroot directory (usually /usr/local/apache, although Redhat uses /etc/httpd). You can also have a virtualhost directory. Wherever your pages are served from via httpd.conf, you need to change that directories ownership and group. It needs to be changed to whatever httpd.conf says for User and Group. This is usually nobody or webuser and webgroup.

So you need to change the permissions on the directory that your pages are served from like this (assuming that the user, group = nobody):

chown nobody (htdocs directory)
chgrp nobody (htdocs directory)
You will also need to change the files in the directory like so:
cd (htdocs directory)
chown nobody *
chgrp nobody *

That should fix you up. Let me know.

Also any time a change is made to httpd.conf, you need to restart the server. The way to do that is like this:
ps aux | less Find apache root process id.
kill (root process id)
httpd -d (serverroot directory) Restarts apache.

Well I figured out that I needed to set chown and chgrp to apache
I can access the site on the intranet, but not internet
I have apache started and all, but It won't put the files on the Internet, only intranet.
I can get to my site by typing the internal IP, but not the external IP

When you say external I assume that you are referring to accessing from the Windows machine. If so you should be able to access it by opening up your browser on the Windows machine and typing in:
http://(localhost). Localhost in this case is not what you use but the machine name of the Linux box. Here is how to do so:

(1.) Make sure that your machine actually has a name. Do this by editing your host file in /etc/hosts. It should have a line like this: (IP Address (hostname). So if you wanted your machine to be called Nike and your IP address was 192.168.100.1, then it would look like this 192.168.100.1 Nike.

(2.) Make sure that this machine name is specified in your httpd.conf file. The section called ServerName should also be the same as in the hosts file. In our example, it would look like so: ServerName Nike.

(3.) That will do it but you should probably also change your hosts file in Windows. The setup is the same.
(4.) Now you should be able to access your system via the browser. In our example, type in http://Nike. This will load the Apache index file.

Hope this helps.

nope nope nope
None of that worked.
Thanks for trying though
I have managed to get my site attached to my internal IP (192.168.1.20) and I have port forwarding set up on the router (port 80)
The Windows machine has Apache stopped
Linux has HTTPD started
When I have the Windows machine running with apache, it runs just fine and everything is put on the internet, but the Linux just won't
I have configured them just about the same.
What is wrong?
Should I start a new thread?