• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ClarkConnect troubles.

fuzzybabybunny

Moderator<br>Digital & Video Cameras
Moderator
Ok, I'm having more trouble now.

I installed an empty 160GB in the CC box. It's hdb, and I edited fstab:

/dev/hdb, /mnt/2C, ext3, defaults, 0 0

I then did

mkdir /mnt/2C

mount /dev/hdb /mnt/2C

I want to share /mnt/2C with my Windows machine.

CC comes with a bunch of default shares like /home/shared, /var/www, and all of these share fine with my Windows box. I can copy files to them, read files to them, delete files on them, etc. The problem is that there doesn't seem to be a way to just share a custome directory like /mnt/2C. I have to use something called a 'flexshare'

Use the Flexshare module to add custom file shares.

The flexshare directory is uneditable, and if I create a 2C flexshare, its directory is /var/flexshare/shares/2c. So I go back and remount the drive and edit fstab to /var/flexshare/shares/2c. I have no idea how to edit this flexshare properties thing, and this is what I have so far:

Enabled: yes
Share Name: flex-2c
Server URL: \\gateway.clarkconnect.lan\flex-2c
Comment: none
Public Access: yes
Group Owner: what the heck is this??? There's root, bin, daemon, adm, tty, the list goes on and on. Documentation does not specify what this means.
Permissions: Read/Write
File Write Attributes: rwx, rwx, rwx

Whenever I try to copy a file to my 2c flexshare, Windows gives an error saying the disk is full or write protected. Any idea what's going on?

*******old post**********

I am so frustrated I am about to cry.

I ordered an 8 port unmanaged gigabit switch. I finally have some free time to install Clark Connect. I've been *trying* to get a frickin' file server up for the past three months, but I've been bogged down by countless hardware issues and lack of free time.

I plug the Cat5 from my modem to my onboard LAN in the linux box and guess what? The onboard LAN is blown. Wow. It was working fine with Ubuntu a week or two ago, apt-getting stuff, etc. And now, after sitting in my room not even turned on, it's dead. No lights. No link. Changed wires. Nothing.

Here is my setup:

http://fuzzybabybunny.smugmug.com/gallery/1650588/2/115234663/Large

I booted into ClarkConnect and eth0 is the onboard LAN and designated as External, the card that connects to the modem. Of course, this is non-working. I can't figure out how the heck to set one of my other NICs to External.

Here's the settings that I do for the other NIC (eth1):
External - ok
DHCP - ok
HostName - what in God's name is this?
automatic DNS servers - check ok

I enter in this information, and the settings NEVER stick. It keeps on kicking me back to the HostName box to re-enter a hostname. I have no idea what a Hostname is. I've tried 'server,' 'gateway.clarkconnect.lan,' 'server.lan,' and nothing works.

When I try to edit eth0 to have it NOT be external, the same thing happens.

The thing that frustrates me to absolutely no end is that these quick startup guides NEVER work. There's always something that goes wrong, and I have absolutely no idea how to fix it because, guess what, the guide gives no contingiency plans. And more likely than not, my main machine has no internet because the internet's hooked up to the linux box.
 
Oh ya. That is why it's a good idea to have a good knowledge about it.

Generally for Clackconnect it sets itself up as a easy everything-in-one package. I think that is generally true, but you still would need to have a Linux guy to get the initial setup going, after that then a regular person should be able to manage it.

For me personally I started off using Linux with Redhat 7.0 because Redhat was suppose to be 'easy'. I had a lot of difficulty with it until I used Slackware, which is considured 'difficult'. Well what happenned is that Slackware strips all the bullsh*t away so that as I was doing stuff it was obvious what is going on. After that _then_ Redhat was easy.

Probably the quick answer is to go into your BIOS of your machine and disable the onboard NIC completely. Since it's not working then there is no point in even having the OS aware of it. Once that happens then Linux gives device names based on first come first serve. Eth1 should then become Eth0. Eth2 should become Eth1, etc etc. Hopefully then it would be easy to get working.

Hostname is the name of the machine. It's important in Linux as thats is simply how you identify the computer.

Probably in this context it's going to be different. (I don't have any experiance with CC, but I am just giving it a educated guess) The problem is that with some ISPs and other things they use the hostname of the machine to determine it's IP address when doing the DHCP assignment stuff. It used to be that way for my cable, you had to assign your computer a specific hostname to get a DHCP lease. Now with Windows that is fine, but with Linux it's more irritating so the dhcp has the ability to send a fake hostname.

I think that is what it's asking about, but I am not sure. If it was designed correctly you should be able to leave it blank and it will default to the system's real hostname, but often these things have bugs.


See if disabling the onboard nic is helpfull. Otherwise if push comes to shove you can simply configure it manually via a text editor and ssh. I beleive CC is based on Redhat Linux, so the configuration files should be the same. Then you can bypass all the 'easy' stuff and just change the values manually. About the equivelent of registry editing in Windows, but much safer. (you simply make *.backup files of the text files your editing so you can undo your changes).
 
I think I'm just going to ignore flexshares for now and just edit fstab and smb.conf. In the smb.conf file, [shared] is one of the default shares that CC comes with, the one that I can edit, copy, paste to, etc. So I decided to just mimic this with my [2C] share name. (2C is the new 160GB HDD with ext3) 2C pops up in Windows Explorer, but I still can't write to it. I get the message "Access is denied. Make sure the disk is not full or write protected and that the file is not currently in use."

Why the heck doesn't this work? [shared] and [2C] have exactly the same properties, but [2C] doesn't work while [shared] does?

Here's my smb.conf:

login as: root
root@192.168.1.1's password:
Last login: Thu Dec 7 01:51:39 2006
[root@gateway ~]# :51:39 2:51:39 2
[root@gateway ~]# vi /etc/samba/smb.conf
# PDC
#----

add machine script = /usr/sbin/useradd -d /dev/null -g samba-clients -s /bin/false -M %u


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

include = /etc/samba/flexshare.conf

[printers]
printing = cups
path = /tmp
browseable = yes
printable = yes
public = yes
guest ok = yes

[homes]
read only = no
browseable = no

[shared]
comment = Public Shared Folder
path = /home/shared
browseable = yes
guest only = yes
writable = yes
public = yes

[2C]
comment = 2C Shared Drive
path = /mnt/2C
browseable = yes
guest only = yes
writable = yes
public = yes

[ftpsite]
comment = Public FTP Server Folder
path = /var/ftp
browseable = yes
guest only = yes
writable = yes
public = yes
Include = /etc/samba/flexshare.conf

In fstab, I mounted my 160GB like the CC tells me to here: http://ccfaq.valar.co.uk/modules.php?name=News&file=article&sid=12)

fstab:

[root@gateway ~]# vi /etc/fstab
LABEL=/1 / ext3 defaults 1 1
LABEL=/boot1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
LABEL=SWAP-hda2 swap swap defaults 0 0
/dev/hdb /mnt/2C ext3 auto 1 2

 
are you directly editing the smb.conf? if you are then STOP and use the web interface that they provide, as that will be much easier. if you only have eth0 then you will have to shut down iptables (iptable -F) then access it by

https://your_ip_here:81

and log in wth root uname and passwrd and go from there, make sure that you enable port 81 in the firewall for the interface that you attach to it on so that you can get back folliowing a reboot and don't have to ssh in to kill the iptables again.
 
I got it with the help of skyking. It was just some ownership issues. The drive mount points were owned by root when they should have been owned by nobody.
 
Back
Top