SBC/Yahoo DSL down after Win98se upgrade.

This is not a DUN issue. DUN is not in any way involved in DSL connections.

--
Gary S. Terhune
MS MVP Shell/User

"James Egan" wrote in message
...
On Thu, 13 Oct 2005 01:35:29 GMT, dylan wrote:

I also had him ping google.com and he received an
"Unknown Host" error, but when I had him ping
216.239.37.99, he received the usual four replies
with no loss.

Then it's clearly a dns problem. This information is usually passed on
to the pc along with it's ip address as part of the dhcp process. You
will need to rebuild the winsock as follows

1. Un-install Dial-Up Networking. Don't reboot.
2. Delete registry key HKLM\System\CurrentControlSet\Services\Winsock2
3. Re-install Dial-Up Networking. Reboot.


Jim.

On Thu, 13 Oct 2005 02:31:08 -0700, "Gary S. Terhune"
wrote:

This is not a DUN issue.

I know it's not a DUN issue. It's a DNS issue which is a sign of a
damaged winsock. That's how to rebuild the winsock in win9x.


DUN is not in any way involved in DSL connections.

That's incorrect but a different matter. DSL connections quite often
use dial up networking. Simply substituting a dsl modem for an
analogue one.


Jim.

On Thu, 13 Oct 2005 02:31:08 -0700, "Gary S. Terhune"
wrote:

This is not a DUN issue.

I know it's not a DUN issue. It's a DNS issue which is a sign of a
damaged winsock. That's how to rebuild the winsock in win9x.


DUN is not in any way involved in DSL connections.

That's incorrect but a different matter. DSL connections quite often
use dial up networking. Simply substituting a dsl modem for an
analogue one.


Jim.

Sorry, I was at the blitzy end of a blitzy day. You're right, of course, but
there are also other issues that could be involved, and this page includes
not only your WINSOCK repair but also other suggestions pertinent to this
issue.
http://www.dslreports.com/faq/1453

--
Gary S. Terhune
MS MVP Shell/User

"James Egan" wrote in message
...
On Thu, 13 Oct 2005 02:31:08 -0700, "Gary S. Terhune"
wrote:

This is not a DUN issue.

I know it's not a DUN issue. It's a DNS issue which is a sign of a
damaged winsock. That's how to rebuild the winsock in win9x.


DUN is not in any way involved in DSL connections.

That's incorrect but a different matter. DSL connections quite often
use dial up networking. Simply substituting a dsl modem for an
analogue one.


Jim.

Sorry, I was at the blitzy end of a blitzy day. You're right, of course, but
there are also other issues that could be involved, and this page includes
not only your WINSOCK repair but also other suggestions pertinent to this
issue.
http://www.dslreports.com/faq/1453

--
Gary S. Terhune
MS MVP Shell/User

"James Egan" wrote in message
...
On Thu, 13 Oct 2005 02:31:08 -0700, "Gary S. Terhune"
wrote:

This is not a DUN issue.

I know it's not a DUN issue. It's a DNS issue which is a sign of a
damaged winsock. That's how to rebuild the winsock in win9x.


DUN is not in any way involved in DSL connections.

That's incorrect but a different matter. DSL connections quite often
use dial up networking. Simply substituting a dsl modem for an
analogue one.


Jim.

On Thu, 13 Oct 2005 10:06:50 +0100, James Egan
transmitted this:

On Thu, 13 Oct 2005 01:35:29 GMT, dylan wrote:

I also had him ping google.com and he received an
"Unknown Host" error, but when I had him ping
216.239.37.99, he received the usual four replies
with no loss.

Then it's clearly a dns problem. This information is usually passed on
to the pc along with it's ip address as part of the dhcp process. You
will need to rebuild the winsock as follows

1. Un-install Dial-Up Networking. Don't reboot.
2. Delete registry key HKLM\System\CurrentControlSet\Services\Winsock2
3. Re-install Dial-Up Networking. Reboot.

I've made notes on all the things I print to check
Winsock first in the future--I posted the whole
story in my previous message in the thread, but
the date on Winsock.dll caused a week worth of
hair pulling. It's all running smooth now, so I
guess my friend'll still talk to me.

dylan

On Thu, 13 Oct 2005 10:25:39 -0700, Gary S.
Terhune transmitted this:

Sorry, I was at the blitzy end of a blitzy day. You're right, of course, but
there are also other issues that could be involved, and this page includes
not only your WINSOCK repair but also other suggestions pertinent to this
issue.
http://www.dslreports.com/faq/1453

Thanks, I'm going to keep this for future
reference.

dylan

On Thu, 13 Oct 2005 10:06:50 +0100, James Egan
transmitted this:

On Thu, 13 Oct 2005 01:35:29 GMT, dylan wrote:

I also had him ping google.com and he received an
"Unknown Host" error, but when I had him ping
216.239.37.99, he received the usual four replies
with no loss.

Then it's clearly a dns problem. This information is usually passed on
to the pc along with it's ip address as part of the dhcp process. You
will need to rebuild the winsock as follows

1. Un-install Dial-Up Networking. Don't reboot.
2. Delete registry key HKLM\System\CurrentControlSet\Services\Winsock2
3. Re-install Dial-Up Networking. Reboot.

I've made notes on all the things I print to check
Winsock first in the future--I posted the whole
story in my previous message in the thread, but
the date on Winsock.dll caused a week worth of
hair pulling. It's all running smooth now, so I
guess my friend'll still talk to me.

dylan

On Thu, 13 Oct 2005 10:25:39 -0700, Gary S.
Terhune transmitted this:

Sorry, I was at the blitzy end of a blitzy day. You're right, of course, but
there are also other issues that could be involved, and this page includes
not only your WINSOCK repair but also other suggestions pertinent to this
issue.
http://www.dslreports.com/faq/1453

Thanks, I'm going to keep this for future
reference.

dylan

On Wed, 12 Oct 2005 18:54:58 -0700, Gary S.
Terhune transmitted this:

Sorry, I'm getting blitzy today. I *thought* there was another machine
involved but in my re-reading, I missed that.

It's okay, after a week of this, we were both
pretty blitzy, too.

Turned out it was a damaged Winsock.dll and all
the uninstalling and re-installing didn't fix it,
because any time we reinstalled Winsock, Windows
would tell us the file being replaced was newer,
so we'd keep it. Eventually we got to renaming
the Winsock files and saw the date on the DLL was
10/7/05--the day we did the upgrade.

Thanks for all your help, his network
configuration is much cleaner now, had we gone
straight to Winsock, we wouldn't have gotten that
done.

dylan