Question / Help Months of Attempts, at wits end

[Jadious]

Looking for any and all helpful suggestions regarding twitch/youtube streaming. I've been trying for months find out what is preventing me from streaming to both platforms. Something's being blocked, somewhere. And I can't for the life of me find the answer.

- I have tried to do this with OBS, Xsplit and Shadowplay all have failed. It's not the programs.

- When I try the Twitch Bandwidth test tool, all fails across the board. Youtube Gaming also fails. It's not the sites.

- I have reset TCP/IP with Winsock. I've forwarded port 1935 on both Win Firewall and Router itself. I've given the broadcasting programs themselves full access. I've completely turned the firewall off. Still nothing.

- I have a 30 down, 10 up connection. Nothing glamorous but well within acceptable range based on everything I've read. Speedtest never fails to show the speeds I'm supposed to be getting.

- I am currently running Windows 10, this problem existed when I had 8 and 8.1. Never tried to stream when I had Win 7. Everything's being run with Admin.

I'm trying to think of anything else I should include in this post, I'll update if I do.

For now, any and all suggestions are welcome, thanks.

 

[FerretBomb]

Post a log file from a streaming attempt, after letting it time out and fail to connect.

Are you able to watch YouTube/Twitch content from your connection?

Press WIN+R, type in 'cmd' and hit enter. In the new box, type 'tracert' (minus the single quotes in both cases) along with the URL for the ingest server you're trying to use (URLs can be found here: http://twitchstatus.com/ under the 'ingest' section). Hit enter.
Right-click and 'mark' the last few lines that aren't asterisks (including the first asterisk-line) and paste them here. This will show us where your connection is dying.


Which ISP are you using? There's a chance that they may be content-filtering, as Twitch streaming is very bandwidth-intensive.
Which antivirus are you using? Unlikely, but possible that some overly-aggressive security suites could be blocking access to Twitch, or from your streaming software for some reason.
What are you using to connect to the internet? (Directly connected to modem, through a 'home router' device, through Internet connection sharing (ICS), through a university/campus network, through a custom Linux NAT device, etc)

Hopefully we'll be able to help get you going. :) First step is to gather information and eliminate possible causes.

 

[Jadious]

I don't have any other connections problems of note, which makes this mystery all the more frustrating. I watch streams and videos without issue.

I uploaded the log file below,

Here is the Tracert data

1 <1 ms <1 ms <1 ms mynetwork.home [**************]
2 23 ms 37 ms 16 ms
3 * 16 ms 16 ms
4 17 ms 29 ms 16 ms
5 32 ms 29 ms 30 ms tcore4-toronto63_2-4-0-1.net.bell.ca []
6 30 ms 30 ms 31 ms tcore4-chicagocp_hundredgige0-5-0-0.net.bell.ca []
7 29 ms 28 ms 29 ms bx9-chicagodt_ae1-0.net.bell.ca []
8 * * * Request timed out.

I am on Bell Fibe in Toronto, Canada. I suppose it's possible they're heavily throttling me but I think I'd have issues with other things crop up if that was the case.

No Antivirus, the occasional malwarebytes scan and clean up. Windows Firewall is all that stands in the way currently.

I am on a desktop directly connected to the modem.

Thanks

 

[FerretBomb]

Hmm. Yes, it seems the ingests don't respond to traceroutes (I could have sworn they did before).

The next step really would be to try a manual handshake through Telnet or similar, though I'm not sure how to do that.

I'm a bit concerned about the 'reset TCPIP with winsock' comment... the last time I used Winsock for anything was under Win95. Was that following a guide somewhere, or what?
Did you run the twitch bandwidth tester as Admin? Try Shaperprobe?

 

[Jadious]

Yeah the Winsock thing was tried in desperation a little while ago, maybe the comment was inaccurately referring to it as winsock. It was simply the command line "netsh int ip reset c:\resetlog.txt"

It didn't work before or after that. But it didn't have any adverse effects on anything else internet related.

I am running the Bandwidth tester with admin, I will have a look at Shaperprobe and get back to you. Is there anything I should be looking out for specifically?

 

[R1CH]

Open a cmd prompt and post output of:

