Skip to main content
29th November 2020

Xbox Dev Kit at Home

The Problem

Recently I was experiencing an issue when attempting to deploy and run a development game at home on my Xbox Development Kit.

Deploying the packaged build to the kit would work flawlessly, however this was taking ~20 minutes and was really slowing down my productivity. When attempting to then use the ‘Run from PC’ deploy method I would receive this error.

Registering network share 'd:\scratch\{PATH REDACTED}\Image\Loose' with '192.168.1.152'.

Network registration failed: 0x8D160184
0x8D160184 - The specified folder was not found for registration.
             This could be due to DNS issues or an incorrect path.
             Please verify the path is valid and accessible to the console.

After confirming that the path did in fact exist, as well as making sure I could still connect to the console, I approached a colleague and was put in contact with the a developer from games studio who gave some possible solutions.

The Solutions

Solution A

The problem could have been caused by the windows firewall blocking the inbound connection.

If this was the case, the solution would be to first remove any rules that were blocking the inbound network connection of ‘Xbox transfer link service’. Then run the command:

netsh advfirewall firewall add rule name="Xbox Transport Link Service (inbound)" dir=in action=allow protocol=tcp localport=4201

Doing this unfortunately did not solve my issue.

Solution B

If ensuring connections from the development kit weren’t being blocked, then it is likely that the console is having trouble resolving the connection itself.

To solve this I was required to run various commands from the GDK.

  1. Ensure that I am connected to the console that I am having issues with.

    xbconnect 192.168.1.80
  2. Then update add a hosts entry on the console to point my machine to an IP address.

    xbupdatehosts add @auto @auto

    Unfortunately when I ran this I received an error saying that it didn’t understand the parameter @auto. I was able to resolve this problem by supplementing my full computer name that’s on the domain, then followed by the local ip address of the computer. This for example

    xbupdatehosts add my-pc.region.corporate.com 192.168.1.50
  3. Check the hosts entry on the development kit has been updated with the new manual mappings

    xbupdatehosts list

Conclusion

What now makes sense was that my development kit was having trouble talking to my domain joined Windows PC, while both devices were physically off the domain. My setup is a bit strange as work PC funnels all network traffic through a VPN and sometimes inwards connections don’t always work out as expected.