Silly Question but the "server" can i just connect it to extra port on my router or does it need to be set up a special way?

Originally Posted by remeron
hi there, everything is up and working for me.
but i can't figure out how to access my linux box (at home) thru internet with putty. i am trying to use putty to access my linux box to get into command line. when i'm at home, it works well locally (when i use my xp machine to putty to my linux box). but i can't from work. i've already registered with dyndns and i could access my utorrent webui (i'm using utorrent instead of torrentflux cause flux doesn't allow proxy) from work.

help?

Make sure the SSH port is redirected on your router ;)

Originally Posted by Enforcer
Silly Question but the "server" can i just connect it to extra port on my router or does it need to be set up a special way?

Just attach it like you would attach any pc.

I am having problems finishing up the ftp part here. I installed ProFTPd without a hitch but got the line 98 problem. Using the fix from 'TheEclipse' I changed the server name from Deepthought to my own but now get:

* Starting ftp server proftpd
- IPv6 getaddrinfo 'stack-server.stack' error: No address associated with hostname

When I check my network properties I see that the correct ip address is associated so I have no clue what to try next. Any ideas?

Are you sure your hostname is associated with an IPv6 IP adress? I highly doubt that, because IPv6 adresses aren't all that readable, and everybody uses IPv4 adresses ;)

Does the proftpdservice itself start?

Originally Posted by Glider
Make sure the SSH port is redirected on your router ;)

When you say that you mean, i need to port forward the SSH port on my router right?
what's the port by the way..is it 22?

Edit: It's okay now. It's just a matter of forwarding the SSH port on my router. silly me. thanks for a great guide Glider.

I started over and still had the problems with the line 98 issue. I decided to go with your change instead of TheEclipses (why, no clue). It still told me that no address is associated with the hostname, but i've read by searching these 400+ entries that it doesn't matter (why, no clue). Now i'm immediately running into problems with the "vncpasswd ~/.vnc/passwd" part the same way that Hu had on page 19:

The program 'vncpasswd' can be found in the following packages:
* vnc-common
* vnc4-common
Try: apt-get install <selected package>
bash: vncpasswd: command not found

Hu says that changing "vncpasswd ~/.vnc/passwd" to "x11vnc -storepasswd" fixes the problem (why, no clue). Is this true/recommended?

Glider, I have no intention of sounding ungrateful here, but is it possible to go through your tut again and change the inconsistencies? I am really trying to understand/learn what I'm doing here but it seems i run into a new problem with every step. (I figured out the samba part from the beginning by creating a common workgroup with windows, that seems important for many other newbs).

Please try your whole process from the beginning and notice what steps you might have left out. It will also save yourself the hassle of responding to everyone's individual problems.

Seriously though, thanks for the time you've put in and I only hope to help.

Originally Posted by Glider
Is there an X server running after you've rebooted? If not it's logically that VNC can't connect to it ;)

Also, don't start the VNC server as root (ie. with sudo), it has to connect to an user session.

Thanks!
I started it as root, that was the problem.

Glider the guide was awesome! however, when I couldn't get your ftp config to work I tried Eclipse's and while the ftp starts ok, and I can connect, it seems to disconnect right away. Any idea why?

Are you using the correct username and password? Can you post the output of "sudo netstat -taunp"?

Username and password are ok.

