Results 1 to 3 of 3

Thread: Accessing A Knoppix PC from A Windows Network - Password?

  1. #1
    Junior Member
    Join Date
    Feb 2005
    Posts
    3

    Accessing A Knoppix PC from A Windows Network - Password?

    Total NOOBY alert!!!!

    Okay, I am running from CD, and I am looking at what is possible before I commit to a HDD install.

    Most importantly, I want total transparent operation on my home network. (3 other PC's running Win98 and WinXP Pro)

    Now, via the Control Center and / or Samba I have managed to get my Knoppix PC visible on the network as KNOPPIX with the comment Samba Server 3.09 Debain next to it.

    But, when I click on it from a windows PC it asks me for a password.to get access. What Password??

    If I can't get this to work, I'll be using the Knoppix CD as a coaster, that's all it will be good for if I can't get access.

    In addition, how do I browse my network from Knoppix?

    Sorry if it is a dopey question, and before anyone asks I have done a search of the forums before asking

    Archie

  2. #2
    Junior Member
    Join Date
    Feb 2005
    Posts
    3
    Okay, I just found Samba Network Neigborhood under Knoppix Utilities on the panel, Yikes, this menu is so illogical it hurts.

  3. #3
    Senior Member registered user
    Join Date
    May 2003
    Posts
    981

    Re: Accessing A Knoppix PC from A Windows Network - Password

    Quote Originally Posted by archiebald

    If I can't get this to work, I'll be using the Knoppix CD as a coaster, that's all it will be good for if I can't get access.

    Archie
    We don't want no coasters!

    Check out this doc:
    http://www.knoppix.net/wiki/Smb_Client_HowTo

    Google for 'SMB how to', Samba how to' etc.



    Also, here is something which helped me get set up a long time ago. I don't use samba any more, I hardly ever run windows.



    Confirm that your network settings are correct and working. Open a terminal or DOS box (depending on the machine) and type ping ipaddress.ofthe.other.machine. If one PC can't reach the other, that's your first problem.

    Make sure file sharing is installed under Windows. Also make sure that the "Network Authentication" tab below the protocols is set to "Windows Logon" and not "Client for Microsoft Networks" to reduce the level of authentication to something we can work with.

    Check your Windows workgroup name and computer name. If necessary, reset these in the Network Connection Wizard (Windows, especially ME is a bit notorious for losing these settings without warning).

    Share some folders under Windows. I don't know if ME has the level of authentication that 2K and XP have, where you must add users intending to access shares from another box as users to the sharing box in order for them to be seen. If so, do that.

    In Linux, open up /etc/samba/smb.conf as root (or su to root and open it from a terminal, if you know how to do that).

    Change the WORKGROUP setting to the same name as under Windows.

    Check the other settings in the file to see if anything leaps out at you as needing to be changed, but otherwise add a share to the end of the file by using one of the examples (uncomment it, or copy it and uncomment it, changing the share name and path to reflect your system-- and don't forget, folders can only be shared from your own ${HOME} directory). The general syntax for a Samba share is:

    [SHARE_NAME_(no spaces allowed)]
    path = /home/username/foldername
    comment = what_will_appear_in_the_tooltip/comment
    public = yes
    guest ok = yes
    writable = no

    Save any changes, close smb.conf and open /etc/hostname (also as root).

    Type your hostname (the name of your Linux box), if it does not appear.

    Save and close /etc/hostname, and open /etc/hosts (still as root). Next to "127.0.0.1 localhost", add your hostname, so that it reads "127.0.0.1 localhost your_real_hostname". This helps sometimes in making sure that everybody knows that localhost and your_hostname are the same box.

    Save and close the text editor, and open your Users and Groups management tool (if you use KDE, that would be KUser, I believe). Add your WinME user and other Linux user as users, using the same usernames and passwords as they have under the other OSes. If you have the option to not create a Home folder for them, you can take it, unless they'll need one for some reason. Save these changes and exit the tool.

    Open a terminal, su to root (or log out and log in as root, but really, using the su command is better) and type smbpasswd -a -e username_of_the_ME_user password_of_the_ME_user and hit enter. This will add that user to the smbusers list, which means that Samba won't refuse their connection when they try to access the files shared on your box. Repeat for any other users on the ME or Linux boxes.

    Reboot. You could just (re)start the Samba server using the command '/etc/rc.d/init.d/smb stop' and then '/etc/rc.d/init.d/smb start', of course, but I don't know if having a share set will cause the server service to automatically start at boot, and rebooting now is the easiest way to find out. Log in as a regular user. At this point, the ME box should be able to see and access your shares. If not, it means that the Samba server isn't started, so start it with the command above. You may have to wait for the network to refresh to see the shares, which can take up to 15 minutes.

    Now, open LinNeighborhood. Go to the Options and set everything how you want it (default mount points, default username/pw, etc). Also, you will want to set "Memorize Shares/Remount on next startup" to active. I usually like to set "ask username/pw once" as well, otherwise it's a PITA. Don't forget to save the new options.

    Scan the network and mount the shares you want.

    Close LinNeighborhood and open either your Startup folder if using KDE (I believe it's in /home/username/.kde (the dot means it's a hidden folder, so unhide hidden folders if you can't see it)/startup, or the GNOME Control Panel=>Advanced=>Session Manager if using GNOME (sorry I don't know how to create startup shortcuts for other WMs).

    In any case, you want to make the following shortcut: LinNeighborhood -m (may need to enter full path to LinNeighborhood, some distros don't recognize it only by name) which tells it to mount the memorized shares without starting the GUI and then exit.

Similar Threads

  1. Accessing hard drive (NTFS - Windows XP) from USB Knoppix??
    By tecnoL in forum MS Windows & New to Linux
    Replies: 3
    Last Post: 04-10-2007, 11:56 AM
  2. Accessing files von network shares
    By Deadman in forum Networking
    Replies: 0
    Last Post: 11-24-2005, 08:19 PM
  3. problem accessing windows network drive
    By cli168 in forum MS Windows & New to Linux
    Replies: 4
    Last Post: 06-17-2005, 11:03 PM
  4. Accessing Windows Registry Through Knoppix
    By kaplan71 in forum MS Windows & New to Linux
    Replies: 5
    Last Post: 02-24-2005, 10:09 AM
  5. Accessing Windows Files
    By standmatt in forum Hdd Install / Debian / Apt
    Replies: 8
    Last Post: 10-07-2003, 05:10 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's

$299.00



HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED picture

HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED

$179.99



HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ* picture

HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ*

$94.99



HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's

$229.99



HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD picture

HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD

$750.00



ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM picture

ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM

$170.00



HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs picture

HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs

$399.00



HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs picture

HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs

$102.59



HP ProLiant Microserver Micro Server HSTNS-5151 untested picture

HP ProLiant Microserver Micro Server HSTNS-5151 untested

$75.00



HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001 picture

HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001

$849.99