IT BS thread

Most of us don't have much to contribute either. Just a whole lot of BS.

 

Oh, I have plenty of BS. I should fit in perfectly.

 

Here's my contribution for the day.

 

OMG i've only done that a time or two

 

Lol this ^

And I wish I had more experience with servers and managing them, I don't really know where to start

I do usually get calls from friends needing remote support, have you guys heard of teamviewer before? It's probably my favorite tool I have on my computer and saves me from having to use gas and drive to a friend's house.

http://www.teamviewer.com/en/download/index.aspx

You tell them to get the Quick Support one, then once it's downloaded on their machine they will give you an ID and Password. Of course on your machine you'd have to have the whole program not just the Quick Support one. It's like a simplified remote desktop

 

Teamviewer and Logmein are fantastic.

What do you feel you're lacking? I wanted to learn more about Linux servers and cli, so I built a Linux server w/o a GUI. Took a little bit to get it to the point where it does everything I want it to - and there's always more to add, but it was a great experience.

I am blessed to get to touch millions of dollars of equipment at work that I would never normally get exposed to however.... Before I got this job, I learned everything myself.

 

Well I plan to maybe apply for an IT position on my college campus over the summer. I know most of what they do is just upgrade software or possibly install new hardware, and during the course of the summer classes usually instructors will call in with quick, easy things. I don't know how they manage their machines on campus. I do know they're running Windows 7 professional and have network logins set up. If I do apply I want to at least know what to do when managing such a vast network of machines.

And here is another funny picture I found:


^^^ i might use that for my sig

 

Sub'd for later use.

I work as a service desk person in a Data Center

 

you can't go wrong with the Microsoft stuff. There is always a need for it.

One of the things that will always help you is a good basic knowledge of networking. I'm not a network person, but with a good basic knowledge, i can trouble shoot a lot of issues. Also find a way to build an environment at home and play with it. setup an email server and make it work. Setup a web server and host a web site.

Getting started in desktops and then moving to servers is very common. A lot of times when you are doing desktop trouble shooting, it is with their communications with a server.

 

Networking...hmm well I understand the basics involving Static IPs, DHCP servers, DNS, and basically anything pertaining to consumer home routers and home networks. Outside of that I know a main means for communication through the internet is though TCP/IP, I know that there is different protocols like HTTP/HTTPs and FTP.

 

That's a good start. Knowing things like that make you more valuable to a company because you can do more than just one little thing. It gives you the ability to troubleshoot an issue from beginning to end.

here are some of the more advanced topics that you will run into in the enterprise.

Firewalls, VLANS and VLAN tagging, basic routing (reading a route table).

 

Troubleshooting! Yes, I definitely know how to use Ping and Traceroute.

Firewalls, I know the basic is that it's either software on the end users machine or on the router itself, with the router option being more common? And that theyre used to monitor traffic entering and leaving the company's network.

VLAN and VLAN tagging I've heard of that acronym before but I don't know what it is.

What would a routing table look like? Do you have any samples I can have a read at?

 

You can look at one on your workstation if you wish.

cmd -> route print on Windoze. route -v on Linux.

 

every machine has a route table - here is an example. It explains where your traffic is going to go based on the IP it is going to. It looks like a bunch of garbage but the first line says that any IP will use 10.24.70.253 as the gateway to get there.

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.24.70.253 10.24.70.23 20
10.24.70.0 255.255.255.0 On-link 10.24.70.23 276
10.24.70.23 255.255.255.255 On-link 10.24.70.23 276
10.24.70.255 255.255.255.255 On-link 10.24.70.23 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.24.70.23 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.24.70.23 276
===========================================================================
Persistent Routes:
None

 

http://en.wikipedia.org/wiki/Virtual_LAN

 

+ there's hardware and software firewalls .

 

you guys will get a kick out of this

http://evilrouters.net/achievement-unlocked/

 

I have wayyyy too many of those...

 

VLAN's are Virtual LAN's. It's a way of creating multiple networks inside a router and switch which can then segment different devices from one another.