Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Thu, Nov 04, 2004 at 08:57:29AM -0800, Antoinette wrote: Please send list mail to the list. > i cannot ping it...here's the output from traceroute > > traceroute 170.223.226.49 > trying to get source for 170.223.226.49 > source should be 170.223.103.96 > traceroute to 170.223.226.49 (170.223.226.49) from > 170.223.103.96 (170.223.103.9 > 6), 30 hops max > outgoing MTU = 1500 > 1 bcores1msfc-g-v403.partners.org (170.223.103.94) 1 ms 0 ms > 0 ms > 2 ccores1msfc-g-V990.partners.org (170.223.2.53) 1 ms 1 ms > 1 ms > 3 acorer3-ccores1msfc-t3-atm-1-0-58.mgh.harvard.edu > (132.183.17.58) 3 ms 3 m > s 3 ms > 4 acores1msfc-vlan2.nsmc.partners.org (170.223.24.73) 6 ms 5 > ms 3 ms > 5 * *^C OK. At this point, I recommend going back to your network engineers and asking for proper settings for default route and netmask. Then ask them if they need to make firewall changes to allow whatever protocol you are using (ssh?) in to this machine. -dsr- -- this is the new strategy for terrorism defense: if there's no freedom left, the terrorists have no freedom to destroy. - Doug Linder
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |