Unable to create a network socket connection

[lapatona]

Running ME with Netscape 4.79 and cannot log onto the internet. Keep getting message "Netscape cannot create a network socket connect...." IE won't find the net either - "can't find page" error is returned. I can ping just fine and I can see other computers on the network, just can't get to the internet. This is a home network and not blocking anyone out.

 

[Guest_imported]

Hey,

I have the same problem! did u manage to fix it?
If so, wld u b kind enuff so as to tell me ??

Thanks

 

[Guest_imported]

Hey,

I have the same problem! did u manage to fix it?
If so, wld u b kind enuff so as to tell me ??

Thanks

 

[Guest_imported]

Your problem sounds like it's being caused by a corrupted registry entry.

In Windows 98, you can try this...

1. Make a backup copy of your registry.
2. Then navigate to H_key_Local_Machine, System, Current Control Set, Services.
3. Delete the Winsock2 folder.
4. Then uninstall dial-up networking and re-install it.

The re-install will recreate the Winsock2 entries in the registry, and you should be back in business.

Very important----> ALWAYS make a backup of your registry before fooling with it, so if something doesn't work as planned you can recover.

 

[Guest_imported]

Your problem sounds like it's being caused by a corrupted registry entry.

In Windows 98, you can try this...

1. Make a backup copy of your registry.
2. Then navigate to H_key_Local_Machine, System, Current Control Set, Services.
3. Delete the Winsock2 folder.
4. Then uninstall dial-up networking and re-install it.

The re-install will recreate the Winsock2 entries in the registry, and you should be back in business.

Very important----> ALWAYS make a backup of your registry before fooling with it, so if something doesn't work as planned you can recover.

 

[GOLIAT]

Hi!
I think I have a simular problem.
I get the same error msgs when connecting to the Internet via internal modem.
The difference is though that I cant ping either ( and I use win 95).
I tried bjoedeman's solution, but it didnt work.

 

[GOLIAT]

Hi!
I think I have a simular problem.
I get the same error msgs when connecting to the Internet via internal modem.
The difference is though that I cant ping either ( and I use win 95).
I tried bjoedeman's solution, but it didnt work.

 

[GOLIAT]

Hi!
I think I have a simular problem.
I get the same error msgs when connecting to the Internet via internal modem.
The difference is though that I cant ping either ( and I use win 95).
I tried bjoedeman's solution, but it didnt work.

 

[Guest_imported]

You saved me a lot of head ache. Your solution worked for me. Thank you very much.

 

[Guest_imported]

To bjoedeman...THANK YOU VERY MUCH FOR THE HELP. I've spent two days in trying to solve this problem. Now, problem solved...LIVE LONG and PROSPER...MAY THE FORCE BE WITH YOU.

 

[SOD]

Fixed a problem I was having with IE, Netscape, and a Lan connection. THANKS!

 

[tonypt]

My friend keeps getting an unable to create a network socket connection in Netscape 4.5 and also can't get on the internet via IE 5.5 SP1 either. The solution below sounds good, but how do I reinstall the dialup and in 98 how do I make a registry backup?

THanks. TOny tonypt@hotmail.com



Your problem sounds like it's being caused by a corrupted registry entry.

In Windows 98, you can try this...

1. Make a backup copy of your registry.
2. Then navigate to H_key_Local_Machine, System, Current Control Set, Services.
3. Delete the Winsock2 folder.
4. Then uninstall dial-up networking and re-install it.

The re-install will recreate the Winsock2 entries in the registry, and you should be back in business.

Very important----> ALWAYS make a backup of your registry before fooling with it, so if something doesn't work as planned you can recover.

 

[Guest_imported]

the tip worked great
thanks

 

[jringer]

Amazing!!!!! It really worked. Was trying for 2 days to resolve. Thanks

 

[ramonrojos]

I was trying to move file sharing from TCP-IP to NETBUI. Couldn't make the switch. Got the file shares working again under TCP-IP, and lost the socket connections on both machines. No browsers, no ftp, nothing! After three hour of frustration, I searched and found this tip. It worked!

Unfortunately, then network neighborhood died on one PC. It couldn't read or map any drives, but other PC's could map it and see it. Go figure. Must have been something with the login. I ended up fdisking it and reloading the OS. What a pain.

 

[buddyismydog]

Thank you for this web site and those of you who offered the fix for the socket connection error. I have messed with this dumb thing for two days and found this web site and I am back in business. Thanks soooooo much!