tcp/ip screwed up bad
Steg
tcp/ip is severly damanged. Reinstalls, and all manner of fixeshave
not worked. I tried removing everything in Network settings. I tried
compeltely removing dial-up networking and tcp/ip per microsofts
knowledge base. I can ping places when I connect to the internet (or
any ppp for that matter) with thier numeric ip address. But web
surfing doesn't work nor any kind of telnet (numeric or dns). I have
spent all day working on this problem. any help would be appreciated.
---------
My e-mail is batsteg at yahoo.com
______________________________________________________________________
Posted Via Uncensored-News.Com - Still Only $9.95 - http://www.uncensored-news.com
With Servers In California, Texas And Virginia - The Worlds Uncensored News Source
Steg
my problem exactly. My last nic card was a 3com. It seems alot of
people have this problem but no solution
bean beanyland" <be...@nyc.rr.com> wrote in message
news:DD8C7CE3FFD94B4283A804C7D7B61FB6766BE9@CPMSFTMSGV22...
> In some cases on a windows 95 and 98 when i install a 3com network
card
> and try and connect to the internet the computers do not resolve
dns to
> ips. If i ping a ip address i will get a respones. But if i type
in
> the domain name www.yahoo.com it will not respond. I have
reinstall
> many componets (tcp/ip, winsock, dun). Does anyone have any way to
fix
> this without reinstalling the OS. I have spent hours on the phone
with
> 3com and with Microsft but know one has the answer.
Steg
this "solution" that I will try tomorrow:
This reply is wordy because I am including a lot of terms in this
solution post to get some good indexing in
Deja.com, where I ultimately found the solution.
I had the same problem and finally found a solution. A week ago, I
installed a new lan card (RealTek
compatible 8029) and after, it caused problems with TCP/IP Sockets.
Some things worked (ping) and some
did not (ftp localhost returned a 10047 (WSAEAFNOSUPPORT) or
sometimes a 10044
(WSAESOCKTNOTSUPPORT). Other utilities reported various errors
relating to being unable to open a
socket or that TCP/IP was not installed.
Dial-up connections worked - I was able to connect to the Internet
but not able to surf or use the other Internet
apps (email, agent, etc).
The Microsoft Knowledgebase (http://support.microsoft.com) mentioned
similar problems but no resolution
that solved the problem (uninstall TCP/IP and Dial-up Networking then
re-installing them). Reinstall of Win98
(Win98SE in my case) also did not cure the problem. Comparing files
with a working system and replacing
them did not cure the
problem. I assumed the problem was registry-related.
I had another partition with Win2000 RC2 and it worked fine, that's
how I was able to connect to the Internec
and finally find the solution in Deja.com. Unfortunately, Win2000
does not support my SB1000 cable modem,
but that's another story.
The solution is pretty easy and is described below, based on
another's post:
===================
BELOW IS A POSSIBLE RESOLUTION TO THE WINSOCK FAILURE PROBLEM. THE
PROCEDURE IS
DESCRIBED IN ABBREVIATED FORM AT THE BOTTOM OF THIS MESSAGE.
The solution was posted on the microsoft.public.win98.performance
newsgroup under the Subject "DUN
Win98 - Socket connections error." Below is a version of the
instructions, re-numbered to better reflect
discrete steps. If you need more details on performing the procedure,
let me know. Good luck!
Roger T. Imai
Nashville TN
rti...@REMOVEmindspring.com
PROBLEM: INSTALLING WINDOWS 98 SECOND EDITION CAUSES WINDOWS SOCKETS
TO FAIL
Windows 98 2nd Edition installation caused Winsock-TCP/IP to stop
working, disabling Internet-based
communication client software.
The problem may also occur under the original Windows 98 if the "128-
bit Encryption Support for Dialup
Networking 1.3" Update is installed, then subsequently uninstalled
from Control Panel, Add/Remove.
SYMPTOMS
After installing Windows 98 Second Edition, Winsock clients may
report the following errors:
* Internet Explorer 5.0: "Cannot Find Server or DNS Error,"
Outlook 98: "The server could not be found. (Account 'MindSpring Mail
Server', POP3 Server:
'pop.mindspring.com', Error Number 0x800ccc0d)."
* FTP client WS_FTP (if used): "FTP Failed 'createsocket' - address
not supported."
Windows 98 Dialup Networking may connect normally to the ISP
with "Password Authentication Protocol" and "TCP/IP" listed in the
"Connected To..." window under the
Modem icon in the System Tray. Modem Diagnostics and the Modem
Session Log may report no error
conditions.
Other procedures provided by the Windows 98 Troubleshooter Wizards do
not resolve the symptoms.
--------
RESOLUTION
1. Remove DUN from Control Panel, Add/Remove Programs - Windows Setup
tab, click (don't un-check)
Communications then click the Details button and un-check Dial-up
Networking. Click OK to close with
windows.
2 Ignore prompt to Restart
3. Run regedit from the Start->Run box. Delete Winsock and Winsock2
branches from
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
4. Run AUTODIAL.REG (see below). This puts back a few items into the
registry deleted in step 3. Run it by
finding it in explorer and double- clicking it.
5. Restart Windows
6. Reinstall DUN similar to how you removed it in step 1. (you will
be prompted for the Windows 98 CD)
7. Restart Windows
Winsock functions should be restored.
CONTENTS OF AUTODIAL.REG
Create a file called AUTODIAL.REG somewhere with the lines between
the dash lines below.
--------------------------------
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock\Autodial]
"AutodialDllName32"="url.dll"
"AutodialFcnName32"="AutodialHookCallback"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings]
"EnableAutodial"=hex:01,00,00,00
---------------------------------
===================
The procedure described above did solve my problem. One point, I
checked what happened to the registry
when I ran the AUTODIAL.REG and noted that it did not install the
"AutodialDllName32"="url.dll" entry like I
thought it should so I did it manually after running the .REG and
noticing it was missing the key. I am not sure
if it is required. Regedit lets you create keys and values.
Good Luck - I will post this at various places. I would not have been
able to resolve this problem without the
help from others that post solutions on Usenet.
Gary
Sent via Deja.com http://www.deja.com/
Before you buy.
cpichon
wow, I wish I could have found that article a year or so ago. I had
the exact same problem and ended up having to reformat my box.