Windows XP Community - XPHeads



Registry Mechanic - Free Scan Now

Can't connect to internet after reboot

microsoft.public.windowsxp.network_web


Reply
  #1 (permalink)  
Old 01-12-2008, 01:19 AM
Steve 1116
 
Posts: n/a
Can't connect to internet after reboot
I have been struggling with this issue on my Win XP desktop for
several months. I have searched these groups and found similar
issues, but none exactly the same. Hopefully someone else has seen
this behavior. When I reboot the machine, I can no longer connect to
the internet. IE7, Firefox, Outlook - nothing works. Then I run IE7
Network Diagnostics. It either says that it fixed the problem or that
there was no problem - and everything then works fine...until the next
reboot. This is consistent and repeatable. I appreciate any help
anyone can provide. Below is the Network Diagnostics log. Thanks in
advance!

Last diagnostic run time: 01/09/08 18:51:36 HTTP, HTTPS, FTP
Diagnostic
HTTP, HTTPS, FTP connectivity
info HTTP: Successfully connected to www.microsoft.com.
info HTTPS: Successfully connected to www.microsoft.com.
info FTP (Passive): Successfully connected to ftp.microsoft.com.
DNS Client Diagnostic
DNS - Not a home user scenario
info Using Web Proxy: no
info Resolving name ok for (www.microsoft.com): yes
No DNS servers
DNS failure
Gateway Diagnostic
Gateway
info The following proxy configuration is being used by IE:
Automatically Detect Settingsisabled Automatic Configuration Script:
Proxy Server: Proxy Bypass list:
info This computer has the following default gateway entry(ies):
192.168.1.1
info This computer has the following IP address(es): 192.168.1.101
info The default gateway is in the same subnet as this computer
info The default gateway entry is a valid unicast address
info The default gateway address was resolved via ARP in 1 try(ies)
info The default gateway was reached via ICMP Ping in 1 try(ies)
info TCP port 80 on host 207.46.193.254 was successfully reached
info The Internet host www.microsoft.com was successfully reached
info The default gateway is OK
IP Layer Diagnostic
Corrupted IP routing table
info The default route is valid
info The loopback route is valid
info The local host route is valid
info The local subnet route is valid
Invalid ARP cache entries
action The ARP cache has been flushed
IP Configuration Diagnostic
Invalid IP address
info Valid IP address detected: 192.168.1.101
Wireless Diagnostic
Wireless - Service disabled
Wireless - User SSID
Wireless - First time setup
Wireless - Radio off
Wireless - Out of range
Wireless - Hardware issue
Wireless - Novice user
Wireless - Ad-hoc network
Wireless - Less preferred
Wireless - 802.1x enabled
Wireless - Configuration mismatch
Wireless - Low SNR
WinSock Diagnostic
WinSock status
info All base service provider entries are present in the Winsock
catalog.
info The Winsock Service provider chains are valid.
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback
communication test.
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback
communication test.
info Provider entry RSVP UDP Service Provider passed the loopback
communication test.
info Provider entry RSVP TCP Service Provider passed the loopback
communication test.
info Connectivity is valid for all Winsock service providers.
Network Adapter Diagnostic
Network location detection
info Using home Internet connection
Network adapter identification
info Network connection: Name=Local Area Connection, Device=Realtek
RTL8139/810x Family Fast Ethernet NIC, MediaType=LAN,
SubMediaType=LAN
info Network connection: Name=1394 Connection, Device=1394 Net
Adapter, MediaType=LAN, SubMediaType=1394
info Ethernet connection selected
Network adapter status
info Network connection status: Connected
HTTP, HTTPS, FTP Diagnostic
HTTP, HTTPS, FTP connectivity
warn HTTP: Error 12007 connecting to www.microsoft.com: The server
name or address could not be resolved
info FTP (Passive): Successfully connected to ftp.microsoft.com.
info HTTP: Successfully connected to www.hotmail.com.
warn HTTPS: Error 12037 connecting to www.passport.net: The date in
the certificate is invalid or has expired
warn HTTPS: Error 12007 connecting to www.microsoft.com: The server
name or address could not be resolved
error Could not make an HTTPS connection.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 01-12-2008, 01:49 AM
Robert L. \(MS-MVP\)
 
Posts: n/a
Re: Can't connect to internet after reboot
For troubleshooting, try to start the computer with clean boot. This how to
may help.

