On this page
- Step 1: Open Windows Defender Firewall
- Step 2: Whitelist Ports 6450
- Step 3: Outbound Rule (Ports)
- Step 4: Whitelist ATAS IP Addresses (Inbound Rule)
- Step 5: Whitelist ATAS IP Addresses (Outbound Rule)
- Step 6: Confirm Rules Are Active
- Pro Tip: Use This PowerShell Script to Automate the Entire Process
- Need Assistance?
Whitelisting ATAS ports and IPs in your Windows VPS firewall can help improve connection stability and reduce interruptions, especially during high-volume trading hours. Follow the steps below to create both inbound and outbound rules using Windows Defender Firewall with Advanced Security.
IPs and ports last verified: July 2026.
Step 1: Open Windows Defender Firewall
On your VPS, search for and open:
Windows Defender Firewall with Advanced Security
- In the left sidebar, you’ll see options for Inbound Rules and Outbound Rules
Step 2: Whitelist Ports 6450
- Go to Inbound Rules
- Click New Rule → choose Port → click Next
Select TCP and enter:
6450- Select Allow the connection → click Next
- Apply to all profiles (Domain, Private, Public)
- Name the rule: ATAS Ports
- Click Finish
Step 3: Outbound Rule (Ports)
Repeat the same steps above under Outbound Rules
→ Name the rule: ATAS Ports (Outbound)
Step 4: Whitelist ATAS IP Addresses (Inbound Rule)
- Still under Inbound Rules, click New Rule
- Select Custom, then click Next
Navigate to the Scope tab
- Under “Remote IP address,” select These IP addresses
Click Add, and input each of the following IPs one by one:
51.178.130.10
142.132.201.231
65.21.32.251
135.181.115.236
- Under Protocol and Ports, leave default (Any) → click Next
- Under Action, select Allow the connection → click Next
- Apply to all profiles → click Next
- Name the rule: ATAS - Inbound IPs
- Click Finish
Here is the matching Outbound Rule section for whitelisting ATAS IPs:
Step 5: Whitelist ATAS IP Addresses (Outbound Rule)
- Go to Outbound Rules, click New Rule
- Select Custom, then click Next
Go to the Scope tab
- Under “Remote IP address,” select These IP addresses
Click Add, and enter each of the following IPs one by one:
51.178.130.10
142.132.201.231
65.21.32.251
135.181.115.236
- Under Protocol and Ports, leave as default (Any) → click Next
- Under Action, choose Allow the connection → click Next
- Apply to all profiles → click Next
- Name the rule: ATAS - Outbound IPs
- Click Finish
Step 6: Confirm Rules Are Active
After adding the rules:
- Open the Firewall rule list under Inbound and Outbound Rules.
- Ensure the new rules are listed and enabled (green checkmarks).
- Restart your platform and test connectivity to confirm improvements.
Pro Tip: Use This PowerShell Script to Automate the Entire Process
# ===============================
# ATAS Firewall Whitelist Script
# ===============================
# Run as Administrator
Write-Host "Creating Windows Firewall rules for ATAS..." -ForegroundColor Cyan
# --- Step 2: Inbound Port 6450 ---
New-NetFirewallRule -DisplayName "ATAS Port (Inbound)" `
-Direction Inbound -Action Allow -Protocol TCP -LocalPort 6450 `
-Profile Domain,Private,Public
# --- Step 3: Outbound Port 6450 ---
New-NetFirewallRule -DisplayName "ATAS Port (Outbound)" `
-Direction Outbound -Action Allow -Protocol TCP -LocalPort 6450 `
-Profile Domain,Private,Public
# --- Step 4 & 5: Whitelist ATAS IP (Inbound & Outbound) ---
$atasIPs = @(
"51.178.130.10",
"142.132.201.231",
"65.21.32.251",
"135.181.115.236"
)
foreach ($ip in $atasIPs) {
# Inbound IP rule
New-NetFirewallRule -DisplayName "ATAS - Inbound IP $ip" `
-Direction Inbound -Action Allow -RemoteAddress $ip `
-Profile Domain,Private,Public -Protocol Any
# Outbound IP rule
New-NetFirewallRule -DisplayName "ATAS - Outbound IP $ip" `
-Direction Outbound -Action Allow -RemoteAddress $ip `
-Profile Domain,Private,Public -Protocol Any
}
Write-Host "ATAS Firewall Rules have been successfully created." -ForegroundColor GreenNeed Assistance?
Our support team is available 24/7. If you have any questions or run into issues, open a support ticket from your QuantVPS dashboard and we'll get back to you as quickly as possible.
Still need help? Our team answers 24/7.
Related articles
3 min read
How to Connect a Rithmic Account to ATAS
UpdatedNinjaTrader13 min read
Common NinjaTrader Errors and How to Fix Them
UpdatedNinjaTrader9 min read
Fix NinjaTrader Slowness with the NinjaScript Utilization Monitor
UpdatedNinjaTrader2 min read
How to Clear the Cache in NinjaTrader 8 (NT8)
Updated
