Good day everyone!

I have been offered an internship at a local network security company that offers a course in Certified Ethical Hacking. During the course of my first interview I was informed a second interview would take place and it would involve working with a Linux server and windows and making them work together.

I have a Linux server at home for personal use, namely hosting game servers for my friends, so I understand how to start it up and run a few commands but I am very noob with Linux's back end like advanced networking and helping the two machines talk to each other.

My question is what would be the best thing to learn over the space of 2 weeks to help me pass the interview test. If anyone can point me the right direction I would really appreciate it.

Regards,
Michael.

Hello and welcome to LQ.

Almost every task you may know in windows is similar to the same tasks in linux. Just different names usually. So don't get overboard.

"Talking to each other" Guess you could study up on various ways two computers may interact or share resources. tcp/ip and anything to do with resource sharing like ftp, ntp and secure means like sftp or ssh or https.


Guess you could ask them what they'd want you to know?

1 members found this post helpful.

"Welcome, Coldfire!" So, let's get started!

First of all, let me introduce you to VirtualBox! Armed with this totally-free "virtual machine monitor," which just happens to be backed by one of the largest software companies in the world, you can forthwith construct "a Windows environment on your Linux box," or "a Linux environment on your Windows box," as the case might be, and thus to run "the two environments-of-interest" together.

First ... (uh huh...) "figure out" how to do that!

Next, you need to subject yourself ... willingly ... to the self-educational experience that a writer (from a few decades ago) called, "A Sip From The Fire-Hose."

In order for two obviously-different operating systems to "work together," it is necessary for the two of them to negotiate a common ground. (In this case,a common "network file-system.") There are several common standards that the two of them could converge on – such as NFS – but let us for the sake of convenience presume that they will instead choose Windows' on "home turf," SMB. Which means that you must now take a self-induced crash course in Samba, this being the Linux-based "client" which enables active participation in an otherwise Windows-based network.

I very-strongly encourage you to embrace this challenge, and to realize that this is precisely what your first-interviewer intended, when (s)he purposely gave you time to prepare. If "at first panic" you feel that you've just been hit in the face with a hot cast-iron skillet ... "pwang-g-g-g-g!!" ... just get used to it. (If, right now, you do not feel "more-or-less sheer panic," then something is dreadfully wrong.) ... "It will pass."

Meanwhile – "get started," and feel free to ask any sort of questions you might subsequently see fit ... right here. "You are," shall we say, "among many friends."

- - -
P.S. I have complete confidence that you will succeed in your second interview! ... ("Now, get busy!")

2 members found this post helpful.