Do I look like a DHCP server to you? WARNING - Work Rant

[shiner]

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: arod
You guys just hand out IP to any computer on the network? Thats kinda dangerous... We have DHCP but the computers MAC address is assigned an IP and that has to be keyed into the system inorder for it to get an ip from the dhcp server. He may have been asking you to do that but didnt communicate it very well.

We do but we don't. Before a workstation goes in the network port has to be made hot. In the past they had all ports hot all the time but that got them into trouble. Now before a tech takes a workstation out to deploy it he has to give our network team the port number he needs made hot. We suggested tying the IP address to the MAC but upper management here didn't want to do that. I work for a consulting firm that manages the helpdesk, desktop, server, and network engineering groups for this customer and they get the final say in how we do things. We make suggestions, but sometimes they don't want to go with what we suggest. For the most part I don't have to deal with silly stuff since they tend to leave the server team alone to do what we want. Occasionally though they do ignore our suggestions and say something has to be done such and such way. That usually lasts until they get bitten in the ass by the poor decision and then they come around to our way of thinking.

Maybe you should have trained him on how your office handles its computer addressing schemes. It sounds like you just handed him a PC and had him set it up himself. Then you get annoyed when he relies on knowledge from a previous job since you never told him your way of doing things. Maybe you should get some better management skills and stop critisizing your employees.

Maybe you should kiss my ass. He's not my employee. He works on the desktop team, it's not my job to make sure those people know how to do their jobs.

 

[shiner]

Originally posted by: wyvrn
This is a prime example of a paper cert. In addition to those certifications, your company should have required verifiable working experience. Sucks to be you in that case!

That is a problem here. For the desktop and helpdesk positions here they don't require much experience. In fact most of our helpdesk people are fresh out of college and have no real world work experience. The desktop guys/gals aren't quite as bad, but it's rare to find one on that team here that has been actually working in the I.T. field for more than a year or two.

 

[Spyro]

Originally posted by: Nemesis77
You should have just said "Sure. The IP is.... 127.0.0.1"

😛

Yeah, it makes sense too.

 

[busmaster11]

Originally posted by: shinerburke

Originally posted by: wyvrn
This is a prime example of a paper cert. In addition to those certifications, your company should have required verifiable working experience. Sucks to be you in that case!

That is a problem here. For the desktop and helpdesk positions here they don't require much experience. In fact most of our helpdesk people are fresh out of college and have no real world work experience. The desktop guys/gals aren't quite as bad, but it's rare to find one on that team here that has been actually working in the I.T. field for more than a year or two.

What the hell!!! I'm a lan manager with a good CURRENT job but looking to relocate to Chicago. In Chicago, with my three years of solid experience I can't even find a helpdesk job!!!

 

[FoBoT]

maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

 

[Arkitech]

Originally posted by: busmaster11

Originally posted by: shinerburke

Originally posted by: wyvrn
This is a prime example of a paper cert. In addition to those certifications, your company should have required verifiable working experience. Sucks to be you in that case!

That is a problem here. For the desktop and helpdesk positions here they don't require much experience. In fact most of our helpdesk people are fresh out of college and have no real world work experience. The desktop guys/gals aren't quite as bad, but it's rare to find one on that team here that has been actually working in the I.T. field for more than a year or two.

What the hell!!! I'm a lan manager with a good CURRENT job but looking to relocate to Chicago. In Chicago, with my three years of solid experience I can't even find a helpdesk job!!!

Have you tried any of the recruiters here? There's quite a few IT staffing services in the Chicago-area, I can pass on a few names if you're interested.

Also there could be a possible opening in my company for someone with experience, drop me a PM if you want.

 

[rawoutput]

Originally posted by: shinerburke

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: arod
You guys just hand out IP to any computer on the network? Thats kinda dangerous... We have DHCP but the computers MAC address is assigned an IP and that has to be keyed into the system inorder for it to get an ip from the dhcp server. He may have been asking you to do that but didnt communicate it very well.

