@Bozac 

Ok.  I was mistaken.  Particularly with TCP connections, only one device can be forwarded on any given port.  So, see what happens if you omit 3074 on the PC range.

  @pcuttle 

This is what I have so far.

  @Bozac 

Add the UDP 3075-3079 for PC and give it a go.

  @Bozac 

Unfortunately, I have a feeling the 3074 TCP connection is going to trip you up.  That port may be needed to broker all the other connections.

  @pcuttle 

pcuttle wrote

  @Bozac 

 

Add the UDP 3075-3079 for PC and give it a go.

Short of rebooting the router, I did restart the PC and checking to see what I get......stand by

  @Bozac 

Ac couple of options if you cannot get them both working simultaneously.  Try using prot triggering... .I'll look at how that would look, or consuly COD fourms.  I have never had your situation, but port trigeering may be the answer as it is more dynamic.

  @pcuttle 

Still showing NAT Type: Moderate....

pcuttle wrote

  @Bozac 

 

Ac couple of options if you cannot get them both working simultaneously.  Try using prot triggering... .I'll look at how that would look, or consuly COD fourms.  I have never had your situation, but port trigeering may be the answer as it is more dynamic.

 @pcuttle 

Thats what I was feeling too after poking around and see the settings.....just not sure and doing a million things right now (working) 

  @pcuttle 

pcuttle wrote

  @Bozac 

 

Ac couple of options if you cannot get them both working simultaneously.  Try using prot triggering... .I'll look at how that would look, or consuly COD fourms.  I have never had your situation, but port trigeering may be the answer as it is more dynamic.

I just need to figure out the trigger port

  @pcuttle 

Here is the "Common Service" Battlenet