How to run Windows OS with a clean ...With MSCONFIG, you also can configure
a clean boot to disable common startup ... To perform a clean boot, please
follow these steps: 1) Run MSCONFIG.EXE. ...
www.chicagotech.net/netforums/viewtopic.php?t=57


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Steve 1116" <SteveAmico@hotmail.com> wrote in message
news:f6f1f649-81d8-481d-8ef9-46ba9941ca67@f47g2000hsd.googlegroups.com...
>I have been struggling with this issue on my Win XP desktop for
> several months. I have searched these groups and found similar
> issues, but none exactly the same. Hopefully someone else has seen
> this behavior. When I reboot the machine, I can no longer connect to
> the internet. IE7, Firefox, Outlook - nothing works. Then I run IE7
> Network Diagnostics. It either says that it fixed the problem or that
> there was no problem - and everything then works fine...until the next
> reboot. This is consistent and repeatable. I appreciate any help
> anyone can provide. Below is the Network Diagnostics log. Thanks in
> advance!
>
> Last diagnostic run time: 01/09/08 18:51:36 HTTP, HTTPS, FTP
> Diagnostic
> HTTP, HTTPS, FTP connectivity
> info HTTP: Successfully connected to www.microsoft.com.
> info HTTPS: Successfully connected to www.microsoft.com.
> info FTP (Passive): Successfully connected to ftp.microsoft.com.
> DNS Client Diagnostic
> DNS - Not a home user scenario
> info Using Web Proxy: no
> info Resolving name ok for (www.microsoft.com): yes
> No DNS servers
> DNS failure
> Gateway Diagnostic
> Gateway
> info The following proxy configuration is being used by IE:
> Automatically Detect Settingsisabled Automatic Configuration Script:
> Proxy Server: Proxy Bypass list:
> info This computer has the following default gateway entry(ies):
> 192.168.1.1
> info This computer has the following IP address(es): 192.168.1.101
> info The default gateway is in the same subnet as this computer
> info The default gateway entry is a valid unicast address
> info The default gateway address was resolved via ARP in 1 try(ies)
> info The default gateway was reached via ICMP Ping in 1 try(ies)
> info TCP port 80 on host 207.46.193.254 was successfully reached
> info The Internet host www.microsoft.com was successfully reached
> info The default gateway is OK
> IP Layer Diagnostic
> Corrupted IP routing table
> info The default route is valid
> info The loopback route is valid
> info The local host route is valid
> info The local subnet route is valid
> Invalid ARP cache entries
> action The ARP cache has been flushed
> IP Configuration Diagnostic
> Invalid IP address
> info Valid IP address detected: 192.168.1.101
> Wireless Diagnostic
> Wireless - Service disabled
> Wireless - User SSID
> Wireless - First time setup
> Wireless - Radio off
> Wireless - Out of range
> Wireless - Hardware issue
> Wireless - Novice user
> Wireless - Ad-hoc network
> Wireless - Less preferred
> Wireless - 802.1x enabled
> Wireless - Configuration mismatch
> Wireless - Low SNR
> WinSock Diagnostic
> WinSock status
> info All base service provider entries are present in the Winsock
> catalog.
> info The Winsock Service provider chains are valid.
> info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback
> communication test.
> info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback
> communication test.
> info Provider entry RSVP UDP Service Provider passed the loopback
> communication test.
> info Provider entry RSVP TCP Service Provider passed the loopback
> communication test.
> info Connectivity is valid for all Winsock service providers.
> Network Adapter Diagnostic
> Network location detection
> info Using home Internet connection
> Network adapter identification
> info Network connection: Name=Local Area Connection, Device=Realtek
> RTL8139/810x Family Fast Ethernet NIC, MediaType=LAN,
> SubMediaType=LAN
> info Network connection: Name=1394 Connection, Device=1394 Net
> Adapter, MediaType=LAN, SubMediaType=1394
> info Ethernet connection selected
> Network adapter status
> info Network connection status: Connected
> HTTP, HTTPS, FTP Diagnostic
> HTTP, HTTPS, FTP connectivity
> warn HTTP: Error 12007 connecting to www.microsoft.com: The server
> name or address could not be resolved
> info FTP (Passive): Successfully connected to ftp.microsoft.com.
> info HTTP: Successfully connected to www.hotmail.com.
> warn HTTPS: Error 12037 connecting to www.passport.net: The date in
> the certificate is invalid or has expired
> warn HTTPS: Error 12007 connecting to www.microsoft.com: The server
> name or address could not be resolved
> error Could not make an HTTPS connection.
>


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 01-12-2008, 03:02 AM
Steve 1116
 