We do but we don't. Before a workstation goes in the network port has to be made hot. In the past they had all ports hot all the time but that got them into trouble. Now before a tech takes a workstation out to deploy it he has to give our network team the port number he needs made hot. We suggested tying the IP address to the MAC but upper management here didn't want to do that. I work for a consulting firm that manages the helpdesk, desktop, server, and network engineering groups for this customer and they get the final say in how we do things. We make suggestions, but sometimes they don't want to go with what we suggest. For the most part I don't have to deal with silly stuff since they tend to leave the server team alone to do what we want. Occasionally though they do ignore our suggestions and say something has to be done such and such way. That usually lasts until they get bitten in the ass by the poor decision and then they come around to our way of thinking.

Maybe you should have trained him on how your office handles its computer addressing schemes. It sounds like you just handed him a PC and had him set it up himself. Then you get annoyed when he relies on knowledge from a previous job since you never told him your way of doing things. Maybe you should get some better management skills and stop critisizing your employees.

Maybe you should kiss my ass. He's not my employee. He works on the desktop team, it's not my job to make sure those people know how to do their jobs.

Wow those interpersonal skills are just shining right through. You all work on the same team and when he screws up, guess who he's going to blame? When your boss asks you about it you should tell him to kiss your ass, because you run a server team and your much more capable than a clown like him.

 

[shiner]

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: arod
You guys just hand out IP to any computer on the network? Thats kinda dangerous... We have DHCP but the computers MAC address is assigned an IP and that has to be keyed into the system inorder for it to get an ip from the dhcp server. He may have been asking you to do that but didnt communicate it very well.

We do but we don't. Before a workstation goes in the network port has to be made hot. In the past they had all ports hot all the time but that got them into trouble. Now before a tech takes a workstation out to deploy it he has to give our network team the port number he needs made hot. We suggested tying the IP address to the MAC but upper management here didn't want to do that. I work for a consulting firm that manages the helpdesk, desktop, server, and network engineering groups for this customer and they get the final say in how we do things. We make suggestions, but sometimes they don't want to go with what we suggest. For the most part I don't have to deal with silly stuff since they tend to leave the server team alone to do what we want. Occasionally though they do ignore our suggestions and say something has to be done such and such way. That usually lasts until they get bitten in the ass by the poor decision and then they come around to our way of thinking.

Maybe you should have trained him on how your office handles its computer addressing schemes. It sounds like you just handed him a PC and had him set it up himself. Then you get annoyed when he relies on knowledge from a previous job since you never told him your way of doing things. Maybe you should get some better management skills and stop critisizing your employees.

Maybe you should kiss my ass. He's not my employee. He works on the desktop team, it's not my job to make sure those people know how to do their jobs.

Wow those interpersonal skills are just shining right through. You all work on the same team and when he screws up, guess who he's going to blame? When your boss asks you about it you should tell him to kiss your ass, because you run a server team and your much more capable than a clown like him.

Trust me. If my boss, who is the owner of our company, were to find out about this the desktop guy would lose his job.

 

[shiner]

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

 

[Dracos]

Originally posted by: busmaster11

Originally posted by: shinerburke

Originally posted by: wyvrn
This is a prime example of a paper cert. In addition to those certifications, your company should have required verifiable working experience. Sucks to be you in that case!

That is a problem here. For the desktop and helpdesk positions here they don't require much experience. In fact most of our helpdesk people are fresh out of college and have no real world work experience. The desktop guys/gals aren't quite as bad, but it's rare to find one on that team here that has been actually working in the I.T. field for more than a year or two.

What the hell!!! I'm a lan manager with a good CURRENT job but looking to relocate to Chicago. In Chicago, with my three years of solid experience I can't even find a helpdesk job!!!

Computer Job Market in Chicago is extremely tough right now....and boy do i know it...

 

[gregshin]

i agree with WVRN....you need to just chill and have better management/teamwork skills. I'm the network admin at my company and i also do IT consulting...i know people can be stupid...or they are used to working someway from another company....but i dont let their dumb questions affect me. At least that guy had the balls/initiave to call you and question DHCP...he's not like some mindless robots that i used to work with.

 

[NogginBoink]

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: rawoutput

Originally posted by: shinerburke

Originally posted by: arod
You guys just hand out IP to any computer on the network? Thats kinda dangerous... We have DHCP but the computers MAC address is assigned an IP and that has to be keyed into the system inorder for it to get an ip from the dhcp server. He may have been asking you to do that but didnt communicate it very well.

