@JaredBusch said:

No, this is whining. Wah! I've slurped your services for 10 year, why you no give me immediate service!

Opened a help ticket with Dropbox support. They said to allow 1-3 business days for response...GRR!!

Yeah, but I've been a member for close to a decade...never had an issue like this before...

No, I was just stating a fact. I'm aware of how support works...

I wasn't complaining. I know I haven't paid a penny for all that time and that my issues are way down the chain compared to their paying customers. I'm neither ignorant nor stupid. Why do you have such an issue with me Jared?

@thanksaj said:

@NetworkNerdWifey said:

I'm just glad you didn't kill yourself on the long drive from here to NY without stopping to sleep. insert angry momma face here

Thanks Brandi...I was okay. I would have been in bigger trouble if I HAD stopped to sleep, to be perfectly honest...

I'm often like that too. A little sleep can do a lot of damage.

It's always best practice to disable root login over SSH, especially from the Internet; use su or sudo for root access. Another good practice is to disable password-based authentication; only use keys with a passphrase. The setup you're doing here is useful for allowing scripted/automated connections between machines (e.g. for backups, scheduled tasks, etc) but they should be accounts with limited access, not root. You should be creating layers that make it difficult for someone to gain access to your systems; root keys with no passphrase means you're solely relying on that one strong password (which is one keylogger away from being defeated.)

@Rob-Dunn Yup, I hope it helps!

Glad you had a good experience.
Some clown over here got owned with a speeding fine recently.
$1000
14 demerit points (only get 12)
Car impounded for 28 days ($900 to get it back)
Suspended drivers license for 6 months.

Double Demerits are still in effect as someone found out today. Remember you only have 12 points. #slowdownsavelives http://t.co/6iWSzcxFGp

I use the highly secure leave-it-off function on my home PC. If my assistance is requested at home by Mrs nadnerB, then I use Teamviewer.

@scottalanmiller said:

Any UNIX box will function as a syslog server. But better you implement ELK, Splunk or get a service like Loggly. All are free at your scale. ELK is free at any scale.

Hmmm....

Also, when I update to 14.10, $4!+ goes haywire...

Wish I could be helpful I haven't had a need to do this since... 2010? And that was for college.

I do remember that everyone was struggling with Ubuntu to get it connected to AD but CentOS (which is what I was using at the time) worked flawlessly.

@scottalanmiller said:

@thanksaj said:

Ok, so what? Am I supposed to install a GUI into these?

Yes, TeamViewer is a remote GUI viewer. Without a GUI what are you expecting TeamViewer to even do? What would it show, a blank page? Without a GUI there is literally nothing for TeamViewer to attach to and show to you remotely.

Exactly - you should be using SSH to connect to a command line, not TeamViewer.

@dashrender said in Migrate Exchange 2003 Public Folders to Exchange 2013:

Why are you posting on a thread that is more than 2 years old?

Because he has useful resources.

@coliver said:

From my understanding a hairpin is basically a network bridge like a router. It just takes all info going in and passes it to the appropriate point on the other side.

On your linux server does the Pertino connection appear as an independent interface?

Yes.

ifconfig results:

eth0 Link encap:Ethernet HWaddr 00:0c:29:4b:35:b2
inet addr:172.16.255.20 Bcast:172.16.255.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe4b:35b2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127046 errors:0 dropped:0 overruns:0 frame:0
TX packets:283744 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33435018 (33.4 MB) TX bytes:436448592 (436.4 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:193 errors:0 dropped:0 overruns:0 frame:0
TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29941 (29.9 KB) TX bytes:29941 (29.9 KB)

pertino0 Link encap:Ethernet HWaddr 7e:a6:0f:81:df:5f
inet addr:50.203.224.9 Bcast:50.203.224.255 Mask:255.255.255.0
inet6 addr: fe80::7ca6:fff:fe81:df5f/64 Scope:Link
inet6 addr: 2001:470:813b::1bcf:0:f02/48 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2717 errors:0 dropped:0 overruns:0 frame:0
TX packets:1765 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:261357 (261.3 KB) TX bytes:464420 (464.4 KB)

@scottalanmiller said:

Did you test the system at all before installing new RAM?

I didn't, no. I do know one issue that is possible is that some Dell servers require that 4/6 memory slots be filled to even boot (learned this at my first IT job) and the memory has to match. I've got 4x512MB and 3x2GB, and while they're the same speed, etc, maybe something else like the voltage is different about them preventing it from booting.

@Dashrender said:

I'm a bit lost.

You have two NASs at home mounted to a Linux box, that you are then sharing to CIFS so you can mount them on a Windows box?

Is the Windows box not on the local LAN? If not I guess that's why you have Pertino as part of this, because you are Pertino'ing from a non local Windows box to the Linux box which is offering a pass-through to the NASs?

If your Windows box is local to NASs, why bother going through the Linux box?

The Windows box and the Linux box are both on the same LAN as the NASes. This is more so I can access the NASes easily remotely on my Pertino network.

@david.wiese said:

i setup plex on my win7 pc without any issues. Port forwarding for outside access is setup as well. It took me all of 30 minutes to install and configure so i could watch on any device inside my network. I'm not sure what issues you had however.

In all fairness, it may have been the VM I was using. I just rebuilt a new version of it, as it had originally come from my first and only ever P2V. It never seemed stable, but the new VM is much more so.

@scottalanmiller said:

Same issue still?

The logging doesn't appear to be working at all right now, which is weird.

Yup, that is a nice little unit. I think that that is one generation old (and therefore one generation newer than mine) hence the good price. Should run the latest Raidiator OS (6.x).

I found a thread on the Ubuntu forums here: ubuntuforums.org/showthread.php?t=1845962

It pointed me to a conf file located here: /etc/rsyslog.d/50-default.conf

I used vi to uncomment this line:

cron.* /var/log/cron.log

Now I should get cron logs. I'll check the other place too. Thanks!