[UCIMC-Tech] problems reaching google.com from Bike Project

Mike Lehman rebelmike at earthlink.net
Mon Jul 7 23:21:21 CDT 2008


During the Prairiegreens meeting this evening in the Family Room, a tech-savvy member reported he was unable to access google.com, although I didn't ask anything more about his trouble. I did note that he was using a Dell via wireless, on which I think he was running a Linux OS.
Mike Lehman

-----Original Message-----
>From: Barry Isralewitz <barryi at ks.uiuc.edu>
>Sent: Jul 7, 2008 7:11 PM
>To: Stuart Levy <slevy at ncsa.uiuc.edu>, imc-tech at lists.ucimc.org
>Subject: [UCIMC-Tech] problems reaching google.com from Bike Project
>
>Hello,
>
>
>  Any word yet on a possible fix to the below?  Recap: the Bike Project
>computer (running BSD) can  get to any web site or service, except for those
>served from 
>   google.com.  
>I suspect some strangeness in the building network.
>For the doubtful, feel free to to plug your laptop into a spare RJ-45 on the
>shop switch and check yourself.
>  
>   I was worried that a misset time-of-day on the Bike Project BSD mchine was
>part of the problem  -- but I fixed this, and this odd problem still persists.
>(That is, since I sent below mail, time-of-day has been correct -- NTP had not been
>running at all on the BSD machine.  I fixed this; now NTP gets time from UIUC's
>stratum 2 servers).
>
>    Barry
>
>
>----- Forwarded message from Barry Isralewitz <barryi at ks.uiuc.edu> -----
>
>Date: Thu, 26 Jun 2008 22:19:49 -0500
>From: Barry Isralewitz <barryi at ks.uiuc.edu>
>To: Stuart Levy <slevy at ncsa.uiuc.edu>
>Cc: imc-tech at lists.ucimc.org
>Subject: Re: [UCIMC-Tech] Re: Gmail problems
>In-Reply-To: <20080506193748.GA21418 at osage.ncsa.uiuc.edu>
>
>Hi Stuart,
>
>
>  Interspersed with quoting your email, some results below of running netstat and traceroute and more on the Bike Project computer.
>
>On Tue, May 06, 2008 at 02:37:48PM -0500, Stuart Levy wrote:
>> On Tue, May 06, 2008 at 02:10:48PM -0500, Barry Isralewitz wrote:
>> > Hi,
>> > 
>> > On Tue, May 06, 2008 at 01:41:37PM -0500, Bob Illyes wrote:
>> > > Joy uses gmail without problem, but gmail doesn't work from the Print Mac, 
>> > > which has an old OS and browser for arcane reasons. Gmail seems to be picky 
>> > > about browsers, and the issue in the Bike Projet may be an old browser 
>> > > rather than the UCIMC web service. Print doesn't have any problem with 
>> > > Google itself, though, last time I checked.
>> >  
>> >  Thanks for the info.
>> > 
>> >  To clarify problem I see in Bike Project computer: the trouble seems to be
>> > with establishing any communication at all with with google.com and/or
>> > gmail.com; so this seems more of a routing/adressing issue than a browser-
>> > compaitiblity issue.  (To be positive, I'll try pings from/to different places
>> > when I'm next in the shop.) The Firefox browser version on Bike Project's BSD
>> > computer is modern enough; it renders gmail and google pages quickly and
>> > accurately during some periods (i.e.  when communication apparently going
>> > well.) Also, the http://google.com default page is very simple, about any
>> > browser around can render it at least somewhat well.
>> > 
>> >  Hmm... I'm recalling now I had the same problem last week -- periods when
>> > could not contact google.com but could contact all other distant websites -- on
>> > my laptop when connected to OpenIMC in the room 24. (Have latest, stable
>> > browser versions on my laptop.)
>> > 
>> >  Demonstrate problem with Firefox:
>> >      a) enter 'google.com' into address bar, get animated 'busy' icon 
>> >      b) while a) continues, open a new tab.  enter yahoo.com.  page is quickly displayed.
>> >      c) close tab from a) (it is still 'busy'.
>> >      d) open new tab.  try google.com again.  Another 'busy' icon
>> >      e) enter "newyorktimes.com". Page is quickly displayed.  The google pages continue to display 'busy' icons. In some cases, the google pges will appear a few minutes later, sometimes not. 
>> 
>> It'd be interesting to open a terminal window (xterm or whatever)
>> while this is going on, and type
>> 
>>     netstat -tf inet
>> 
>> and note the output. 
>
>
>  Here I have one Firefox tab Firefox open, with a google attempt a couple of minutes, and another tab with a google contact in the process of failing.
>
>bash2-2.05b$     netstat -tf inet
>Active Internet connections
>Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
>tcp4       0    392  192.168.42.106.53676   od-in-f83.google.http  ESTABLISHED
>tcp4       0      0  192.168.42.106.61635   209.62.185.9.http      ESTABLISHED
>tcp4       0      0  192.168.42.106.59502   204.2.228.81.http      ESTABLISHED
>tcp4       0      0  192.168.42.106.56346   128.242.191.49.http    ESTABLISHED
>tcp4       0      0  192.168.42.106.49924   winnipeg.ks.uiuc.ssh   ESTABLISHED
>tcp4       0      0  192.168.42.106.49986   winnipeg.ks.uiuc.ssh   ESTABLISHED
>
>
>
>  Pretty much sites but google.com, gmail.com, and other Google sites go through.  Some non-google sites have Google-dependent parts, these load partially, then freeze up displaying messages about loading these -- say www.google-analytics.com or googlesyndication.com addresses.
>
> There'll be a line for every active TCP connection.
>> Do you see a line like
>> 
>> 
>>     tcp4       0    224  192.168.11.11.55390    <something>.google.com.http      SYN_SENT
>> 
>> ?  The "SYN_SENT" would be the important thing -- it'd mean that 
>> packets were being sent to google but no acknowledgement was reaching you.
>> This would be a way of showing that it's a network-level problem,
>> not e.g. a name resolution problem.
>> 
>> It would also be interesting to "traceroute" to google.com at a troublesome time,
>> and see how far it gets.
>
> Here are some traceroutes and pings I ran last week on  the Bike Project computer with a few notes interspersed.  Note that the traceroutes to google are clearly diffrent different from traceroutes to uiuc.edu and yahoo.com.  
>====
>2008-Jun-19  09:21:46 AM (CDT)
>--
>whasmyip.org says we are 75.145.177.73
>Note: clock is misset....
>bash2-2.05b$ date -u
>Thu Jun 19 21:22:45 UTC 2008
>   note:At 10:24 AM June 19 chicago time
>--
>bash2-2.05b$  uname -a
>FreeBSD  6.0-RELEASE FreeBSD 6.0-RELEASE #0: Tue Jan 10 23:42:31 CST 2006     kaduk@:/usr/obj/usr/src/sys/PROLIX  i386
>
>---
>--
>
>bash2-2.05b$ date;traceroute www.uiuc.edu;date
>Thu Jun 19 15:19:21 CDT 2008
>traceroute to swan29.admin.uiuc.edu (128.174.254.29), 64 hops max, 40 byte packets
> 1  192.168.42.1 (192.168.42.1)  1.888 ms  0.901 ms  0.829 ms
> 2  * * *
> 3  ge-1-2-ur01.champaign.il.chicago.comcast.net (68.85.178.65)  9.347 ms  9.595 ms  12.543 ms
> 4  pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.170)  21.972 ms  16.036 ms  15.775 ms
> 5  pos-0-1-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.169)  25.179 ms  31.886 ms  27.784 ms
> 6  pos-0-12-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.21)  40.192 ms  40.884 ms  47.968 ms
> 7  68.86.85.137 (68.86.85.137)  76.245 ms  77.168 ms  76.228 ms
> 8  te-1-1-pr01.600wseventh.ca.ibone.comcast.net (68.86.84.130)  76.682 ms  74.434 ms  76.721 ms
> 9  68.86.89.158 (68.86.89.158)  234.557 ms  184.015 ms  230.299 ms
>10  vl3492.mpd01.lax01.atlas.cogentco.com (154.54.3.9)  98.143 ms
>    vl3493.mpd01.lax01.atlas.cogentco.com (154.54.6.229)  74.178 ms
>    vl3492.mpd01.lax01.atlas.cogentco.com (154.54.3.9)  73.726 ms
>11  te3-1.mpd01.sjc01.atlas.cogentco.com (154.54.5.181)  84.512 ms  89.169 ms  111.431 ms
>12  te3-3.mpd01.sfo01.atlas.cogentco.com (154.54.6.133)  88.699 ms  87.053 ms  85.278 ms
>13  te4-1.mpd01.mci01.atlas.cogentco.com (154.54.6.33)  120.869 ms  172.868 ms  122.139 ms
>14  *
>    te4-3.mpd01.ord01.atlas.cogentco.com (66.28.4.186)  288.273 ms *
>15  vl3605.na31.b002329-4.ord01.atlas.cogentco.com (38.20.36.178)  118.772 ms  119.233 ms  124.766 ms
>16  university-of-illinios-urbana.demarc.cogentco.com (38.104.99.42)  79.229 ms  77.604 ms  80.115 ms
>17  t-ur2rtr.ix.ui-iccn.org (72.36.126.101)  82.734 ms  84.086 ms  82.708 ms
>18  iccn-ur2rtr-uiuc2.gw.uiuc.edu (72.36.127.6)  80.092 ms  80.648 ms  83.994 ms
>19  t-exiteb.gw.uiuc.edu (130.126.0.73)  91.742 ms  82.852 ms  80.989 ms
>20  * * *
>21  * * *
>22  * * *
>23  * * *
>24  * * *
>25  * * *
>26  * * *
>27  * * *
>28  * * *
>29  * * *
>30  * * *
>31  * * *
>32  * * *
>33  * * *
>34  * * *
>35  * * *
>36  * * *
>37  * * *
>38  * * *
>39  * * *
>40  * * *
>41  * * *
>42  * * *
>43  * * *
>44  * * *
>45  * * *
>46  * * *
>47  * * *
>48  * * *
>49  * * *
>50  *  * *
>51  * * *
>52  *  
>Thu Jun 19 15:28:17 CDT 2008
>time = 9:30 am
>
>
>=======================
>
>
>
>sh2-2.05b$ date;traceroute yahoo.com;date
>Thu Jun 19 15:29:23 CDT 2008
>traceroute: Warning: yahoo.com has multiple addresses; using 68.180.206.184
>traceroute to yahoo.com (68.180.206.184), 64 hops max, 40 byte packets
> 1  192.168.42.1 (192.168.42.1)  1.139 ms  0.918 ms  0.816 ms
> 2  * * *
> 3  ge-1-2-ur01.champaign.il.chicago.comcast.net (68.85.178.65)  8.969 ms  9.102 ms  9.296 ms
> 4  pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.170)  21.770 ms  18.800 ms  17.057 ms
> 5  pos-0-1-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.169)  25.159 ms  26.459 ms  25.407 ms
> 6  pos-0-5-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.66)  32.740 ms  40.511 ms  33.817 ms
> 7  *
>    te-4-4.car1.Atlanta2.Level3.net (4.71.252.13)  42.774 ms  41.573 ms
> 8  ae-71-52.ebr1.Atlanta2.Level3.net (4.68.103.60)  43.645 ms  43.071 ms  35.926 ms
> 9  ae-73-70.ebr3.Atlanta2.Level3.net (4.69.138.20)  38.925 ms  46.805 ms  54.537 ms
>10  ae-7.ebr3.Dallas1.Level3.net (4.69.134.21)  47.758 ms  50.175 ms  53.953 ms
>11  ae-3.ebr2.LosAngeles1.Level3.net (4.69.132.77)  90.452 ms  78.928 ms  84.395 ms
>12  ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22)  87.406 ms *  88.364 ms
>13  ae-63-63.ebr3.LosAngeles1.Level3.net (4.69.137.33)  78.810 ms  86.329 ms  91.813 ms
>14  ae-2.ebr3.SanJose1.Level3.net (4.69.132.9)  84.292 ms  88.344 ms  90.424 ms
>15  ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230)  84.842 ms
>    ae-93-93.csw4.SanJose1.Level3.net (4.69.134.238)  88.823 ms
>    ae-83-83.csw3.SanJose1.Level3.net (4.69.134.234)  83.674 ms
>16  ae-23-79.car3.SanJose1.Level3.net (4.68.18.69)  86.193 ms
>    ae-43-99.car3.SanJose1.Level3.net (4.68.18.197)  98.863 ms
>    ae-23-79.car3.SanJose1.Level3.net (4.68.18.69)  214.310 ms
>17  4.71.112.14 (4.71.112.14)  90.279 ms  90.228 ms  89.510 ms
>18  ae1-p161.msr1.sp1.yahoo.com (216.115.107.63)  90.759 ms
>    ae1-p171.msr2.sp1.yahoo.com (216.115.107.87)  90.610 ms
>    ae0-p171.msr2.sp1.yahoo.com (216.115.107.83)  88.891 ms
>19  te-8-1.bas-a2.sp1.yahoo.com (209.131.32.19)  90.982 ms
>    te-9-1.bas-a1.sp1.yahoo.com (209.131.32.21)  90.635 ms
>    te-8-1.bas-a1.sp1.yahoo.com (209.131.32.17)  90.110 ms
>20  * * *
>21  * * *
>22  * * *
>23  * * *
>24  * * *
>25  * * *
>26  * * *
>27  * * *
>28  * * *
>29  * * *
>30  * * *
>31  * * *
>32  * * *
>33  * * *
>34  * * *
>35  * * *
>36  * * *
>37  * * *
>38  * * *
>39  * * *
>40  * * *
>41  * * *
>42  * * *
>43  * * *
>44  * * *
>45  * * *
>46  * * *
>47  * * *
>48  * * *
>49  * * *
>50  * * *
>51  * * *
>52  * * *
>53  * * *
>54  * * *
>55  * * *
>56  * * *
>57  * * *
>58  * * *
>59  * * *
>60  * * *
>61  * * *
>62  * * *
>63  * * *
>64  * * *
>Thu Jun 19 15:41:08 CDT 2008
>
>
>=======
>
>
>
>
>ash2-2.05b$ date;traceroute google.com;date
>Thu Jun 19 16:36:09 CDT 2008
>traceroute: Warning: google.com has multiple addresses; using 64.233.167.99
>traceroute to google.com (64.233.167.99), 64 hops max, 40 byte packets
> 1  192.168.42.1 (192.168.42.1)  3.941 ms  6.835 ms  3.111 ms
> 2  * * *
> 3  ge-1-2-ur01.champaign.il.chicago.comcast.net (68.85.178.65)  8.422 ms  7.143 ms  9.784 ms
> 4  pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.170)  20.564 ms  17.295 ms  16.990 ms
> 5  pos-0-1-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.169)  27.575 ms  26.328 ms  31.989 ms
> 6  pos-0-5-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.66)  32.472 ms  34.752 ms  33.793 ms
> 7  te-4-3.car1.Atlanta2.Level3.net (4.71.252.25)  37.362 ms  33.989 ms  34.209 ms
> 8  ae-63-51.ebr3.Atlanta2.Level3.net (4.68.103.30)  32.028 ms  33.186 ms  34.873 ms
> 9  ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19)  39.361 ms
>    ae-62-60.ebr2.Atlanta2.Level3.net (4.69.138.3)  35.932 ms
>    ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19)  47.590 ms
>10  ae-3.ebr2.Chicago1.Level3.net (4.69.132.73)  37.396 ms  49.094 ms  36.569 ms
>11  ae-21-56.car1.Chicago1.Level3.net (4.68.101.162)  38.945 ms
>    ae-21-52.car1.Chicago1.Level3.net (4.68.101.34)  40.676 ms  38.025 ms
>12  *
>    GOOGLE-INC.car1.Chicago1.Level3.net (4.79.208.18)  45.265 ms  45.227 ms
>13  72.14.232.53 (72.14.232.53)  38.219 ms
>    66.249.94.133 (66.249.94.133)  38.033 ms  40.504 ms
>14  72.14.232.74 (72.14.232.74)  45.250 ms
>    64.233.175.42 (64.233.175.42)  39.700 ms
>    72.14.232.74 (72.14.232.74)  44.323 ms
>15  py-in-f99.google.com (64.233.167.99)  42.799 ms  40.262 ms  40.371 ms
>Thu Jun 19 16:36:31 CDT 2008
>
>
>
>-----
>
>Second try to Google
>
>
>bash2-2.05b$ date;traceroute google.com;date
>Thu Jun 19 16:36:09 CDT 2008
>traceroute: Warning: google.com has multiple addresses; using 64.233.167.99
>traceroute to google.com (64.233.167.99), 64 hops max, 40 byte packets
> 1  192.168.42.1 (192.168.42.1)  3.941 ms  6.835 ms  3.111 ms
> 2  * * *
> 3  ge-1-2-ur01.champaign.il.chicago.comcast.net (68.85.178.65)  8.422 ms  7.143 ms  9.784 ms
> 4  pos-0-11-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.170)  20.564 ms  17.295 ms  16.990 ms
> 5  pos-0-1-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.169)  27.575 ms  26.328 ms  31.989 ms
> 6  pos-0-5-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.66)  32.472 ms  34.752 ms  33.793 ms
> 7  te-4-3.car1.Atlanta2.Level3.net (4.71.252.25)  37.362 ms  33.989 ms  34.209 ms
> 8  ae-63-51.ebr3.Atlanta2.Level3.net (4.68.103.30)  32.028 ms  33.186 ms  34.873 ms
> 9  ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19)  39.361 ms
>    ae-62-60.ebr2.Atlanta2.Level3.net (4.69.138.3)  35.932 ms
>    ae-72-70.ebr2.Atlanta2.Level3.net (4.69.138.19)  47.590 ms
>10  ae-3.ebr2.Chicago1.Level3.net (4.69.132.73)  37.396 ms  49.094 ms  36.569 ms
>11  ae-21-56.car1.Chicago1.Level3.net (4.68.101.162)  38.945 ms
>    ae-21-52.car1.Chicago1.Level3.net (4.68.101.34)  40.676 ms  38.025 ms
>12  *
>    GOOGLE-INC.car1.Chicago1.Level3.net (4.79.208.18)  45.265 ms  45.227 ms
>13  72.14.232.53 (72.14.232.53)  38.219 ms
>    66.249.94.133 (66.249.94.133)  38.033 ms  40.504 ms
>14  72.14.232.74 (72.14.232.74)  45.250 ms
>    64.233.175.42 (64.233.175.42)  39.700 ms
>    72.14.232.74 (72.14.232.74)  44.323 ms
>15  py-in-f99.google.com (64.233.167.99)  42.799 ms  40.262 ms  40.371 ms
>Thu Jun 19 16:36:31 CDT 2008
>
>------
>Pings 
>(stopped UIUC ones quickly, am in hurry)
>
>
>bash2-2.05b$ uname
>FreeBSD
>bash2-2.05b$  ping google.com
>PING google.com (72.14.207.99): 56 data bytes
>64 bytes from 72.14.207.99: icmp_seq=0 ttl=242 time=55.199 ms
>64 bytes from 72.14.207.99: icmp_seq=1 ttl=242 time=56.382 ms
>^C
>--- google.com ping statistics ---
>2 packets transmitted, 2 packets received, 0% packet loss
>round-trip min/avg/max/stddev = 55.199/55.790/56.382/0.592 ms
>bash2-2.05b$ ping yahoo.com
>PING yahoo.com (68.180.206.184): 56 data bytes
>64 bytes from 68.180.206.184: icmp_seq=0 ttl=52 time=89.973 ms
>64 bytes from 68.180.206.184: icmp_seq=1 ttl=52 time=104.619 ms
>64 bytes from 68.180.206.184: icmp_seq=2 ttl=52 time=89.305 ms
>64 bytes from 68.180.206.184: icmp_seq=3 ttl=52 time=90.078 ms
>^C
>--- yahoo.com ping statistics ---
>4 packets transmitted, 4 packets received, 0% packet loss
>round-trip min/avg/max/stddev = 89.305/93.494/104.619/6.430 ms
>bash2-2.05b$ ping uiuc.edu
>PING uiuc.edu (128.174.254.29): 56 data bytes
>^C
>--- uiuc.edu ping statistics ---
>4 packets transmitted, 0 packets received, 100% packet loss
>bash2-2.05b$ ping www.uiuc.edu
>PING swan29.admin.uiuc.edu (128.174.254.29): 56 data bytes
>^C
>--- swan29.admin.uiuc.edu ping statistics ---
>7 packets transmitted, 0 packets received, 100% packet loss
>bash2-2.05b$ ping login.ks.uiuc.edu
>PING winnipeg.ks.uiuc.edu (130.126.120.41): 56 data bytes
>^C
>--- winnipeg.ks.uiuc.edu ping statistics ---
>13 packets transmitted, 0 packets received, 100% packet loss
>bash2-2.05b$ ping www.beckman.uiuc.edu
>PING bi-www1.beckman.uiuc.edu (130.126.116.250): 56 data bytes
>^C
>--- bi-www1.beckman.uiuc.edu ping statistics ---
>6 packets transmitted, 0 packets received, 100% packet loss
>bash2-2.05b$ date
>Thu Jun 19 16:39:33 CDT 2008
>bash2-2.05b$       
>
>
>
>---
>
>
>
>   Thanks for any insight you can provide.
>
>        Cheers,
>
>
>        Barry
>
>
>>  Here's what I get from zeco to google.com now (2:40pm Tue):
>> 
>> 
>> [slevy at zeco ~]$ traceroute www.google.com
>> traceroute: Warning: www.google.com has multiple addresses; using 64.233.169.99
>> traceroute to www.l.google.com (64.233.169.99), 64 hops max, 40 byte packets
>>  1  192.168.11.1 (192.168.11.1)  0.366 ms  0.519 ms  0.463 ms
>>  2  * * *
>>  3  ge-1-2-ur01.champaign.il.chicago.comcast.net (68.85.178.65)  13.067 ms  14.257 ms  18.691 ms
>>  4  pos-0-10-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.90.174)  15.016 ms  20.180 ms  21.873 ms
>>  5  pos-0-0-0-0-cr01.nashville.tn.ibone.comcast.net (68.86.90.173)  28.347 ms  25.456 ms  32.600 ms
>>  6  pos-0-5-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.66)  32.474 ms  39.619 ms  31.696 ms
>>  7  te-9-1.car1.Atlanta2.Level3.net (4.71.252.29)  38.348 ms  233.805 ms  202.324 ms
>>  8  ae-21-52.car1.Atlanta1.Level3.net (4.68.103.34)  32.476 ms  34.408 ms  34.820 ms
>>  9  GOOGLE-INC.car1.Atlanta1.Level3.net (4.78.209.194)  35.161 ms  39.392 ms  42.619 ms
>> 10  209.85.254.188 (209.85.254.188)  59.483 ms  45.657 ms  65.054 ms
>> 11  72.14.238.137 (72.14.238.137)  51.222 ms
>>     72.14.238.139 (72.14.238.139)  54.197 ms
>>     72.14.238.137 (72.14.238.137)  52.119 ms
>> 12  64.233.175.169 (64.233.175.169)  59.934 ms
>>     64.233.175.109 (64.233.175.109)  46.281 ms
>>     64.233.175.111 (64.233.175.111)  47.436 ms
>> 13  216.239.49.149 (216.239.49.149)  50.079 ms
>>     216.239.49.145 (216.239.49.145)  51.710 ms  50.709 ms
>> 14  yo-in-f99.google.com (64.233.169.99)  48.751 ms  52.487 ms  52.077 ms
>> 
>> 
>> >          Cheers,
>> > 
>> >          Barry
>> > 
>> > -- 
>> > Barry Isralewitz   Theoretical and Computational Biophysics Group, UIUC  
>> > Beckman 3043   Office Phone: (217) 244-1612  Home Phone: (217) 337-6364
>> > email: barryi at ks.uiuc.edu      http://www.ks.uiuc.edu/~barryi
>> > _______________________________________________
>> > IMC-Tech mailing list
>> > IMC-Tech at lists.ucimc.org
>> > http://lists.chambana.net/cgi-bin/listinfo/imc-tech
>
>-- 
>Barry Isralewitz, Ph. D.   Theoretical and Computational Biophysics Group, UIUC
>Beckman 3043    Office Phone: (217) 244-1612   Home Phone: (217) 337-6364
>email: barryi at ks.uiuc.edu      http://www.ks.uiuc.edu/~barryi
>
>----- End forwarded message -----
>
>-- 
>Barry Isralewitz, Ph. D.   Theoretical and Computational Biophysics Group, UIUC
>Beckman 3043    Office Phone: (217) 244-1612   Home Phone: (217) 337-6364
>email: barryi at ks.uiuc.edu      http://www.ks.uiuc.edu/~barryi
>_______________________________________________
>IMC-Tech mailing list
>IMC-Tech at lists.ucimc.org
>http://lists.chambana.net/cgi-bin/listinfo/imc-tech



More information about the IMC-Tech mailing list