Posts: n/a
Re: Can't connect to internet after reboot
On Jan 11, 8:49 pm, "Robert L. \(MS-MVP\)"
<blinNoEmailple...@mvps.org> wrote:
> For troubleshooting, try to start the computer with clean boot. This how to
> may help.
>
> How to run Windows OS with a clean ...With MSCONFIG, you also can configure
> a clean boot to disable common startup ... To perform a clean boot, please
> follow these steps: 1) Run MSCONFIG.EXE. ...
> www.chicagotech.net/netforums/viewtopic.php?t=57
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting onhttp://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access onhttp://www.HowToNetworking.com
>
> "Steve 1116" <SteveAm...@hotmail.com> wrote in message
>
> news:f6f1f649-81d8-481d-8ef9-46ba9941ca67@f47g2000hsd.googlegroups.com...
>
> >I have been struggling with this issue on my Win XP desktop for
> > several months. I have searched these groups and found similar
> > issues, but none exactly the same. Hopefully someone else has seen
> > this behavior. When I reboot the machine, I can no longer connect to
> > the internet. IE7, Firefox, Outlook - nothing works. Then I run IE7
> > Network Diagnostics. It either says that it fixed the problem or that
> > there was no problem - and everything then works fine...until the next
> > reboot. This is consistent and repeatable. I appreciate any help
> > anyone can provide. Below is the Network Diagnostics log. Thanks in
> > advance!

>
> > Last diagnostic run time: 01/09/08 18:51:36 HTTP, HTTPS, FTP
> > Diagnostic
> > HTTP, HTTPS, FTP connectivity
> > info HTTP: Successfully connected towww.microsoft.com.
> > info HTTPS: Successfully connected towww.microsoft.com.
> > info FTP (Passive): Successfully connected to ftp.microsoft.com.
> > DNS Client Diagnostic
> > DNS - Not a home user scenario
> > info Using Web Proxy: no
> > info Resolving name ok for (www.microsoft.com):yes
> > No DNS servers
> > DNS failure
> > Gateway Diagnostic
> > Gateway
> > info The following proxy configuration is being used by IE:
> > Automatically Detect Settingsisabled Automatic Configuration Script:
> > Proxy Server: Proxy Bypass list:
> > info This computer has the following default gateway entry(ies):
> > 192.168.1.1
> > info This computer has the following IP address(es): 192.168.1.101
> > info The default gateway is in the same subnet as this computer
> > info The default gateway entry is a valid unicast address
> > info The default gateway address was resolved via ARP in 1 try(ies)
> > info The default gateway was reached via ICMP Ping in 1 try(ies)
> > info TCP port 80 on host 207.46.193.254 was successfully reached
> > info The Internet hostwww.microsoft.comwas successfully reached
> > info The default gateway is OK
> > IP Layer Diagnostic
> > Corrupted IP routing table
> > info The default route is valid
> > info The loopback route is valid
> > info The local host route is valid
> > info The local subnet route is valid
> > Invalid ARP cache entries
> > action The ARP cache has been flushed
> > IP Configuration Diagnostic
> > Invalid IP address
> > info Valid IP address detected: 192.168.1.101
> > Wireless Diagnostic
> > Wireless - Service disabled
> > Wireless - User SSID
> > Wireless - First time setup
> > Wireless - Radio off
> > Wireless - Out of range
> > Wireless - Hardware issue
> > Wireless - Novice user
> > Wireless - Ad-hoc network
> > Wireless - Less preferred
> > Wireless - 802.1x enabled
> > Wireless - Configuration mismatch
> > Wireless - Low SNR
> > WinSock Diagnostic
> > WinSock status
> > info All base service provider entries are present in the Winsock
> > catalog.
> > info The Winsock Service provider chains are valid.
> > info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback
> > communication test.
> > info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback
> > communication test.
> > info Provider entry RSVP UDP Service Provider passed the loopback
> > communication test.
> > info Provider entry RSVP TCP Service Provider passed the loopback
> > communication test.
> > info Connectivity is valid for all Winsock service providers.
> > Network Adapter Diagnostic
> > Network location detection
> > info Using home Internet connection
> > Network adapter identification
> > info Network connection: Name=Local Area Connection, Device=Realtek
> > RTL8139/810x Family Fast Ethernet NIC, MediaType=LAN,
> > SubMediaType=LAN
> > info Network connection: Name=1394 Connection, Device=1394 Net
> > Adapter, MediaType=LAN, SubMediaType=1394
> > info Ethernet connection selected
> > Network adapter status
> > info Network connection status: Connected
> > HTTP, HTTPS, FTP Diagnostic
> > HTTP, HTTPS, FTP connectivity
> > warn HTTP: Error 12007 connecting towww.microsoft.com:The server
> > name or address could not be resolved
> > info FTP (Passive): Successfully connected to ftp.microsoft.com.
> > info HTTP: Successfully connected towww.hotmail.com.
> > warn HTTPS: Error 12037 connecting towww.passport.net:The date in
> > the certificate is invalid or has expired
> > warn HTTPS: Error 12007 connecting towww.microsoft.com:The server
> > name or address could not be resolved
> > error Could not make an HTTPS connection.


