I got an issue from Bushnet to UTL now. 

from 41.220.7.131 

traceroute mail2.utlonline.co.ug
traceroute to mail2.utlonline.co.ug (81.199.21.120), 30 hops max, 40 byte 
packets
 1  41.220.7.129 (41.220.7.129)  0.605 ms  3.609 ms  0.198 ms
 2  uplink.bushnet.net (217.212.242.2)  2.036 ms  4.739 ms  2.008 ms
 3  217.212.242.38 (217.212.242.38)  621.120 ms  420.365 ms  678.425 ms
 4  * * *
 5  * * *

ergo, my clients can not email UTL at the moment.

From my office (also bushnet) UTL is reachable just fine.

(i really thought i had posted enough today, it just doesnt seem to stop)


On Monday 22 October 2007 09:53:40 [EMAIL PROTECTED] wrote:
> From the mtn side I try to connect/receive mail etc from 
mail.interact-ug.org
> (41.220.6.45) I'm behind MTN's firewall but all traces stop on a former
> bushnet router.
> 
>  
> 
> People,
> 
>  
> 
> Now no access at all where as last night some ping's went through but most
> did not plus thaty latency extremely high.. over 3000ms for local 
connection.
> 
>  
> 
> Can anyone besides Herbert shed some light here?
> 
>  
> 
> Trace from mtn's lan
> 
>  
> 
> C:\Documents and Settings\Rob Gipman>tracert mail.interact-ug.org
> 
>  
> 
> Tracing route to interact-ug.org [41.220.6.45]
> 
> over a maximum of 30 hops:
> 
>  
> 
>   1     2 ms    <1 ms    <1 ms  10.151.28.1
> 
>   2     2 ms    <1 ms    <1 ms  10.151.28.2
> 
>   3    <1 ms    <1 ms    <1 ms  10.151.36.121
> 
>   4    <1 ms    <1 ms    <1 ms  distrouter.mtn.co.ug [212.88.97.49]
> 
>   5    <1 ms    <1 ms    <1 ms  212.88.97.54
> 
>   6     3 ms     2 ms     2 ms  194.153.153.19
> 
>   7    48 ms    25 ms    71 ms  41.220.14.253
> 
>   8    49 ms    49 ms    59 ms  41.220.14.1
> 
>   9     *        *        *     Request timed out.
> 
>  10     *        *
> 
>  
> 
> Trace from 41.220.6.45
> 
>  
> 
> ~ # traceroute 212.88.97.60
> 
> traceroute to 212.88.97.60 (212.88.97.60), 30 hops max, 38 byte packets
> 
>  1  41.220.6.1 (41.220.6.1)  50.474 ms  4.173 ms  4.246 ms
> 
>  2  * * *
> 
>  
> 
> Rob 
> 
> ________________________________
> 
> From: Rob Gipman 
> Sent: Friday, October 19, 2007 10:18 PM
> To: Rob Gipman; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [UIXP Techies] New Infocom Block blocks
> 
>  
> 
> Strange but perhaps it's just a ful pipe i have to go througjh.
> 
>  
> 
> Tracing route to mail.interact-ug.org [41.220.6.45]
> over a maximum of 30 hops:
> 
>   1     2 ms     1 ms     3 ms  192.168.29.1
>   2    18 ms    18 ms    18 ms  212.88.96.9
>   3    20 ms    20 ms    20 ms  212.88.96.1
>   4    20 ms    22 ms    20 ms  212.88.97.54
>   5    44 ms    24 ms    22 ms  194.153.153.19
>   6    67 ms    46 ms    45 ms  41.220.14.253
>   7    66 ms    73 ms   100 ms  41.220.14.1
>   8    71 ms    57 ms    57 ms  uplink.bushnet.net [217.212.242.2]
>   9     *        *        *     Request timed out.
>  10     *        *        *     Request timed out.
>  11     *        *        *     Request timed out.
>  12  ^C
> C:\Documents and Settings\Rob Gipman>ping -t 41.220.6.45
> 
> Pinging 41.220.6.45 with 32 bytes of data:
> 
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 41.220.6.45: bytes=32 time=3516ms TTL=55
> Request timed out.
> Request timed out.
> 
>  
> 
> Anyone tough the weekend is here.
> 
>  
> 
> Rob
> 
>  
> 
> ________________________________
> 
> From: [EMAIL PROTECTED] on behalf of Rob Gipman
> Sent: Fri 10/19/2007 6:51 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [UIXP Techies] New Infocom Block blocks
> 
> THanks Mike, as i figured already. Simlar to Reiners problem seems that was
> simple to fix. Hope this one to but my bet is on the old bushnet router who
> Herbert (Bushnet-now Datanet) is suporting. Will probably have to wait the
> weekend here.
> 
>  
> 
> Rob
> 
>  
> 
> ________________________________
> 
> From: Mike Barnard [mailto:[EMAIL PROTECTED]
> Sent: Fri 10/19/2007 5:40 PM
> To: Rob Gipman
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [UIXP Techies] New Infocom Block blocks
> 
> 
> Hi,
> 
>        
> 
>       Was at the site and tried traces to 2 mtn location, one fidex and one
> wimax and could not get there.
> 
>       tracert 212.88.16.138 <http://212.88.16.138/> 
> 
> 
> For sure this is not an MTN IP address, an a whois 212.88.16.0
> <http://212.88.16.0/>  does not return anything useful.
> 
>       C:\Documents and Settings\Rob Gipman>tracert 212.88.97.90
> <http://212.88.97.90/> 
> 
> 
> Yeap, this is MTN...
> 
>        
> 
>       Tracing route to 212.88.97.90 <http://212.88.97.90/>  over a maximum
> of 30 hops
> 
>       1 <1 ms <1 ms <1 ms 172.16.143.1 <http://172.16.143.1/> 
> 
>       2 5 ms 6 ms 3 ms 41.220.6.1 <http://41.220.6.1/> 
> 
>       3 1618 ms 2497 ms 2806 ms 217.212.242.38 <http://217.212.242.38/> 
> 
>       4 3228 ms 3019 ms 3027 ms 12net-router.bushnet.net
> <http://12net-router.bushnet.net/>  [ 217.212.242.13 
<http://217.212.242.13/>
> ]
> 
>       5 3759 ms 2970 ms 2885 ms 41.220.14.2 <http://41.220.14.2/> 
> 
>       6 1672 ms 2711 ms 2013 ms 41.220.14.254 <http://41.220.14.254/> 
> 
>       7 * * * Request timed out.
> 
>       8 * * * Request timed out.
> 
> 
> something is definately wrong there....within the traceroute's source 
network
> you hit 3000ms and you do not even hit the one2net/bushnet/spacenet IXP
> router, which is 41.220.14.253 <http://41.220.14.253/> .
> 
> 
> Regards,
> 
> 
> -- 
> Mike
> 
> Of course, you might discount this possibility, but remember that one in
> a million chances happen 99% of the time. 
> ------------------------------------------------------------ 
> 
> 



-- 
rgds,

Reinier Battenberg
Director
Mountbatten Ltd.
+256 782 801 749
www.mountbatten.net
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug
%LUG is generously hosted by INFOCOM http://www.infocom.co.ug/

The above comments and data are owned by whoever posted them (including 
attachments if any). The List's Host is not responsible for them in any way.
---------------------------------------

Reply via email to