If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
DSL problem with Compac
I'm trying to get my Compac Presario 5000 backup computer to log on the
net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA -- I love a good meal! That's why I don't cook. |
Ads |
#2
|
|||
|
|||
DSL problem with Compac
KenK wrote:
I'm trying to get my Compac Presario 5000 backup computer to log on the net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA This is my Ethernet connection to my ADSL modem/router. (About 140KB image) https://s1.postimg.org/6jmkfbmrwv/lo...connection.gif These are some tests I can do, to verify DHCP, DNS, and ping work. (About 24KB image) https://s1.postimg.org/6jzbtid027/command_prompt.gif In particular, this ping test to sun.com, should work if you have the ability to pass packets. ping 156.151.59.35 The tick box "Notify me when this connection has limited or no connectivity" as far as I know, it contacts a well known web page on a Microsoft server, using a symbolic address ("microsoft.com" style), which verifies DNS works and packet transfer works. The HTML fetched is tiny, and is only intended to check the plumbing. By you doing the nslookup and ping tests, that achieves much the same results. The Repair button issues some network stack resets, but I don't think you need that just yet. If you want to post a picture, you can do it here. https://postimage.org/index.php?um=flash Paul |
#3
|
|||
|
|||
DSL problem with Compac
Paul wrote in news
KenK wrote: I'm trying to get my Compac Presario 5000 backup computer to log on the net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA This is my Ethernet connection to my ADSL modem/router. (About 140KB image) https://s1.postimg.org/6jmkfbmrwv/lo...connection.gif These are some tests I can do, to verify DHCP, DNS, and ping work. (About 24KB image) https://s1.postimg.org/6jzbtid027/command_prompt.gif In particular, this ping test to sun.com, should work if you have the ability to pass packets. ping 156.151.59.35 The tick box "Notify me when this connection has limited or no connectivity" as far as I know, it contacts a well known web page on a Microsoft server, using a symbolic address ("microsoft.com" style), which verifies DNS works and packet transfer works. The HTML fetched is tiny, and is only intended to check the plumbing. By you doing the nslookup and ping tests, that achieves much the same results. The Repair button issues some network stack resets, but I don't think you need that just yet. If you want to post a picture, you can do it here. https://postimage.org/index.php?um=flash Paul Thank you for the great response! My results pretty much match those you showed me for first connection. However, my Local Area Connection Support Details window only shows the first three items filled in, not all nine as yours shows. However, the Local Area Connection Properties window is entirely different. Gives me a choice of Windows Locator or DCE Cell Directory Service. Neither rings a bell with me. The Ping 156.151.59.35 Doesn't wotk. "Destination host unreachable". I double-checked and I used correct numbers. Any suggestions? TIA -- I love a good meal! That's why I don't cook. |
#4
|
|||
|
|||
DSL problem with Compac
KenK wrote:
Paul wrote in news KenK wrote: I'm trying to get my Compac Presario 5000 backup computer to log on the net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA This is my Ethernet connection to my ADSL modem/router. (About 140KB image) https://s1.postimg.org/6jmkfbmrwv/lo...connection.gif These are some tests I can do, to verify DHCP, DNS, and ping work. (About 24KB image) https://s1.postimg.org/6jzbtid027/command_prompt.gif In particular, this ping test to sun.com, should work if you have the ability to pass packets. ping 156.151.59.35 The tick box "Notify me when this connection has limited or no connectivity" as far as I know, it contacts a well known web page on a Microsoft server, using a symbolic address ("microsoft.com" style), which verifies DNS works and packet transfer works. The HTML fetched is tiny, and is only intended to check the plumbing. By you doing the nslookup and ping tests, that achieves much the same results. The Repair button issues some network stack resets, but I don't think you need that just yet. If you want to post a picture, you can do it here. https://postimage.org/index.php?um=flash Paul Thank you for the great response! My results pretty much match those you showed me for first connection. However, my Local Area Connection Support Details window only shows the first three items filled in, not all nine as yours shows. However, the Local Area Connection Properties window is entirely different. Gives me a choice of Windows Locator or DCE Cell Directory Service. Neither rings a bell with me. The Ping 156.151.59.35 Doesn't wotk. "Destination host unreachable". I double-checked and I used correct numbers. Any suggestions? TIA In your "Local Area Connection Support Details", try scrolling down to the bottom of the three-entry window until you see "Internet Protocol (TCP/IP). You might have been selecting "Client for Microsoft Networks" and doing Properties on that one. I think what you were seeing, was the properties of the top item, which shows Windows Locator. You might have been seeing this when you tried it, and you have to scroll the list further down and try again. [image 62KB] https://s1.postimg.org/8spsa7t33j/Cl...t_Networks.gif ******* When you work in your Command Prompt window, you can right click the top bar, and there is Edit : Select All. The background within the Command Prompt will turn white. Now, right-click the top bar again, and do Edit : Copy. What that does, is copy the text in the Command Prompt window. Then go to your USENET client (Xnews?) and paste the text. Edit the text, so it shows the output of your ipconfig command. This is mine pasted again. ******* Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\User Nameipconfig Windows IP Configuration Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 ******* I think yours might be showing the APIPA address, instead of a LAN address. "The APIPA reserved range is 169.254.0.0 – 169.254.255.255" When that happens, it means the computer is not able to reach the DHCP server, and get a "normal" lan address. Normal LAN addresses (the unrouted ones for LANs and not the general Internet), are in the 192.168.x.x range or the 10.x.x.x range. You can see in this example, I got a 169.254.x.x address, the "bad" APIPA address. https://s1.postimg.org/9sxybcudtb/li...pa_address.gif I simulated that in a WinXP VM, and selected Internal Network versus Bridged Connection. That prevents me from seeing a router, and the OS burps up an imaginary APIPA address to console itself. I think yours might be similar. But I'm stuck on the "next step". In your case, if it was APIPA, why is it doing that ? It's highly unlikely the router has DHCP disabled. It would make it pretty hard to log into the router and configure it, if the networking connection was that broken. Are you able to reach the web interface on the router ? Via any means ? Have you ever seen it before ? Paul |
#5
|
|||
|
|||
DSL problem with Compac
Paul wrote in newssth67$md3$1
@gioia.aioe.org: KenK wrote: Paul wrote in news KenK wrote: I'm trying to get my Compac Presario 5000 backup computer to log on the net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA This is my Ethernet connection to my ADSL modem/router. (About 140KB image) https://s1.postimg.org/6jmkfbmrwv/lo...connection.gif These are some tests I can do, to verify DHCP, DNS, and ping work. (About 24KB image) https://s1.postimg.org/6jzbtid027/command_prompt.gif In particular, this ping test to sun.com, should work if you have the ability to pass packets. ping 156.151.59.35 The tick box "Notify me when this connection has limited or no connectivity" as far as I know, it contacts a well known web page on a Microsoft server, using a symbolic address ("microsoft.com" style), which verifies DNS works and packet transfer works. The HTML fetched is tiny, and is only intended to check the plumbing. By you doing the nslookup and ping tests, that achieves much the same results. The Repair button issues some network stack resets, but I don't think you need that just yet. If you want to post a picture, you can do it here. https://postimage.org/index.php?um=flash Paul Thank you for the great response! My results pretty much match those you showed me for first connection. However, my Local Area Connection Support Details window only shows the first three items filled in, not all nine as yours shows. However, the Local Area Connection Properties window is entirely different. Gives me a choice of Windows Locator or DCE Cell Directory Service. Neither rings a bell with me. The Ping 156.151.59.35 Doesn't wotk. "Destination host unreachable". I double-checked and I used correct numbers. Any suggestions? TIA In your "Local Area Connection Support Details", try scrolling down to the bottom of the three-entry window until you see "Internet Protocol (TCP/IP). You might have been selecting "Client for Microsoft Networks" and doing Properties on that one. I think what you were seeing, was the properties of the top item, which shows Windows Locator. You might have been seeing this when you tried it, and you have to scroll the list further down and try again. [image 62KB] https://s1.postimg.org/8spsa7t33j/Cl...rosoft_Network s.gif ******* When you work in your Command Prompt window, you can right click the top bar, and there is Edit : Select All. The background within the Command Prompt will turn white. Now, right-click the top bar again, and do Edit : Copy. What that does, is copy the text in the Command Prompt window. Then go to your USENET client (Xnews?) and paste the text. Edit the text, so it shows the output of your ipconfig command. This is mine pasted again. ******* Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\User Nameipconfig Windows IP Configuration Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 ******* I think yours might be showing the APIPA address, instead of a LAN address. "The APIPA reserved range is 169.254.0.0 – 169.254.255.255" When that happens, it means the computer is not able to reach the DHCP server, and get a "normal" lan address. Normal LAN addresses (the unrouted ones for LANs and not the general Internet), are in the 192.168.x.x range or the 10.x.x.x range. You can see in this example, I got a 169.254.x.x address, the "bad" APIPA address. https://s1.postimg.org/9sxybcudtb/li...tivity_apipa_a ddress.gi f I simulated that in a WinXP VM, and selected Internal Network versus Bridged Connection. That prevents me from seeing a router, and the OS burps up an imaginary APIPA address to console itself. I think yours might be similar. But I'm stuck on the "next step". In your case, if it was APIPA, why is it doing that ? It's highly unlikely the router has DHCP disabled. It would make it pretty hard to log into the router and configure it, if the networking connection was that broken. Are you able to reach the web interface on the router ? Via any means ? Have you ever seen it before ? Paul I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA -- I love a good meal! That's why I don't cook. |
#6
|
|||
|
|||
DSL problem with Compac
In message , KenK
writes: [] Rechecked and Firefox on Compaq still not finding on-line destinations. TIA Can it see the router's web interface? 4 -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf "Usenet is a way of being annoyed by people you otherwise never would have met." - John J. Kinyon |
#7
|
|||
|
|||
DSL problem with Compac
KenK wrote:
I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I had to resort to disabling a Service in the Service control panel (of Administrative Tools), to get a partially disabled network connection. I got a network address of zero though. Compare this to what you're seeing. https://s1.postimg.org/3e4yp8o2pb/wh...e_disabled.gif My theory is, something in the OS, a setting somewhere is doing it. And I was able to break it by pretending to be an administrator and screwing up a service. Maybe a dependency a service needs, isn't being met. Paul |
#8
|
|||
|
|||
DSL problem with Compac
"J. P. Gilliver (John)" wrote in
: In message , KenK writes: [] Rechecked and Firefox on Compaq still not finding on-line destinations. TIA Can it see the router's web interface? 4 Sorry, don't understand. Please explain for the computer ignorant? TIA -- I love a good meal! That's why I don't cook. |
#9
|
|||
|
|||
DSL problem with Compac
Paul wrote in news
KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I had to resort to disabling a Service in the Service control panel (of Administrative Tools), to get a partially disabled network connection. I got a network address of zero though. Compare this to what you're seeing. https://s1.postimg.org/3e4yp8o2pb/wh...e_disabled.gif My theory is, something in the OS, a setting somewhere is doing it. And I was able to break it by pretending to be an administrator and screwing up a service. Maybe a dependency a service needs, isn't being met. Paul So that leaves ... Reload XP? Can I do so now that MS has made XP obsolete? You used to have to contact MS to get permission to install XP. What is the situation now? Just freely install XP on any computer? Or does one still have to call? Any thoughts about a less drastic solution? Though the reinstall wouldn't be that terrible. I rarely use the backup system and if DSL worked it wouldn't take long to DL the few programs I'd use on it - Firefox, Eudora, Xnews, Total Commander (file manager) and that's about it that I can think of. TIA -- I love a good meal! That's why I don't cook. |
#10
|
|||
|
|||
DSL problem with Compac
KenK wrote:
Paul wrote in news KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I had to resort to disabling a Service in the Service control panel (of Administrative Tools), to get a partially disabled network connection. I got a network address of zero though. Compare this to what you're seeing. https://s1.postimg.org/3e4yp8o2pb/wh...e_disabled.gif My theory is, something in the OS, a setting somewhere is doing it. And I was able to break it by pretending to be an administrator and screwing up a service. Maybe a dependency a service needs, isn't being met. Paul So that leaves ... Reload XP? Can I do so now that MS has made XP obsolete? You used to have to contact MS to get permission to install XP. What is the situation now? Just freely install XP on any computer? Or does one still have to call? Any thoughts about a less drastic solution? Though the reinstall wouldn't be that terrible. I rarely use the backup system and if DSL worked it wouldn't take long to DL the few programs I'd use on it - Firefox, Eudora, Xnews, Total Commander (file manager) and that's about it that I can think of. TIA I was hoping you'd look in Control Panels : Administrators Tools : Services and see if the two services in question are running or not. Sure, you can Repair Install WinXP, without losing your files or programs. But, will that fix it ? Such a repair would require visiting Windows Update, and re-installing security patches since the date the WinXP CD was released. So if you had a WinXP SP3 disc for Repair Install, there might be a hundred security patches to do after that. And while that's running, the Windows Update wuauserv has to be in working order, for you to get the patches. Keep a copy of IE8 standalone on a USB stick, in case the update system starts having problems with IE5 or IE6 in WinXP. The activation system hasn't changed. You need your license key. It could be on a COA sticker. It could be on the sleeve of some WinXP retail or system installer media. You have to nail down a key first, before getting yourself primed for a Repair Install. The installer is not clever enough to re-use the current key on its own. If WinXP is not happy with doing network activation (maybe you've re-installed the OS too many times in the last X months), then you may end up calling the automated activation phone number anyway. The activation server, may not be enforcing System Builder reinstalls as closely as it was at one time, and may let a reinstall slide (and activate) with no muss or fuss. There are a few variables as to what happens with activation servers. Worst case (highly unlikely at this date), you actually talk to a human. Microsoft doesn't want that to happen. As long as you've made a backup of the C: drive with something like Macrium, if the reinstall goes badly, or you "want out", use the Macrium Emergency CD to boot the computer, then restore from your external storage where you put the WinXP backup. Paul |
#11
|
|||
|
|||
DSL problem with Compac
Paul wrote in news
KenK wrote: Paul wrote in news KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I couldn't find these two dialog boxes as shown in your link to check them. How do I access them? I had to resort to disabling a Service in the Service control panel (of Administrative Tools), to get a partially disabled network connection. I got a network address of zero though. Compare this to what you're seeing. https://s1.postimg.org/3e4yp8o2pb/wh...ice_disabled.g if My theory is, something in the OS, a setting somewhere is doing it. And I was able to break it by pretending to be an administrator and screwing up a service. Maybe a dependency a service needs, isn't being met. Paul So that leaves ... Reload XP? Can I do so now that MS has made XP obsolete? You used to have to contact MS to get permission to install XP. What is the situation now? Just freely install XP on any computer? Or does one still have to call? Any thoughts about a less drastic solution? Though the reinstall wouldn't be that terrible. I rarely use the backup system and if DSL worked it wouldn't take long to DL the few programs I'd use on it - Firefox, Eudora, Xnews, Total Commander (file manager) and that's about it that I can think of. TIA I was hoping you'd look in Control Panels : Administrators Tools : Services and see if the two services in question are running or not. Sure, you can Repair Install WinXP, without losing your files or programs. But, will that fix it ? Such a repair would require visiting Windows Update, and re-installing security patches since the date the WinXP CD was released. So if you had a WinXP SP3 disc for Repair Install, there might be a hundred security patches to do after that. And while that's running, the Windows Update wuauserv has to be in working order, for you to get the patches. Keep a copy of IE8 standalone on a USB stick, in case the update system starts having problems with IE5 or IE6 in WinXP. The activation system hasn't changed. You need your license key. It could be on a COA sticker. It could be on the sleeve of some WinXP retail or system installer media. You have to nail down a key first, before getting yourself primed for a Repair Install. The installer is not clever enough to re-use the current key on its own. If WinXP is not happy with doing network activation (maybe you've re-installed the OS too many times in the last X months), then you may end up calling the automated activation phone number anyway. The activation server, may not be enforcing System Builder reinstalls as closely as it was at one time, and may let a reinstall slide (and activate) with no muss or fuss. There are a few variables as to what happens with activation servers. Worst case (highly unlikely at this date), you actually talk to a human. Microsoft doesn't want that to happen. As long as you've made a backup of the C: drive with something like Macrium, if the reinstall goes badly, or you "want out", use the Macrium Emergency CD to boot the computer, then restore from your external storage where you put the WinXP backup. Paul As I said above, I need guidance with your link pictures. The reloading XP sounds very difficult. I have some Windows CDs labled MS including what appears to be the needed key in a bag with some Compaq Recovery CDs. So I'm pretty sure it's for my machine. Thus, if necessary, I can probably reload XP Home. Debating on whether it's worth a day's or more work and getting MS activation permission to do this. Besides, it may not solve my DSL problem, it might be the hardware. I'm hoping I can get the other Compaq with the screen saver and slow speed problems running right since it already uses DSL properly. Right now I'm running Spinrite on it in hopes of speeding it up a little. Back to work on it tomorrow for an hour or so. Thanks for your great help! -- I love a good meal! That's why I don't cook. |
#12
|
|||
|
|||
DSL problem with Compac
KenK wrote:
Paul wrote in news KenK wrote: Paul wrote in news KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I couldn't find these two dialog boxes as shown in your link to check them. How do I access them? The dialog in question, is an executable. Start : Run : services.msc The Services dialog can also be found in Settings : Control Panel : Administrative Tools : Services And no, Repair Install or Clean Install, isn't all that easy. And you'd better have your license key ready. As well as the media you plan to use. It also helps to have a wsusoffline folder, the one with the hundred security patches. Even so, there will be some hair loss while you fight with Windows Update to see "who is the boss". Another thing you might want to have handy, is a standalone IE8 installer, just in case the freshly installed OS cannot manage to use IE6 for some stuff it would normally be able to do. https://web.archive.org/web/20140605...offline921.zip "Modifications in version 9.2.1 NOTE: This version will be the very very last one supporting Windows XP and Office 2003 " You might have to look in the Legacy section for WinXP there. What the program does, is download wsusscn2 from the Windows Update server, and make up a list of security patches (a set of patches for *any* WinXP, not just for the current OS setup). Then, later, there is a "client" folder, and you can run the installer from the client folder, to install the hundred patches. That's the basic idea of Wsusoffline. But as you'd expect, the topic of Windows Update is full of gaping holes to fall into. So this is not a particularly pleasant topic if you're trying to restore a computer, with one posting a day about what to do next :-/ Windows Update drives me nuts, in terms of workarounds to get the damn thing to work. If MS converted all their .cab updates to the newer format, a bound and determined person could use catalog.update.microsoft.com to download patches one at a time and apply them. I spent many hours one month, doing exactly that. Might have been more than 20 hours, for a number of OSes, patching them *without* using Windows Update directly. I was at that so long, I got some neck strain. I'd recommending the OS reinstall thing, for when you've hit a brick wall. Paul |
#13
|
|||
|
|||
DSL problem with Compac
Paul wrote in news
KenK wrote: Paul wrote in news KenK wrote: Paul wrote in news KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I couldn't find these two dialog boxes as shown in your link to check them. How do I access them? The dialog in question, is an executable. Start : Run : services.msc The Services dialog can also be found in Settings : Control Panel : Administrative Tools : Services And no, Repair Install or Clean Install, isn't all that easy. And you'd better have your license key ready. As well as the media you plan to use. It also helps to have a wsusoffline folder, the one with the hundred security patches. Even so, there will be some hair loss while you fight with Windows Update to see "who is the boss". Another thing you might want to have handy, is a standalone IE8 installer, just in case the freshly installed OS cannot manage to use IE6 for some stuff it would normally be able to do. https://web.archive.org/web/20140605...ad.wsusoffline. net/wsusoffline921.zip "Modifications in version 9.2.1 NOTE: This version will be the very very last one supporting Windows XP and Office 2003 " You might have to look in the Legacy section for WinXP there. What the program does, is download wsusscn2 from the Windows Update server, and make up a list of security patches (a set of patches for *any* WinXP, not just for the current OS setup). Then, later, there is a "client" folder, and you can run the installer from the client folder, to install the hundred patches. That's the basic idea of Wsusoffline. But as you'd expect, the topic of Windows Update is full of gaping holes to fall into. So this is not a particularly pleasant topic if you're trying to restore a computer, with one posting a day about what to do next :-/ Windows Update drives me nuts, in terms of workarounds to get the damn thing to work. If MS converted all their .cab updates to the newer format, a bound and determined person could use catalog.update.microsoft.com to download patches one at a time and apply them. I spent many hours one month, doing exactly that. Might have been more than 20 hours, for a number of OSes, patching them *without* using Windows Update directly. I was at that so long, I got some neck strain. I'd recommending the OS reinstall thing, for when you've hit a brick wall. Paul Still trying to get DSL to work. FWIW Last Saturday had a brilliant dea, This backup system Comaq has Ubuntu Linux on it as a dual boot. I've not run Linux in years. Tried it. DSL works fine. So the problem is definitely with XP, not the Comaq. Back to fiddlng with XP. Wish I could just use Linux but dread finding Linux software that will read the Eudora 7.1 and news files on my main Emachine computer. -- I love a good meal! That's why I don't cook. |
#14
|
|||
|
|||
DSL problem with Compac
KenK wrote:
Paul wrote in news KenK wrote: Paul wrote in news KenK wrote: Paul wrote in news KenK wrote: I changed our troubleshooting a bit. Instead of comparing your results with mine I'm comparing my Compaq which doesn't work with DSL and eMachine which does results. Should be the same. Same DSL feed from same modem, same XP Home OS. Found a few differences. The local area connection General in Compaq has 0 packets received - whereas eMachine does have a quantity, as yours does. The local area connection Support in Compaq has no response in the fourth item - Default Gateway - whereas eMachine does, as yours does. The local area connection Support Details in Compaq's fourth to eighth items are blank, unlike all filled in on the eMachine and yours. The command Prompt ping is totally different. Nothing like your results. The emachine shows: Pinging 156.151.59.35 with 32 bytes of data: Reply from 156.151.59.35: bytes=32 time=84ns TIL=244 Reply from 156.151.59.35: bytes=32 time=100ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Reply from 156.151.59.35: bytes=32 time=83ns TIL=244 Ping statistics for 156.151.59.35: Packets: Sent = 4, Received = 4. Last = 0 (0% loss), and two more similar lines. The Compaq says Destination host unreachable four times. You said this is an internet address and this Compaq result is because the DSL connection is not working? However, the eMachine is on line and should get results like yours. I apologize for changing horses in mid stream and likely causing you to repeat some of your previous remarks. Just refer me back to any. These results I reported are quite similar to those I reported in my last message. Seems the Compaq is seeing the DSL signal but something in the DSL signal is missing and the Compaq's programs can't see the on-line servers, etc. What? Why? Questions of the year! Rechecked and Firefox on Compaq still not finding on-line destinations. TIA What matters is you get a solution. I actually prefer it, if you spot something and figure it out. Your method is perfectly valid. I provided some pictures, just to "prime the pump". ******* I tried to screw up the configuration of the Network Connection and the TCP/IP Properties, and the dialog boxes are wired together in such a way, you can't mis-configure it on purpose. If you don't set it to "Auto" for both item, the manual configuration asks too many questions to satisfy it easily and close the dialog box (short of canceling it to make it go away). I couldn't find these two dialog boxes as shown in your link to check them. How do I access them? The dialog in question, is an executable. Start : Run : services.msc The Services dialog can also be found in Settings : Control Panel : Administrative Tools : Services And no, Repair Install or Clean Install, isn't all that easy. And you'd better have your license key ready. As well as the media you plan to use. It also helps to have a wsusoffline folder, the one with the hundred security patches. Even so, there will be some hair loss while you fight with Windows Update to see "who is the boss". Another thing you might want to have handy, is a standalone IE8 installer, just in case the freshly installed OS cannot manage to use IE6 for some stuff it would normally be able to do. https://web.archive.org/web/20140605...ad.wsusoffline. net/wsusoffline921.zip "Modifications in version 9.2.1 NOTE: This version will be the very very last one supporting Windows XP and Office 2003 " You might have to look in the Legacy section for WinXP there. What the program does, is download wsusscn2 from the Windows Update server, and make up a list of security patches (a set of patches for *any* WinXP, not just for the current OS setup). Then, later, there is a "client" folder, and you can run the installer from the client folder, to install the hundred patches. That's the basic idea of Wsusoffline. But as you'd expect, the topic of Windows Update is full of gaping holes to fall into. So this is not a particularly pleasant topic if you're trying to restore a computer, with one posting a day about what to do next :-/ Windows Update drives me nuts, in terms of workarounds to get the damn thing to work. If MS converted all their .cab updates to the newer format, a bound and determined person could use catalog.update.microsoft.com to download patches one at a time and apply them. I spent many hours one month, doing exactly that. Might have been more than 20 hours, for a number of OSes, patching them *without* using Windows Update directly. I was at that so long, I got some neck strain. I'd recommending the OS reinstall thing, for when you've hit a brick wall. Paul Still trying to get DSL to work. FWIW Last Saturday had a brilliant dea, This backup system Comaq has Ubuntu Linux on it as a dual boot. I've not run Linux in years. Tried it. DSL works fine. So the problem is definitely with XP, not the Comaq. Back to fiddlng with XP. Wish I could just use Linux but dread finding Linux software that will read the Eudora 7.1 and news files on my main Emachine computer. Try running Eudora under WINE :-) Look in your Package Manager for WINE. Once installed, try running some "trivial" program under WINE. (Copy file across to it) cd /path/with/the/file chmod 644 someprog.exe wine ./someprog.exe Part of initialization of WINE, is creation of a C partition. Look in ~/.wine and there should be a "drive_C". Now, move the Eudora profile over to the WINE tree and put it in tne right place. Copy over the Eudora folder, and make sure the executable files are chmod'ed 755. The 5 value is "read and execute", as an example. WINE won't run a program unless it is marked as executable. Windows programs can throw up graphics on the Linux screen under WINE. There is a registry (I've never looked for the files). THe WINEHQ (headquarters) on the web, has program ratings. Programs which haven't a hope of running under WINE, will be noted as such. Some programs receive "gold" or "silver" ratings, which is an indication of how compatible they are. If all this has worked out, you can transfer control to Linux. ******* You can also do a clean install of WinXP if you want. Which can have its share of "little procedures" to restore email and USENET. Plus you get to install Service Packs, Security Updates, hardware drivers, and so on. That stuff you pay the computer store $100 to $200 to do... :-) One way to handle WinXP, is with WSUSOffline version 9.2.1. But I might have already covered that. Even with help like that, Windows Update knows how to be annoying, and will provides hours of entertainment. Paul |
#15
|
|||
|
|||
DSL problem with Compac
KenK wrote in
: I'm trying to get my Compac Presario 5000 backup computer to log on the net. Control panel/Network Connections/LAN or High speed internet seems to show a connection, speed, packets, etc. But I can't get Firefox or email ap (Eudora) to connect. They can't find the net. This computer works with a dial-up connection. but VERY slowly. But that's another problem. I'm stumped. What should I look for? The DSL works fine, from the same modem, in my emachine computer. TIA Finally found it! Had wi-fi chosen. Evidently this machine comes that way. My Emachine never had that problem. -- I love a good meal! That's why I don't cook. |
Thread Tools | |
Display Modes | |
|
|