Well, I have two units arrived now and setup. What tests would you like to see done to these?

I have the usual array of I/O testing programs* lined up & 1TB of hot fresh and nasty user data being dumped onto them.

*Solarwinds permissions view
ATTO Disk Benchmark
IO Zone
Intel NAS Performance Toolkit

What is happening is the mapped drive is sitting idle for 15 min and then disconnecting to free up resources. DB applications such as yours get these errors because this connection is not persistent as g.jacobse has eluded to with the /persistent:yes command. This will keep the drive mapped but does not stop the idle timeout from occuring which will continue your error.

Do this on the machines in question: (also can be deployed via Group policy script)

Open CMD then right click and run as administrator

net config server /autodisconnect:-1

This will set the autodisconnect to never disconnect and you should not see this error any more.

Give it a try and report back your findings.

@Vidya - Don't know if you are still able to assist, but some assistance would be welcomed.

THank you.

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

@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.

Problem resolved...

Told you it was something stupid

[root@jcloud ~]# firewall-cmd --zone=public --add-port=https/tcp --permanent; success [root@jcloud ~]# firewall-cmd --reload success [root@jcloud ~]#

ywOj3Uw.jpg

OK it's there for me now.

When you perform the same steps on OS X (Yosemite 10.10.1) it does as desired.

Screen Shot 2015-01-11 at 9.42.13 AM.png

Screen Shot 2015-01-11 at 9.43.15 AM.png

Fix the storage issue then move to VMs on the systems that you have, most likely.

Another factor that people forget with FakeRAID until it is too late... if your OS crashes your RAID is useless. With hardware RAID you can rebuild your RAID after a drive loss even when the system is offline. The datacenter people don't need to know if the OS is healthy, if it is on, etc. They can swap drives and let the RAID controller repair the array.

With FakeRAID there is no RAID until the OS works and is healthy. So even if you replace a drive, the array might be unable to repair itself.

Dealing with someone facing this problem right now. System crashed with the RAID array lost a drive and won't boot. Not the OS is having issues and there is no RAID at all.

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.

@g.jacobse said:

I agree - that type of message just tells me that I don't want to partner with you. But it is a form of cold calling...

It sure is, something that we block completely. There is good and bad cold calling, though. If you cold call me and ask to speak to me, I'm not going to be pissed, I'll just hang up. But if you cold call and demand to set something up rather than politely asking if we can.... we are done and you are actively blocked and will never get our business.

There is legitimate sales and downright unprofessional "never do business with them" sales. A company doing these tactics definitely does not believe in their own product and is trying to get sales through an intimidation style rather than through presenting a good product.

@garak0410 Not to worry then, they even have a thing that will "fix it for you" .... uh huh 🙂

I would run a repair on Windows. Sounds like you've got some corruption on your OS.

Ugh, our country is falling apart but our politicians still find the time to dick around with trivial legislation telling us what we can and can't do.

We've just implemented a signature management system by these boys www.exclaimer.co.uk, primarily to embed our company logo into all outgoing e-mails. This works a treat with on-premise Exchange and Marketing love it (by default, anything Marketing love, I hate). They also do an Office365 version.

Over all I'm pretty happy with the way it works. The medical edition does a pretty darn good job with the medical words to without any additional training.

Though one doc couldn't get the system to accept vasectomy. We had to train that one for about 3 mins, but since it's been good.

The other key is to speak punctuation. Don't bother trying to have Dragon figure it out.

@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.