We do but we don't. Before a workstation goes in the network port has to be made hot. In the past they had all ports hot all the time but that got them into trouble. Now before a tech takes a workstation out to deploy it he has to give our network team the port number he needs made hot. We suggested tying the IP address to the MAC but upper management here didn't want to do that. I work for a consulting firm that manages the helpdesk, desktop, server, and network engineering groups for this customer and they get the final say in how we do things. We make suggestions, but sometimes they don't want to go with what we suggest. For the most part I don't have to deal with silly stuff since they tend to leave the server team alone to do what we want. Occasionally though they do ignore our suggestions and say something has to be done such and such way. That usually lasts until they get bitten in the ass by the poor decision and then they come around to our way of thinking.

Maybe you should have trained him on how your office handles its computer addressing schemes. It sounds like you just handed him a PC and had him set it up himself. Then you get annoyed when he relies on knowledge from a previous job since you never told him your way of doing things. Maybe you should get some better management skills and stop critisizing your employees.

Maybe you should kiss my ass. He's not my employee. He works on the desktop team, it's not my job to make sure those people know how to do their jobs.

Wow those interpersonal skills are just shining right through. You all work on the same team and when he screws up, guess who he's going to blame? When your boss asks you about it you should tell him to kiss your ass, because you run a server team and your much more capable than a clown like him.

To say nothing of the new guy's interpersonal skills. New on the job, telling the veterans of the company that they're wrong. Despite the fact that many, many computers on the network are running fine. Always guaranteed to provide job security. That's it, just tell those guys who hired you that they're wrong! Because that last job, you know, the one that's not paying me money any more (and you are), they had it right!

Had the new guy simply said, "excuse me, I'm afraid I don't understand. Could you explain this to me please?" I'm sure that the end of shinerburke's story would have had a much different ending.

 

[LemonHead]

Originally posted by: gregshin
i agree with WVRN....you need to just chill and have better management/teamwork skills. I'm the network admin at my company and i also do IT consulting...i know people can be stupid...or they are used to working someway from another company....but i dont let their dumb questions affect me. At least that guy had the balls/initiave to call you and question DHCP...he's not like some mindless robots that i used to work with.

While it is good to try to not react the way he did, I must say that understand where shinerburke is coming from. Too may times my company has hired a supposedly competent tech, only to find out that he is only a "paper tech" and has limited understanding of the job he was hired to do. The worst part is that this "paper tech" will defend his stance to the end without simply admitting that he does not understand, and refuses to be educated by the competent techs.

I feel your pain shinerburke! 😉

 

[spanky]

he needs an assigned DHCP address so he can enter it into the TCP/IP settings on the workstation

fire him.

 

[shiner]

Originally posted by: gregshin
i agree with WVRN....you need to just chill and have better management/teamwork skills. I'm the network admin at my company and i also do IT consulting...i know people can be stupid...or they are used to working someway from another company....but i dont let their dumb questions affect me. At least that guy had the balls/initiave to call you and question DHCP...he's not like some mindless robots that i used to work with.

Had he questioned me on the setup or told me he didn't understand I would not have minded working him through the problem. His attitude from the very beginning was "no you are wrong" and he wouldn't listen when I tried to explain things to him nicely. Only after he started in with his arrogant know it all attitude did I get mad at him. I don't have time to deal with idiots who don't know their job. I'm expected to know how to do mine and I expect the same from others. I don't mind helping anyone if they have a question or don't fully understand something, it's when they try to tell me I don't know what I'm talking about or how to do my job that I get angry at them.

 

[abovewood]

Had he questioned me on the setup or told me he didn't understand I would not have minded working him through the problem. His attitude from the very beginning was "no you are wrong" and he wouldn't listen when I tried to explain things to him nicely. Only after he started in with his arrogant know it all attitude did I get mad at him. I don't have time to deal with idiots who don't know their job. I'm expected to know how to do mine and I expect the same from others. I don't mind helping anyone if they have a question or don't fully understand something, it's when they try to tell me I don't know what I'm talking about or how to do my job that I get angry at them.

fire him.

 

[shiner]

Originally posted by: abovewood

