> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring development network access

> Domains, ports, CIDR blocks, and firewall exceptions required to develop XBOX GDK titles and connect a dev PC to XBOX Series X|S dev kits on your network.

Work with your network administrators to allow the domains and ports listed below on your organization's network, and open firewall exceptions on the local development PC. You must establish a LAN connection between the dev PC and the target device before you can develop against it.

<Note>
  When migrating from the XDK to the GDK, update any folder-specific restriction or firewall rules to the new install path at `C:\Program Files (x86)\Microsoft GDK`.
</Note>

## Domains for XBOX services

```text theme={null}
https://*.xboxlive.com
https://*.xbox.com
https://*.bing.com
https://*.microsoft.com
https://*.akamai.net
```

## Port for XBOX services

TCP 443.

## Ports for the development PC

2303, 3076, 4016, 11442, 11443, 49152, 49157, 49160.

## Ports for multiplayer and Teredo

* UDP 500 (inbound and outbound).
* UDP 3544 (outbound).
* UDP 4500 (inbound and outbound).

To run tests between devices that aren't on the same network, turn off all inbound-packet filtering.

## Server-to-server XBOX network configuration

If your title makes server-to-server XBOX network (XBOX Live) calls, allow-list these CIDR blocks for all XBOX sandboxes, including `RETAIL`, `CERT`, `*.1`, and `*.99`:

* 134.170.28.0/23
* 191.232.80.128/25
* 191.232.82.128/25
* 191.234.78.0/23
* 131.253.28.0/23
* 134.170.176.0/22
* 157.56.70.0/23
* 65.55.42.0/23
* 131.253.22.0/23
* 191.234.240.0/21

## Ports for GDK on XBOX One family consoles

| Port  | Used by                             |
| ----- | ----------------------------------- |
| 22    | SSH                                 |
| 445   | XBOX Manager, SMB                   |
| 4024  | Visual Studio 2019 Remote Debugger  |
| 4201  | XBOX Manager, PIX, Xtf, XbtpLinkSvc |
| 4211  | XBOX Manager, PIX, Xtf              |
| 4221  | XBOX Manager, PIX, Xtf              |
| 4224  | PIX                                 |
| 4600  | PIX                                 |
| 4601  | PIX                                 |
| 9002  | XBOX Game Streaming                 |
| 9269  | Touch Adaptation Kit Tools          |
| 11442 | XBOX Manager                        |
| 11443 | XBOX Manager, Windows Device Portal |
| 8116  | Visual Studio Integration           |
| 8117  | Visual Studio Integration           |

<Note>
  Open the ports above for both TCP and UDP. Most UI tools only need TCP, but XBOX Game Streaming requires UDP.
</Note>

### Submission Validator tool

* Port: 443.
* Domain: `https://*.xboxlive.com`.

### Wake on LAN for XBOX dev kits

Required by `xbreboot` and parts of XBOX Manager. Wake-on-LAN magic packets go to:

* UDP 7.
* UDP 9.

### IPv6-only networks

Most XBOX services, including sign-in and authentication, currently expose only IPv4 endpoints. Development and testing require IPv4 connectivity, and IPv6 is optional. XBOX doesn't support pure IPv6 networks. Console socket APIs and dev tools support IPv6.


## Related topics

- [Optimizing your game for XBOX Game Streaming](/build/core-features/common/game-streaming/game-streaming-optimizing-your-game.md)
- [XBOX console game development environment and tools](/tools/tools-console/gc-tools-console-toc.md)
- [XBOX environment tools and APIs](/tools/tools-console/gc-xbox-tools-and-apis-toc.md)
- [Recommendations for testing in the RETAIL sandbox](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-recommendations-for-testing-in-retail.md)
- [Network stress tests on XBOX Dev Kits](/build/console-features/networking/tools/netstress-networking.md)