Pesky NAT type with AX10000

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Pesky NAT type with AX10000

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
41 Reply
Re:Pesky NAT type with AX10000
2022-08-03 14:22:41

  @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.

  0  
  0  
#22
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:23:57

  @pcuttle 

 

This is what I have so far.

 

  0  
  0  
#23
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:25:52 - last edited 2022-08-03 14:27:10

  @Bozac 

 

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

  0  
  0  
#24
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:28:33

  @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.

  0  
  0  
#25
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:30:09

  @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

  0  
  0  
#26
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:31:05

  @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.

  0  
  0  
#27
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:31:47

  @pcuttle 

 

Still showing NAT Type: Moderate....

  0  
  0  
#28
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:33:03

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) wink

  0  
  0  
#29
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:33:44

  @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

  0  
  0  
#30
Options
Re:Pesky NAT type with AX10000
2022-08-03 14:35:22

  @pcuttle 

 

Here is the "Common Service" Battlenet

 

  0  
  0  
#31
Options
Related Articles