Had he questioned me on the setup or told me he didn't understand I would not have minded working him through the problem. His attitude from the very beginning was "no you are wrong" and he wouldn't listen when I tried to explain things to him nicely. Only after he started in with his arrogant know it all attitude did I get mad at him. I don't have time to deal with idiots who don't know their job. I'm expected to know how to do mine and I expect the same from others. I don't mind helping anyone if they have a question or don't fully understand something, it's when they try to tell me I don't know what I'm talking about or how to do my job that I get angry at them.

fire him.

He's not my employee. He is part of the desktop team, not my server team.

 

[Geekbabe]

Originally posted by: shinerburke

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

Are you 100% sure about that,he really might have thought the mac addie needed to be provisioned in order to get an IP from the DHCP server.

 

[MercenaryForHire]

Originally posted by: Geekbabe

Originally posted by: shinerburke

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

Are you 100% sure about that,he really might have thought the mac addie needed to be provisioned in order to get an IP from the DHCP server.

Well, hopefully he would have just called and said "hey, I need an IP in the x subnet assigned for MAC xx:xx:xx:xx:xx:xx"

Unless he's a moron. Ameesh him.

- M4H

 

[shiner]

Originally posted by: Geekbabe

Originally posted by: shinerburke

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

Are you 100% sure about that,he really might have thought the mac addie needed to be provisioned in order to get an IP from the DHCP server.

I'm sure. He wanted an IP address to enter into the TCP/IP settings....he stated that several times. I'm not confident this guy would even know what a MAC is.

 

[ElFenix]

ha ha!

 

[Geekbabe]

Originally posted by: MercenaryForHire

Originally posted by: Geekbabe

Originally posted by: shinerburke

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

Are you 100% sure about that,he really might have thought the mac addie needed to be provisioned in order to get an IP from the DHCP server.

Well, hopefully he would have just called and said "hey, I need an IP in the x subnet assigned for MAC xx:xx:xx:xx:xx:xx"

Unless he's a moron. Ameesh him.

- M4H

Lol, there are IT people that have poor communication skills? hahaha,that's news to me 😉

Nothing is worse than the end users though,absolutely nothing!

 

[shiner]

Originally posted by: Geekbabe

Originally posted by: MercenaryForHire

Originally posted by: Geekbabe

Originally posted by: shinerburke

Originally posted by: FoBoT
maybe he is talking about using reserved addresses, some people/places use the MAC address to reserve specific IP from the DHCP server

or maybe he's an idiot

We use reservations here, mostly for printers on the network and a few boxes that must have an assigned IP, but that's not what he was asking for. He was under the impression that a DHCP address had to be assigned by an administrator before a PC could connect. He couldn't wrap his brain around the idea of a DHCP server or how it works.

Are you 100% sure about that,he really might have thought the mac addie needed to be provisioned in order to get an IP from the DHCP server.

Well, hopefully he would have just called and said "hey, I need an IP in the x subnet assigned for MAC xx:xx:xx:xx:xx:xx"

Unless he's a moron. Ameesh him.

- M4H

Lol, there are IT people that have poor communication skills? hahaha,that's news to me 😉

Nothing is worse than the end users though,absolutely nothing!

Amen sister. I had one call me the other day angry because she couldn't copy her favorite music CD out to her network user directory. I told her that 1. We did not allow music or media files to be saved to the server and used FileScreen to prevent that. and 2. We use Quota Advisor to limit everyone to having 50mb of space on the server. She wouldn't listen and insisted on speaking to the director of I.T. Not long after that I received a call from this woman's manager apologizing for her behavior.

 

[SagaLore]

You'd be amazed how little a lot of network technicians know about DHCP. I spent the first part of my year where I work now arguing with the entire team, including the manager, that they shouldn't be entering all the DNS and WINS addresses into the systems manually, that if they would just fix the configuration on the DHCP server, they wouldn't have the resolution problems they were having. But NOOOOOO, I was the new guy, I was wrong, blah blah blah.

 

[SagaLore]

Originally posted by: arod
You guys just hand out IP to any computer on the network? Thats kinda dangerous... We have DHCP but the computers MAC address is assigned an IP and that has to be keyed into the system inorder for it to get an ip from the dhcp server. He may have been asking you to do that but didnt communicate it very well.

You're talking about security. You guys using RSA?