Everything, Everything

2024: January February March April
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Broadband
Wednesday 2nd August, 2006 10:35 Comments: 3
I can\'t seem to connect to my fileserver via Remote Desktop. This usually means my fileserver is dead or the router is dead (or dropped the connection) or my ISP has gone down again. All are probably equally likely, but I suspect (and hope) it's the router. I tried scanning it with nmap, and all I can get back is "filtered" even on the ports that were being portforwarded to the fileserver that I think should come back as closed if the server is dead. I hope I just need to reset the router to sort it out.
Avatar Robert - Wednesday 2nd August, 2006 11:12
It looks like there's a network issue somewhere along the way, a traceroute seems to end up going around in a loop at 217.144.159.22, I think. Something funny is definitely happening after 83.142.50.254.
Avatar Robert - Wednesday 2nd August, 2006 11:16
And it looks like 217.144.159.22 is the entry point to FMN's network, according to Cain.
Avatar Robert - Wednesday 2nd August, 2006 18:13
Got home, reset my router, all is well :)
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3