Heres the info you requested:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:2208          0.0.0.0:*               LISTEN     4958/hpiod
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN     5049/smbd
tcp        0      0 0.0.0.0:5900            0.0.0.0:*               LISTEN     5346/x11vnc
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN     5121/proftpd: (acce
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN     5777/cupsd
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN     5049/smbd
tcp        0      0 127.0.0.1:2207          0.0.0.0:*               LISTEN     4961/python
tcp        0      0 192.168.1.110:139       192.168.1.127:3958      ESTABLISHED7520/smbd
tcp        0      0 192.168.1.110:445       192.168.1.124:49807     ESTABLISHED6220/smbd
tcp        0      0 192.168.1.110:139       192.168.1.138:49218     ESTABLISHED7542/smbd
tcp        0      0 192.168.1.110:139       192.168.1.132:62803     ESTABLISHED5869/smbd
tcp        0      0 192.168.1.110:445       192.168.1.123:1750      ESTABLISHED7570/smbd
tcp        0      0 192.168.1.110:139       192.168.1.128:49211     ESTABLISHED7517/smbd
tcp        0      0 192.168.1.110:139       192.168.1.137:49176     ESTABLISHED7371/smbd
tcp6       0      0 :::22                   :::*                    LISTEN     5069/sshd
tcp6       0      0 ::ffff:192.168.1.110:22 ::ffff:192.168.1.:52628 ESTABLISHED7732/1
udp        0      0 0.0.0.0:32768           0.0.0.0:*                          4811/avahi-daemon:
udp        0      0 192.168.1.110:137       0.0.0.0:*                          5047/nmbd
udp        0      0 0.0.0.0:137             0.0.0.0:*                          5047/nmbd
udp        0      0 192.168.1.110:138       0.0.0.0:*                          5047/nmbd
udp        0      0 0.0.0.0:138             0.0.0.0:*                          5047/nmbd
udp        0      0 0.0.0.0:68              0.0.0.0:*                          4073/dhclient3
udp        0      0 0.0.0.0:5353            0.0.0.0:*                          4811/avahi-daemon:

Originally Posted by acidfire

Code:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN     5121/proftpd: (acce

As you can see proftpd is clearly running and listening.

Try to connect to it from the local machine:

ftp <IP>

and see if you can connect locally

and that works no problem, however through fireftp & smartftp on the local networks i can't seem to connect for long. I do get a 220 response but then the connection seems to drop.

Are you running any firewalls on your network?

no, just the usual stuff blocking outside traffic, nothing inside.

And on the XP machine? That firewall does block outgoing connections... Server side everything seems fine...

nope not on and still nothing :(

i got my ssh to work (i am able to putty to my linux comp at home from work). but how do i get vnc to work?
when i type "localhost:0" at the server field of ultravnc, it says connection error. i know i'm doing something wrong but can't figure out.

update: figured out the vnc thing now. seems like everything i write here, i get an epiphany and manage to get things working.

if it helps, this is what I get with ftp:
220 DeepThought
USER chrisg
331 Password required for chrisg.
PASS (password not shown)
230 User chrisg logged in.
NOOP
200 NOOP command successful
TYPE A
200 Type set to A
CWD /
250 CWD command successful
PASV
227 Entering Passive Mode (192,168,1,110,56,251).
LIST
and this is where it hangs up and restarts the connection.

I'm having prob's trying to connect to the the server via the ip. everything looks ok , i'm on the setting up of samba

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 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 commentary 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 made any basic syntactic 
# errors. 
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = server

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
;   wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = true



#### Debugging/Accounting ####

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

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

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
;   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 1

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
;   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = smbpasswd

   obey pam restrictions = yes

;   guest account = nobody
   invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
;   unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
;   pam password change = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
;   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
;   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
;   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
;   printer admin = @lpadmin


############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
;   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = yes

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
;   valid users = %S

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
;   writable = yes

# File creation mask is set to 0600 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0664.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   public = no
   writable = no
   create mode = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
;   write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   writable = no
;   locking = no
;   path = /cdrom
;   public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

It seems that you are only sharing printers, not data

ok how do i fix it to share data

the smb.conf is more or less what came with samba. i edited as much as i could find, replacing what i was told to replace via the tut.

you can add something like

[ShareName]
        path = /path/to/share
        Comment = Whatever Comment you want
        browseable = yes
        writable = yes

Also, if you want to share the home directories

[homes]
        comment = Home Directories
        browseable = yes
        writable = yes
        security mask = 0700
        create mask = 0700

Grr still no luck at getting it to work

This is all new to me but I am going to give it ago. Is there a way you can use this server as an Email Exchange as well?