Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Host: Windows 7 Pro
Client: Ubuntu 16.04 LTS
no streaming, can't unpair devices, interface on Ubuntu broken (buttons below paired devices list almost invisible)
will provide more details if valve asks
I am running Windows 10 Pro 1809 on both server and client. When streaming any game, screen goes black with cursor showing for about 10 seconds, then "Couldn't connect to the remote computer".
For me, this doesn't work after a couple of attempts, I get this behavior every time.
My streaming_client.exe.log shows that Steam tries to connect to 0.0.0.0:0
Sat Jun 15 06:56:40 2019 UTC - Initializing player
Sat Jun 15 06:56:40 2019 UTC - Refresh rate: 60.01
Sat Jun 15 06:56:40 2019 UTC - Effective rate: 59.76
Sat Jun 15 06:56:40 2019 UTC - Video size: 2736x1824, output size: 2736x1824
Sat Jun 15 06:56:40 2019 UTC - Video rect: 2736x1824 at 0,0
Sat Jun 15 06:56:40 2019 UTC - Texture rect: 2736x1824 at 0,0
Sat Jun 15 06:56:40 2019 UTC - Initialized player
Sat Jun 15 06:56:40 2019 UTC - Connecting to server at address: 0.0.0.0:0
Sat Jun 15 06:56:40 2019 UTC - Session state Idle -> Connecting
Sat Jun 15 06:56:40 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049): The requested address is not valid in its context.
Sat Jun 15 06:56:40 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049): The requested address is not valid in its context.
Sat Jun 15 06:56:40 2019 UTC - CStreamTransportClient stopping Remote Client service connection
Sat Jun 15 06:56:40 2019 UTC - Video size: 2736x1824, output size: 2736x1824
Sat Jun 15 06:56:40 2019 UTC - Video rect: 2736x1824 at 0,0
Sat Jun 15 06:56:40 2019 UTC - Texture rect: 2736x1824 at 0,0
Sat Jun 15 06:56:40 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049): The requested address is not valid in its context.
The last entry is repeated multiple times.
I have the same errors as above:
Sat Jun 15 08:17:43 2019 UTC - Initialized player
Sat Jun 15 08:17:43 2019 UTC - Connecting to server at address: 0.0.0.0:0
Sat Jun 15 08:17:43 2019 UTC - Session state Idle -> Connecting
Sat Jun 15 08:17:43 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049):
Sat Jun 15 08:17:43 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049):
Sat Jun 15 08:17:43 2019 UTC - CStreamTransportClient stopping Remote Client service connection
Sat Jun 15 08:17:43 2019 UTC - Video size: 1920x1080, output size: 1920x1080
Sat Jun 15 08:17:43 2019 UTC - Video rect: 1920x1080 at 0,0
Sat Jun 15 08:17:43 2019 UTC - Texture rect: 1920x1080 at 0,0
Sat Jun 15 08:17:43 2019 UTC - Send to 0.0.0.0:0 with size 17 failed (10049)
Last line repeats.
relevant section from: steaming_log.txt
[2019-06-15 07:24:04] Streaming started to MintCenter at 192.168.1.60:60308, audio channels = 2, MTU = 1468
[2019-06-15 07:24:04] Streaming quality: k_EStreamQualityBeautiful
[2019-06-15 07:24:04] Streaming bitrate: Automatic
[2019-06-15 07:24:04] Maximum capture: 1920x1080 59.75 FPS
[2019-06-15 07:24:04] Video Streaming: enabled
[2019-06-15 07:24:04] Audio Streaming: enabled
[2019-06-15 07:24:04] Input Streaming: enabled
[2019-06-15 07:24:04] =====================================================================
[2019-06-15 07:24:04] Game: UNKNOWN (0)
[2019-06-15 07:24:04] Setting target bitrate to 15000 Kbit/s, burst bitrate is 75000 Kbit/s
[2019-06-15 07:24:04] Recording system audio
[2019-06-15 07:24:04] Recording on device: TSB-TV (2- NVIDIA High Definition Audio)
[2019-06-15 07:24:04] Audio client mix format:
[2019-06-15 07:24:04] format: 65534
[2019-06-15 07:24:04] channels: 2
[2019-06-15 07:24:04] samples/sec: 48000
[2019-06-15 07:24:04] bytes/sec: 384000
[2019-06-15 07:24:04] alignment: 8
[2019-06-15 07:24:04] bits/sample: 32
[2019-06-15 07:24:04] channel mask: 0x3
[2019-06-15 07:24:04] data format: {00000003-0000-0010-8000-00AA00389B71}
[2019-06-15 07:24:04] Initializing audio with 2 channels and 48000 samples/sec
[2019-06-15 07:24:04] Streamed game has created a window
[2019-06-15 07:24:04] Bringing streamed game to foreground - success
[2019-06-15 07:24:04] Reinitializing recording system audio
[2019-06-15 07:24:04] Recording on device: Speakers (Steam Streaming Speakers)
[2019-06-15 07:24:04] Audio client mix format:
[2019-06-15 07:24:04] format: 65534
[2019-06-15 07:24:04] channels: 2
[2019-06-15 07:24:04] samples/sec: 48000
[2019-06-15 07:24:04] bytes/sec: 384000
[2019-06-15 07:24:04] alignment: 8
[2019-06-15 07:24:04] bits/sample: 32
[2019-06-15 07:24:04] channel mask: 0x3
[2019-06-15 07:24:04] data format: {00000003-0000-0010-8000-00AA00389B71}
[2019-06-15 07:24:04] Initializing audio with 2 channels and 48000 samples/sec
[2019-06-15 07:24:04] Changing record window: 00020416
[2019-06-15 07:24:04] >>> Switching video stream from NONE to Desktop_MovieStream
[2019-06-15 07:24:04] CDesktopCaptureDWM: Reinitializing D3D for adapter 0xa462
[2019-06-15 07:24:04] Video adapter: NVIDIA GeForce GTX 970, vendor ID: 0x10de, device ID: 0x13c2
As it is inside the "bug" section of the "in-home streaming" group, I am hoping Valve is paying more attention to that.
Use
(PS: You might find @StreamClientArgs --framerate 30 --bitrate 4000 useful, I use those all the time on underpowered machine and slow network.)
I mean, I came here with the same problem, but switched the streaming client (inux) to the beta, and it has worked fine since then (note I just updated yesterday and still am testing it, but it did connect perfectly fine twice in a row after putting both computers to sleep, which wasn't happening before the update to beta)
This isn't the case anymore.