Robert - Thanks for the help! I ran the clean boot and connectivity
worked okay. I had 31 non-MS services running, so now I have the task
to determine which one is causing the problem, but I have a path to
follow so that is good - thanks again!
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 01-12-2008, 12:36 PM
John B
 
Posts: n/a
Re: Can't connect to internet after reboot
FWIW, do you have a second computer, running simultaneously, at this site?
I sense from your description of the immediacy of fault, upon reboot, that
this circumstance is unlikely, yet I would like to ask the question, anyway.

My point is that your Internet Service Provider might be flaky. If a second
computer can see the internet when your problem computer cannot, then your
ISP is off the hook.

Back in the days when we fixed our own audio equipment, it was always
comparatively easy to fix one bad amplifier in a stereo pair, for this very
reason.


"Steve 1116" <SteveAmico@hotmail.com> wrote in message
news:f6f1f649-81d8-481d-8ef9-46ba9941ca67@f47g2000hsd.googlegroups.com...
> I have been struggling with this issue on my Win XP desktop for
> several months.




Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 01-12-2008, 03:23 PM
Robert L. \(MS-MVP\)
 
Posts: n/a
Re: Can't connect to internet after reboot
Thank you for the feedback.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Steve 1116" <SteveAmico@hotmail.com> wrote in message
news:75d3a083-0511-4320-8fc1-0469b14203e4@v46g2000hsv.googlegroups.com...
> On Jan 11, 8:49 pm, "Robert L. \(MS-MVP\)"
> <blinNoEmailple...@mvps.org> wrote:
>> For troubleshooting, try to start the computer with clean boot. This how
>> to
>> may help.
>>
>> How to run Windows OS with a clean ...With MSCONFIG, you also can
>> configure
>> a clean boot to disable common startup ... To perform a clean boot,
>> please
>> follow these steps: 1) Run MSCONFIG.EXE. ...
>> www.chicagotech.net/netforums/viewtopic.php?t=57
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting
>> onhttp://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access
>> onhttp://www.HowToNetworking.com
>>
>> "Steve 1116" <SteveAm...@hotmail.com> wrote in message
>>
>> news:f6f1f649-81d8-481d-8ef9-46ba9941ca67@f47g2000hsd.googlegroups.com...
>>
>> >I have been struggling with this issue on my Win XP desktop for
>> > several months. I have searched these groups and found similar
>> > issues, but none exactly the same. Hopefully someone else has seen
>> > this behavior. When I reboot the machine, I can no longer connect to
>> > the internet. IE7, Firefox, Outlook - nothing works. Then I run IE7
>> > Network Diagnostics. It either says that it fixed the problem or that
>> > there was no problem - and everything then works fine...until the next
>> > reboot. This is consistent and repeatable. I appreciate any help
>> > anyone can provide. Below is the Network Diagnostics log. Thanks in
>> > advance!

