my.excede.net unavailable onsite, fine from elsewhere.

  • 1
  • Problem
  • Updated 2 years ago
  • In Progress
HI there, new user.
I have found that I can access my.excede.net from my primary residence w/no difficulty. However from the site where I am actually _using_ excede my.excede.net doesn't resolve: no access. Traceroute stops at the sat modem.
At the site in question our connection, otherwise, is fine.
Is this a common issue involving new setups?
note: we do unplug the sat modem when we're off-site.
Photo of caseyd

caseyd

  • 11 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Diana

Diana, Viasat Employee

  • 2241 Posts
  • 424 Reply Likes
Hi caseyd, I'm sorry to hear you are having issues getting into my.exede.net. Did you try to type the address over again.  I typed in myexede.net and was able to access the site.  Please try this and let me know if it worked for you.  Please send an  email to exedelistens@viasat.com with your account and contact information. Thanks, Exede Diana
Photo of caseyd

caseyd

  • 11 Posts
  • 0 Reply Likes
Hi Diana,
 I am able to reach the exede website from anywhere but my exede connection.
 I have tried this for a few consecutive days while working on a project on site.
Thanks.
Photo of Diana

Diana, Viasat Employee

  • 2241 Posts
  • 424 Reply Likes
Hi caseyd,   Thanks for the response. Did you send your account information to exedelistens@viasat.com? Is your account active? What browsers are your using and have you cleared history, cache and cookies?  This often helps. 
Photo of Lake Country Satellite

Lake Country Satellite, Champion

  • 140 Posts
  • 94 Reply Likes
It is my.exede.net.....there is no "c"
Photo of caseyd

caseyd

  • 11 Posts
  • 0 Reply Likes
typo in the subject line.
Photo of caseyd

caseyd

  • 11 Posts
  • 0 Reply Likes
happen to be on site now:

traceroute to google.com (172.217.4.142), 64 hops max, 52 byte packets
 1  192.168.0.11 (192.168.0.11)  2872.043 ms  1.254 ms  1.091 ms
 2  *^C
Santoku:~ casey$ ping google.com
PING google.com (172.217.4.142): 56 data bytes
64 bytes from 172.217.4.142: icmp_seq=0 ttl=53 time=2019.178 ms
64 bytes from 172.217.4.142: icmp_seq=1 ttl=53 time=587.805 ms
64 bytes from 172.217.4.142: icmp_seq=2 ttl=53 time=596.167 ms
ç64 bytes from 172.217.4.142: icmp_seq=3 ttl=53 time=598.123 ms
64 bytes from 172.217.4.142: icmp_seq=4 ttl=53 time=586.275 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 586.275/877.510/2019.178/570.853 ms
Santoku:~ casey$ ping my.exede.net
PING chi.4.0p170000000005vcaq.00d70000000k0rweak.gslb.siteforce.com (136.146.47.185): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6

or, ( and they may not route traceroute info, dunno )

...start
Santoku:~ casey$ traceroute www.exede.net
traceroute to go.exede.net (205.186.137.31), 64 hops max, 52 byte packets
 1  192.168.0.11 (192.168.0.11)  1.527 ms  1.045 ms  0.996 ms
 2  *^C
Santoku:~ casey$ traceroute 8.8.4.4
traceroute to 8.8.4.4 (8.8.4.4), 64 hops max, 52 byte packets
 1  192.168.0.11 (192.168.0.11)  2619.352 ms  1.143 ms  0.893 ms
 2  * * *
 3  * * *
 4  * *^C
Santoku:~ casey$ nslookup my.exede.net
Server:        192.168.0.103
Address:    192.168.0.103#53

Non-authoritative answer:
my.exede.net    canonical name = my.exede.net.00d70000000k0rweak.live.siteforce.com.
my.exede.net.00d70000000k0rweak.live.siteforce.com    canonical name = 4.0p170000000005vcaq.00d70000000k0rweak.gslb.siteforce.com.
4.0p170000000005vcaq.00d70000000k0rweak.gslb.siteforce.com    canonical name = chi.4.0p170000000005vcaq.00d70000000k0rweak.gslb.siteforce.com.
Name:    chi.4.0p170000000005vcaq.00d70000000k0rweak.gslb.siteforce.com
Address: 136.146.47.185

Santoku:~ casey$ traceroute 136.146.47.185
traceroute to 136.146.47.185 (136.146.47.185), 64 hops max, 52 byte packets
 1  192.168.0.11 (192.168.0.11)  1.544 ms  1.006 ms  0.919 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
^C

no ping of my.exede.net,  no traceroute from on site. fine off-site.
Photo of Diana

Diana, Viasat Employee

  • 2241 Posts
  • 424 Reply Likes
Hi caseyd, where are you trying to access my.exede.net? have you typed myexede.net ?  I have typed this and it always bring us the web page.  Let me know if this works for you.