Ill try anything if it will help, what IP addresses and would you be able to briefly explain how to do the nslookup?
@Stertuos said:
Ill try anything if it will help, what IP addresses and would you be able to briefly explain how to do the nslookup?
You already did it above.
nslookup tvdb2.plex.tv 8.8.8.8
just do it several times
you may also exchange the 8.8.8.8 with the IP of the other DNS servers you are using, like 1.1.1.1 etc
Google DNS:
C:\Windows\System32>nslookup tvdb2.plex.tv 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: proxy00.pop.sin.plex.bz
Address: 172.104.187.29
Aliases: tvdb2.plex.tv
proxy.plex.tv
proxy.plex.bz
1dot DNS:
C:\Windows\System32>nslookup tvdb2.plex.tv 1.1.1.1
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1
Non-authoritative answer:
Name: proxy00.pop.sin.plex.bz
Address: 172.104.187.29
Aliases: tvdb2.plex.tv
proxy.plex.tv
proxy.plex.bz
My ISP DNS:
C:\Windows\System32>nslookup tvdb2.plex.tv 192.231.203.132
Server: resolv.internode.on.net
Address: 192.231.203.132
Non-authoritative answer:
Name: proxy03.spop.sjc.plex.bz
Address: 184.105.148.73
Aliases: tvdb2.plex.tv
proxy.plex.tv
proxy.plex.bz
Attempting the nslookup tvdb2.plex.tv 8.8.8.8 again causes the exact same responses each time if you were wondering
I pinged TVDB2.plex.tv on my macbook and it would time out as well, so I believe it must be something to do with my modem, I changed it over recently but I cannot swap it back for certain reasons. Wondering if there is anything that I could look for that might be causing this in the modem.
I restored my modem to factory settings: Nil
This is what I am getting from a tracert:
1 <1 ms <1 ms <1 ms DSL-AC68U-3DB8 [192.168.1.1]
2 18 ms 19 ms 17 ms lo0.bras2.adl4.on.ii.net [150.101.32.162]
3 18 ms 18 ms 19 ms cr2.adl4.on.ii.net [150.101.34.47]
4 29 ms 29 ms 29 ms be18.cr2.adl6.on.ii.net [150.101.40.192]
5 30 ms 29 ms 29 ms be18.cr2.mel10.on.ii.net [150.101.40.185]
6 28 ms 29 ms 28 ms ae19.cr1.mel8.on.ii.net [150.101.40.134]
7 29 ms 29 ms 29 ms 218.100.78.51
8 40 ms 39 ms 39 ms ae16-0.syd-96cbe-1b.ntwk.msn.net [198.206.164.97]
9 39 ms 39 ms 40 ms ae9-0.syd-96cbe-1a.ntwk.msn.net [198.206.164.198]
10 140 ms 141 ms 141 ms ae16-0.gum01-96cbe-1a.ntwk.msn.net [104.44.225.188]
11 141 ms 141 ms 141 ms ae0-0.gum01-96cbe-1b.ntwk.msn.net [104.44.226.43]
12 172 ms 170 ms 180 ms ae3-0.hkg-96cbe-1a.ntwk.msn.net [104.44.226.177]
13 172 ms 171 ms 170 ms ae1-0.hkb-96cbe-1a.ntwk.msn.net [104.44.226.56]
14 171 ms 171 ms 173 ms ae19-0.hkb-96cbe-1b.ntwk.msn.net [104.44.224.147]
15 195 ms 195 ms 197 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255]
16 195 ms 196 ms 209 ms ae39-0.icr02.sg3.ntwk.msn.net [104.44.236.155]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
If you find the time, please open a powershell prompt and type this in: curl https://tvdb2.plex.tv
Which type of error message do you get?
It should be “Not authorized” if everything is working as it should.
It seems it is not working as it should
curl : Unable to connect to the remote server
At line:1 char:1
- curl https://tvdb2.plex.tv
-
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc eption + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
I tried to ping the server through my phone on the 4G network and would get:
request timeout for icmp_seq 0
request timeout for icmp_seq 1
request timeout for icmp_seq 2
request timeout for icmp_seq 3 (repeating)
could the server be down? I just find it odd that I have been having troubles with matching tv shows for at least 2 months now.
Is your 4G connection through the same ISP or one of its partners?
I’d log a customer complaint with them and ask them to investigate their routing.
Two completely separate ISPs unfortunately
Particularly in rural areas, some 4G providers use the infrastructure of other data providers in the area. So it could very well be the case that both your connections go over the same networks.
Im quite close to the city and my phone and wired connection are through competing ISP’s
Technicians tested the server in Singapore and found it working as expected.
I was told that ping is not a conclusive test, because often those packets are filtered out.
It would be better to first look up the IP with dig or nslookup
and later try to curl https:\ vdb2.plex.tv
or use telnet to connect on port 443
If you have a telnet simulation or curl for your phone, your results may be different.
Nonetheless, your main internet connection appears to have a routing issue.
nslookup:
C:\Users\Jamie>nslookup tvdb2.plex.tv
Server: 1dot1dot1dot1.cloudflare-dns.com
Address: 1.1.1.1
Non-authoritative answer:
Name: proxy00.pop.sin.plex.bz
Address: 172.104.187.29
Aliases: tvdb2.plex.tv
proxy.plex.tv
proxy.plex.bz
C:\Users\Jamie>ping 172.104.187.29
Pinging 172.104.187.29 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 172.104.187.29:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
How would I go about restoring the routing issue?
@Stertuos said:
Pinging 172.104.187.29 with 32 bytes of data:
As I wrote above, ping is not conclusive. Try curl in powershell or use putty to try and open a telnet session.
How would I go about restoring the routing issue?
If the above tests also fail, only your ISP can solve that.
But double-check that your router doesn’t play a role in this issue.
Sometimes an over-zelous firewall or other filter has unforeseen consequences.
curl gives the same results:
PS C:\Windows\System32\WindowsPowerShell\v1.0> curl https:\ vdb2.plex.tv
curl : Unable to connect to the remote server
At line:1 char:1
- curl https:\ vdb2.plex.tv
-
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc eption + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Is it possible to access tvdb.com rather than through tvdb2.plex.tv to get metadata?
@Stertuos said:
Is it possible to access tvdb.com rather than through tvdb2.plex.tv to get metadata?
No. This is not possible.
I have scoured every inch of my modem (DSL AC68U) and have found nothing that seems out of place
New update, i am under the impression that my ISP has blocked certain media agents, particularly tvdb which is causing the issue. I have a vpn but have not been able get it to bypass the blocks, are there any suggestions which would be the best settings to bypass the blocks?
