@scottalanmiller here is a good one that I got from Windows, this should be all you need ....You're welcome.

YES I have 1 reputation star!

My company is looking for an experienced Teradata admin. The job is in Portland, OR but relocation assistance may be on the table for the right fit. The company is WebMD Health Services but please don't apply online. Contact me @ dkimberlin <@> outlook.com and i will be able to fast track your resume. Thanks for spreading the word.

Mod: if there is a dedicated spot for job postings please move this to that area.

@MattSpeller I read every post you do in Ron Swanson's voice

it has been a while since I have been on the networking train so I just want to confirm a hunch before I make myself look stupid...here's the sitch

Client computer (on metal working machine) has 2 nics. one it uses to communicate with the innerds of the machine and pass commands back and forth and the other is to connect to the coporate network for file sharing and what-not. each works independently but not together. it seems that when both are plugged in the machine commands get routed to the corporate network thus rending the machine useless. they swear that other MFG machines work fine this way. My conclusion was IP addressing.
Here is the thing,
nic one (machine) is 192.168.0.1 subnet 255.255.255.0
nic two (corp) is 192.168.1.x subnet 255.255.255.0

What I think may be happening is that the MSP that set up nic 2 for the corp network gave it a /24 subnet when in fact the corporate network is /16 and has some default route for 192.168.x.x addresses? am I wrong or is this pretty much the only thing that makes sense?

@scottalanmiller I am stalwart?

@scotth yeah, i'm with you. My thought was to see if they could change the machine IP to 172.whatever to get it the heck out of any kind of possible routing issue.

if you don't know me you should know me.

Wow now I have 7 reputation points. I'm getting rep faster than high school cheerleader

It is me...I have been under a rock or something for a year! How did I not come by for almost a year. I am a terrible friend of the mango lassi. Oh well, I hope you are all a forgiving bunch and will look beyond my truancy. Be well fellow mangosians be well.

My company is looking for an experienced Teradata admin. The job is in Portland, OR but relocation assistance may be on the table for the right fit. The company is WebMD Health Services but please don't apply online. Contact me @ dkimberlin <@> outlook.com and i will be able to fast track your resume. Thanks for spreading the word.

Mod: if there is a dedicated spot for job postings please move this to that area.

working

I believe the syntax in the system.webserver namespace is a bit different and as follows:

<system.webServer>
<security>
<authorization>
<add accessType="Allow" roles="WHATEVER" />
<add accessType="Deny" users="WHATEVER" />
</authorization>
</security>
</system.webServer>

taking a trip down memory lane...

@dashrender Agreed, i doubt it is DHCP and to answer why, i don't know, can't see it. Their MSP is just playing blame game i was trying to posit a solution without having all the data. If those things are each on 255.255.255.0 subnets though, no way they can talk without something routing it.

@thwr thanks for talking through this with me BTW. been a while since i ran in the networking world.

@thwr it would be a longshot, there would be no reason they would have turned it on. I just keep going back to there having to be a route for all 192.168.x.x traffic to go elsewhere. that is the only thing i can think of that would snipe the traffic off that nic.

then we would have a 172.x.x.x and a 192.x.x.x so there is no way they are going to talk, which is what we want

@scotth yeah, i'm with you. My thought was to see if they could change the machine IP to 172.whatever to get it the heck out of any kind of possible routing issue.

The problem is the salesman that got tied up in this doesn't know how to tell the MSP what to do to fix it and they are blaming the $100,000 machine for not working when I don't think it is the machine's fault. I'm in WA and the machine is in IL so I can't run out there and check their network...I offered