nslookup live.twitch.tv
ping live.twitch.tv
telnet live.twitch.tv 1935

 

[Jadious]

C:\WINDOWS\system32>nslookup live.twitch.tv
Server: mynetwork.home
Address: ****************

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name: live.twitch.tv
Addresses: 199.9.249.197
199.9.251.234
199.9.249.133
199.9.249.118
199.9.249.201
199.9.251.251
199.9.251.170
199.9.249.116
199.9.249.140
199.9.251.252
199.9.249.134
199.9.249.199
199.9.251.166
199.9.251.253
199.9.249.203
199.9.251.177
199.9.251.254
199.9.249.125
199.9.249.135
199.9.249.120
199.9.251.164


C:\WINDOWS\system32>ping live.twitch.tv

Pinging live.twitch.tv [199.9.251.164] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 199.9.251.164:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>telnet live.twitch.tv 1935
'telnet' is not recognized as an internal or external command,
operable program or batch file.

 

[Jadious]

Any updates here, could use any advice or wild theories you have.

 

[R1CH]

Try tcping instead
http://www.elifulkerson.com/projects/tcping.php

tcping live.twitch.tv 1935

 

[Jadious]

Sorry you're gonna have to help me a bit with this one, I run the tcping and the little window pops up for split second, scrolls through a bunch of text then disappears. Is there something else I'm supposed to do besides run it?

Thanks

 

[R1CH]

You use it from a cmd prompt like the other tools. You need to put it in the same folder as the folder your cmd prompt is running from.

 

[Jadious]

I have it in the folder now. cmd prompt doesn't recognize tcping or tcping live.twitch.tv 1935, is there another command I need to type in?

 

[dping]

I have it in the folder now. cmd prompt doesn't recognize tcping or tcping live.twitch.tv 1935, is there another command I need to type in?

open the folder in windows that tcping is in. up in the address bar type "cmd" press enter. this will start cmd in the folder where tcping is.

Also, I edited one of your posts since you really dont want others knowing your IP at home :P

 

[Jadious]

Thanks for that dping.

It worked but I don't think it's gonna provide many clues

Probing 199.9.249.140:1935/tcp - No response - time=2000.217ms
Probing 199.9.249.140:1935/tcp - No response - time=2000.683ms
Probing 199.9.249.140:1935/tcp - No response - time=2001.839ms
Probing 199.9.249.140:1935/tcp - No response - time=2001.821ms

Ping statistics for 199.9.249.140:1935
4 probes sent.
0 successful, 4 failed.
Was unable to connect, cannot provide trip statistics.

 

[dping]

Thanks for that dping.

It worked but I don't think it's gonna provide many clues

Probing 199.9.249.140:1935/tcp - No response - time=2000.217ms
Probing 199.9.249.140:1935/tcp - No response - time=2000.683ms
Probing 199.9.249.140:1935/tcp - No response - time=2001.839ms
Probing 199.9.249.140:1935/tcp - No response - time=2001.821ms

Ping statistics for 199.9.249.140:1935
4 probes sent.
0 successful, 4 failed.
Was unable to connect, cannot provide trip statistics.

ok, you can turn back on windows firewall as that mainly blocks incoming traffic. That port forwarding thing that you set up. remove it, again for incoming traffic.

Infact, bypass your router and just go straight to the modem from your PC. try the same tests again. If you get a success, you might need to reset that router.

 

[R1CH]

If bypassing your router works, something on your router is blocking port 1935. Definitely remove any port forwarding you might have done as some routers incorrectly interpret port forward requests. Maybe even try a factory reset to be sure, and disable any firewall on the router itself (it's unnecessary since you're behind NAT anyway).

 

[Jadious]

My modem and router are the same piece of hardware, an all in one connection hub. My computer is directly wired to it. I will remove the port forwarding on both the router and windows and test again.

 

[dping]

My modem and router are the same piece of hardware, an all in one connection hub. My computer is directly wired to it. I will remove the port forwarding on both the router and windows and test again.

That is what I was afraid of.:/ contact your ISP letting them know you cannot even ping twitch.tv let alone stream to it.

Maybe even replace the router/modem if all else fails.