"internetClientServer" and "privateNetworkClientServer" don’t work on Xbox.

Open
#1,435 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
networking

Research direction

Start with the StreamSocket sample and its Xbox deployment and networking configuration. Reproduce the listener on port 22112, then test a connection from another device on the local network while comparing the same sample deployed on a PC. Done means both internetClientServer and privateNetworkClientServer allow the Xbox listener to accept the connection.

Written by the indexing model from the issue text.

Description

bug

Which sample are you reporting a bug in?

Example: StreamSocket

Describe the bug
"internetClientServer" and "privateNetworkClientServer" don’t work on Xbox.

To Reproduce
Steps to reproduce the behavior:

  1. build StreamSocket and install on xbox dev
  2. open all and listen on port 22112 (xbox ip: 192.168.20.5)
  3. telnet to xbox ,telnet 192.168.20.5 22112

Expected behavior
connected to 92.168.20.5:22112
"internetClientServer" and "privateNetworkClientServer" work on Xbox and can connect 22112 from other device on the same local network

Screenshots
1:
Image
2:
Image

Configuration

  • Language/architecture/flavor: c# x64 Debug
  • Windows platform and build number: 10.0.26100.4857 (xb_flt_2506ge.250702-1500)

Additional context
as shown in the screenshot(1,2), listening, connecting, sending, and receiving data are all normal.
but on another PC, it can't connect.

Image

visit Xbox Device Portal is ok

Image

Deployed on a PC and everything works

Dominant language
JavaScript
Stars
9.7k
Forks
7.8k
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/Windows-universal-samples

All issues in microsoft/Windows-universal-samples

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.