My first instinct is odd DNS issues - possibly intermittent DNS.
If you can not load squeezenetwork.com in your web browser via the domain names then try the IP address directly, which will take DNS out of the picture.
If you can then access Squeezenetwork - you most certainly have DNS issues that need to be resolved before we go much further. If you can't, something else is going on - possibly firewall or browser/computer issues.
Also, remember, not being able to load squeezenetwork.com in your web browser may be an unrelated issue to the SB3 not working. Let's not lump these two problems together quite yet.
1 12 ms 12 ms <1 ms 192.168.254.1
2 16 ms 13 ms 13 ms 192.168.202.1
3 15 ms 3 ms 15 ms 10.81.11.1
What's up with these three sets of private IPs? Are they simply routing or are there two or three layers of NAT involved?
Results 11 to 12 of 12
2008-10-21, 18:30 #11
- Join Date
- Feb 2008
2008-10-21, 19:30 #12
- Join Date
- Sep 2005
126.96.36.199 does not work
an nslookup on www.squeezenetwork.com
yields only 188.8.131.52 (which doesnt work for me via IP or DNS - so the alt address of 184.108.40.206 is never tried using DNS. Can this
address be added to DNS for www.squeezenetwork.com ?
192.168.202.1 is the wan link to me.
10.81.11.1 and beyond is all part of the ISP's
net...no clue as to their intelligence or lack thereof...