>>
>> > Last diagnostic run time: 01/09/08 18:51:36 HTTP, HTTPS, FTP
>> > Diagnostic
>> > HTTP, HTTPS, FTP connectivity
>> > info HTTP: Successfully connected towww.microsoft.com.
>> > info HTTPS: Successfully connected towww.microsoft.com.
>> > info FTP (Passive): Successfully connected to ftp.microsoft.com.
>> > DNS Client Diagnostic
>> > DNS - Not a home user scenario
>> > info Using Web Proxy: no
>> > info Resolving name ok for (www.microsoft.com):yes
>> > No DNS servers
>> > DNS failure
>> > Gateway Diagnostic
>> > Gateway
>> > info The following proxy configuration is being used by IE:
>> > Automatically Detect Settingsisabled Automatic Configuration Script:
>> > Proxy Server: Proxy Bypass list:
>> > info This computer has the following default gateway entry(ies):
>> > 192.168.1.1
>> > info This computer has the following IP address(es): 192.168.1.101
>> > info The default gateway is in the same subnet as this computer
>> > info The default gateway entry is a valid unicast address
>> > info The default gateway address was resolved via ARP in 1 try(ies)
>> > info The default gateway was reached via ICMP Ping in 1 try(ies)
>> > info TCP port 80 on host 207.46.193.254 was successfully reached
>> > info The Internet hostwww.microsoft.comwas successfully reached
>> > info The default gateway is OK
>> > IP Layer Diagnostic
>> > Corrupted IP routing table
>> > info The default route is valid
>> > info The loopback route is valid
>> > info The local host route is valid
>> > info The local subnet route is valid
>> > Invalid ARP cache entries
>> > action The ARP cache has been flushed
>> > IP Configuration Diagnostic
>> > Invalid IP address
>> > info Valid IP address detected: 192.168.1.101
>> > Wireless Diagnostic
>> > Wireless - Service disabled
>> > Wireless - User SSID
>> > Wireless - First time setup
>> > Wireless - Radio off
>> > Wireless - Out of range
>> > Wireless - Hardware issue
>> > Wireless - Novice user
>> > Wireless - Ad-hoc network
>> > Wireless - Less preferred
>> > Wireless - 802.1x enabled
>> > Wireless - Configuration mismatch
>> > Wireless - Low SNR
>> > WinSock Diagnostic
>> > WinSock status
>> > info All base service provider entries are present in the Winsock
>> > catalog.
>> > info The Winsock Service provider chains are valid.
>> > info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback
>> > communication test.
>> > info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback
>> > communication test.
>> > info Provider entry RSVP UDP Service Provider passed the loopback
>> > communication test.
>> > info Provider entry RSVP TCP Service Provider passed the loopback
>> > communication test.
>> > info Connectivity is valid for all Winsock service providers.
>> > Network Adapter Diagnostic
>> > Network location detection
>> > info Using home Internet connection
>> > Network adapter identification
>> > info Network connection: Name=Local Area Connection, Device=Realtek
>> > RTL8139/810x Family Fast Ethernet NIC, MediaType=LAN,
>> > SubMediaType=LAN
>> > info Network connection: Name=1394 Connection, Device=1394 Net
>> > Adapter, MediaType=LAN, SubMediaType=1394
>> > info Ethernet connection selected
>> > Network adapter status
>> > info Network connection status: Connected
>> > HTTP, HTTPS, FTP Diagnostic
>> > HTTP, HTTPS, FTP connectivity
>> > warn HTTP: Error 12007 connecting towww.microsoft.com:The server
>> > name or address could not be resolved
>> > info FTP (Passive): Successfully connected to ftp.microsoft.com.
>> > info HTTP: Successfully connected towww.hotmail.com.
>> > warn HTTPS: Error 12037 connecting towww.passport.net:The date in
>> > the certificate is invalid or has expired
>> > warn HTTPS: Error 12007 connecting towww.microsoft.com:The server
>> > name or address could not be resolved
>> > error Could not make an HTTPS connection.

>
> Robert - Thanks for the help! I ran the clean boot and connectivity
> worked okay. I had 31 non-MS services running, so now I have the task
> to determine which one is causing the problem, but I have a path to
> follow so that is good - thanks again!


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 01-12-2008, 08:32 PM
Steve 1116
 
Posts: n/a
Re: Can't connect to internet after reboot
On Jan 12, 7:36 am, "John B" <j...@nospam.com> wrote:
> FWIW, do you have a second computer, running simultaneously, at this site?
> I sense from your description of the immediacy of fault, upon reboot, that
> this circumstance is unlikely, yet I would like to ask the question, anyway.
>
> My point is that your Internet Service Provider might be flaky. If a second
> computer can see the internet when your problem computer cannot, then your
> ISP is off the hook.
>
> Back in the days when we fixed our own audio equipment, it was always
> comparatively easy to fix one bad amplifier in a stereo pair, for this very
> reason.
>
> "Steve 1116" <SteveAm...@hotmail.com> wrote in message
>
> news:f6f1f649-81d8-481d-8ef9-46ba9941ca67@f47g2000hsd.googlegroups.com...
>
> > I have been struggling with this issue on my Win XP desktop for
> > several months.


Thanks for the reply, John. I left out all of the steps I took over
the months, but yes, I do have a second computer which has worked fine
throughout. I investigated the router (swapped one with a friend),
the cables, the network card (swapped it with another), etc... and
finally narrowed it down to the one machine. Since I could eventually
get it to work, I delayed addressing it, but I am just waiting for the
day when it stops working altogether! Thanks again for the reply.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 11:10 PM.


Registry Mechanic - Free Scan Now
Driver Scanner 2009 - Free Scan Now




Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 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 65 66 67 68 69 70 71 72 73 74