This is a question for all of the networking experts here - I have tried everything I know and am completely out of ideas.
My office computer ( ASUS mobo P-III 750 MHz 256 MByte RAM running Win98SE ) used to access the internet over our company DSL connection through a simple 8-port router. It wasn't wonderful performance but it worled.
Last May we moved into another building, where we couldn't get DSL or Cable BB, so I didn't notice any problems at first ( having no internet access ). We eventually set up one computer as a gateway with a dial-up modem, and a Linksys switch. Suddenly I found I couldn't access the net - various network utility software is giving error messages that Windows can't create a TCP socket connection.
Now, understand that the network works fine internally - I can access all of the other computers & printers in the building. I can do PINGs and tracerts to off-site computers through the gateway computer & modem and get perfectly good results but I can't do anything through the browser because of the socket problem.
I can't even access the internal TCP server in the Linksys switch - which normally is used for programming the device - I simply get the "can't connect" error message.
Now - I have removed networking & the 3-Com network card - reinstalled windows and then reinstalled the network card. No results - same problem. I tried removing the card and replacing the 3-Com with a Linksys NIC and the Linksys drivers. Same problem. All told I have reconfigured the system about 4 different ways - always with the same results.
I am coming to the point where I may have to fdisk and do a complete reinstallation of everything, but I really don't want to so that as there are a bunch of programs on the HD for which I no longer have the install CDs and I don't want to lose them.
Anybody see this before ? Any ideas as to what I can try next?
Any help greatfully accepted.
Roy
Error creating Socket !!!! ?????
-
YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Assuming all other computers on the network, if any, can connect and browse the internet fine?
Some thoughts, as I don't know what your new sharing software is, but I'm sure you've run through the Internet Connection Setup to tell it the new means of getting to the internet. Can you download (from another computer or CD) and install a newer version of Internet Exploader, such as 5.5 sp2. I'd stay away from putting 6 on a 9X box, officially MS said a small percentage of users can have problems and doesn't support it on 9X, as 6.0 is really meant for 2K and XP.
No old DNS settings leftover in TCP properties from your old building setup? Have you tried manually entering your new ISP's DNS servers instead? I'm leaning this way, towards a DNS problem, because you have internet connectivity (proved by your ability to ping internet IP's), yet you cannot resolve by name. To test this again, try going to the prompt, and pinging http://www.yahoo.com and see what the results are. If it cannot reply, yet you can ping 64.58.76.222 with replies (which is http://www.yahoo.com for today) then it's probably a DNS issue.
One last thought, do you have a new anti-virus program installed, with the latest updates? The quite popular KAK HTA virus family was good at hosing Wsock32 on 9X machines, creating the same symptoms.
Some thoughts, as I don't know what your new sharing software is, but I'm sure you've run through the Internet Connection Setup to tell it the new means of getting to the internet. Can you download (from another computer or CD) and install a newer version of Internet Exploader, such as 5.5 sp2. I'd stay away from putting 6 on a 9X box, officially MS said a small percentage of users can have problems and doesn't support it on 9X, as 6.0 is really meant for 2K and XP.
No old DNS settings leftover in TCP properties from your old building setup? Have you tried manually entering your new ISP's DNS servers instead? I'm leaning this way, towards a DNS problem, because you have internet connectivity (proved by your ability to ping internet IP's), yet you cannot resolve by name. To test this again, try going to the prompt, and pinging http://www.yahoo.com and see what the results are. If it cannot reply, yet you can ping 64.58.76.222 with replies (which is http://www.yahoo.com for today) then it's probably a DNS issue.
One last thought, do you have a new anti-virus program installed, with the latest updates? The quite popular KAK HTA virus family was good at hosing Wsock32 on 9X machines, creating the same symptoms.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
to : YeOldeStoneCat
OK - interesting idea, but no cigar.
I can not connect by IP address either, so I don't see DNS as the culprit. As I said, the Linksys switch has an internal TCP server which allows you access to its setups and results - I can't get to that either.
I have a copy of NetLab - if I try to CONNECT to anything using TCP I get the socket creation error message "unable to create socket". Pings work - tracert works , but they are running below TCP on the stack, so I don't see how to fix it. Yes, I downloaded a new install of IE 5.5 - same thing exactly.
Actually, it looks as though the TCP/IP stack is trashed, but re-installing everything related to it ( NIC software & IE ) doesn't fix it. That kind of suggests to me that something has been seriously corrupted in the registry - which kills my fixes as fast as I install them. Now the KAK virus possibility - that is interesting. My Norton virus scanner files are about a year out of date --- I guess I better spring for the update again.
Roy
I can not connect by IP address either, so I don't see DNS as the culprit. As I said, the Linksys switch has an internal TCP server which allows you access to its setups and results - I can't get to that either.
I have a copy of NetLab - if I try to CONNECT to anything using TCP I get the socket creation error message "unable to create socket". Pings work - tracert works , but they are running below TCP on the stack, so I don't see how to fix it. Yes, I downloaded a new install of IE 5.5 - same thing exactly.
Actually, it looks as though the TCP/IP stack is trashed, but re-installing everything related to it ( NIC software & IE ) doesn't fix it. That kind of suggests to me that something has been seriously corrupted in the registry - which kills my fixes as fast as I install them. Now the KAK virus possibility - that is interesting. My Norton virus scanner files are about a year out of date --- I guess I better spring for the update again.
Roy
-
Boston_Bob
- Member
- Posts: 82
- Joined: Tue Jul 31, 2001 2:41 pm
- Location: Boston MA
i work for my university's computer help desk, we have been seeing things like this lately with some users. especially that "cant create socket" error. the main cause for us has been advertising/spyware software. they tend to corrupt windows TCP/IP stack when more than one are installed. they come along with file sharing programs and other software. i know you said this was a work machine and that you had reinstalled windows so this probably isnt your case but i thought i might suggest it anyway. a neat tool to get rid of them can be found at http://www.lavasoftusa.com .
hope you figure it out
hope you figure it out
me fail english?....that's unpossible!
-
YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Hmmm, I took " I can do PINGs and tracerts to off-site computers through the gateway computer & modem and get perfectly good results " to mean you were pinging public IP's fine.
Sometimes downloading Windows updates related to TCP can help "cure" problems. This worked a lot for me with Win95 with the DUN1.3 update, and once or twice with Win98's DUN1.4 update which you can find here:
http://www.microsoft.com/downloads/rele ... ordinal=99
Only 471 kb.
You mention the Linksys switch...are you using the router with built in switch that you once used from your old location for broadband? Is it still running DHCP and handing out static specified information leftover from your old LAN to your new LAN, conflicting with your new proxy setup? Can you take this Linksys to some other "healthy" computer, and access it's web admin page, just to verify these settings, perhaps it's DHCP is still handing out info which conflict with your new setup.
Sometimes downloading Windows updates related to TCP can help "cure" problems. This worked a lot for me with Win95 with the DUN1.3 update, and once or twice with Win98's DUN1.4 update which you can find here:
http://www.microsoft.com/downloads/rele ... ordinal=99
Only 471 kb.
You mention the Linksys switch...are you using the router with built in switch that you once used from your old location for broadband? Is it still running DHCP and handing out static specified information leftover from your old LAN to your new LAN, conflicting with your new proxy setup? Can you take this Linksys to some other "healthy" computer, and access it's web admin page, just to verify these settings, perhaps it's DHCP is still handing out info which conflict with your new setup.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
yo: YeOldeStoneCat
In no particular order -
The LinkSys is one of the 8-port Switches - I can look at its http page from any of the other computers. In any case, we reconfigured it so IT is a DHCP client and we all have FIXED IP addresses - the Inet sharing on th eWin98SE machine which is serving as or gateway to the dialup required it that way.
As for the Win updates - I have most of them up to date, but I will have to check tomorrow to see if there is anything else. Of course, there is a bit of a problem there, because the Win update site wants to download the software & install it. Can't do that is this case, so I will have to try downloading to another computer & doing the install over the network.
Roy
The LinkSys is one of the 8-port Switches - I can look at its http page from any of the other computers. In any case, we reconfigured it so IT is a DHCP client and we all have FIXED IP addresses - the Inet sharing on th eWin98SE machine which is serving as or gateway to the dialup required it that way.
As for the Win updates - I have most of them up to date, but I will have to check tomorrow to see if there is anything else. Of course, there is a bit of a problem there, because the Win update site wants to download the software & install it. Can't do that is this case, so I will have to try downloading to another computer & doing the install over the network.
Roy
to: Boston_Bob
Greetings:
That's an interesting idea. I have the Lavasoft program here (home) and it found 49 of the little b....s. I'll have to take it into work and run it there - can't hurt to try.
Although, I have to say that if 49 of them didn't cause the problem HERE it's a stretch to think it would do it at work. Of course, it could be one specific beastie, or a special combination.
I'll give it a try.
Roy
That's an interesting idea. I have the Lavasoft program here (home) and it found 49 of the little b....s. I'll have to take it into work and run it there - can't hurt to try.
Although, I have to say that if 49 of them didn't cause the problem HERE it's a stretch to think it would do it at work. Of course, it could be one specific beastie, or a special combination.
I'll give it a try.
Roy
TO: zxc47
Interesting handle you have there.
Anyway - I'm not certain what you meant there - about removing
those lines and putting them back exactly as they were.
I am familiar with regedit, and to some extent with the registry - could you please give me a KEY location to look for, as I don't know where to find the lines you mention.
Thanks - Roy
Anyway - I'm not certain what you meant there - about removing
those lines and putting them back exactly as they were.
I am familiar with regedit, and to some extent with the registry - could you please give me a KEY location to look for, as I don't know where to find the lines you mention.
Thanks - Roy
-
YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Wow, you're still chasing this down, huh?
Did you get a chance to try the DUN1.4 update? I just ran into a similar problem where that helped me cure it again.
What I meant by the switch/router question was....in your old location, I'm not sure on how you had the router setup. The "switch" that you are using now, am I correct is assuming you mean the switch that is built into the Linksys Etherfast Cable/DSL router? Can you take one computer, jot down it's IP settings, then change them static IP, to "Obtain Auto", disable WINS, remove current gateway, remove current DNS, and log back into the Linksys routers web admin page? I'm curious if you have some static WAN info in your router, which it's DHCP service is trying to hand out, and conflicting with any info on your new setup. I'd write down the LAN info of the router, so you know it's IP scope (default is 192.168.1.XXX, with the router at .1), then turn off it's DHCP service. Only drawback from this, is you have to remember you turned it off, and if you ever want to log back onto it again, you'll need to setup a computer with a static IP in the scope, say 192.168.1.2, so as to log back onto the routers web admin page again.
Did you get a chance to try the DUN1.4 update? I just ran into a similar problem where that helped me cure it again.
What I meant by the switch/router question was....in your old location, I'm not sure on how you had the router setup. The "switch" that you are using now, am I correct is assuming you mean the switch that is built into the Linksys Etherfast Cable/DSL router? Can you take one computer, jot down it's IP settings, then change them static IP, to "Obtain Auto", disable WINS, remove current gateway, remove current DNS, and log back into the Linksys routers web admin page? I'm curious if you have some static WAN info in your router, which it's DHCP service is trying to hand out, and conflicting with any info on your new setup. I'd write down the LAN info of the router, so you know it's IP scope (default is 192.168.1.XXX, with the router at .1), then turn off it's DHCP service. Only drawback from this, is you have to remember you turned it off, and if you ever want to log back onto it again, you'll need to setup a computer with a static IP in the scope, say 192.168.1.2, so as to log back onto the routers web admin page again.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
too RGromlich
go to run ,type in regedit, when it open at the top next to file click on edit, on the drop down , click on find< type in winsock.( it will find winstock line for you)
remove the two line . and type them back just like they were,do not copy and paste back in .then reboot your system.and cut the power off to you modem (unplug it.)when the system is back up go to run and type in winipcfg . plug the modem back in and give it time to reset then releast all and renew all
that should fix it
I hope this help you
go to run ,type in regedit, when it open at the top next to file click on edit, on the drop down , click on find< type in winsock.( it will find winstock line for you)
remove the two line . and type them back just like they were,do not copy and paste back in .then reboot your system.and cut the power off to you modem (unplug it.)when the system is back up go to run and type in winipcfg . plug the modem back in and give it time to reset then releast all and renew all
that should fix it
I hope this help you
TO: YeOldeStonecat
I have been "chasing" this problem for 5 months now, and nothing I or anyone else has tried has worked. I am really close to fdisk, but I just don't want to lose all of the installed programs which I no longer have installation disks for. Oh Well . . . . . .
The "old" router was a domestic firewall box, the name of which I don't know, which was on a DSL line. It did NAT and had five ports on it. We no longer have it . That box acted as a DHCP server and handed out IP addresses, although we also had it set up at one time with fixed IP addresses.
In this building we do not have DSL or a cable modem, so we have a dial-up through a V90 modem. One computer is acting as a server (Internet connection sharing) - handling the dial-up and sharing it on the network.
The LinkSys has been set up so that all of our workstations use FIXED IP addresses ( no DHCP ). The only protocol installed and bound on ANY of the workstations is TCP/IP. Other workstations can access the LinkSys seup page ( @ 192.168,0,2 ) mine can not - I get the "can not be displayed" nessage. So this problem does not involve interaction with the LinkSys or connection sharing software - I can't do anything requiring a browser.
Note that I can PING any WS on my site, or any off-site IP address with normal results. But WinSock appears to be inoperative, and I can't find a reason for it. Refering to the message above from "zxc47" - I have four different instances of WinSock in the registry, and none of them look like his description, so I don't really know how to proceed.
When I get a chance I will look for the DUN1.4 update and try it.
ROY
The "old" router was a domestic firewall box, the name of which I don't know, which was on a DSL line. It did NAT and had five ports on it. We no longer have it . That box acted as a DHCP server and handed out IP addresses, although we also had it set up at one time with fixed IP addresses.
In this building we do not have DSL or a cable modem, so we have a dial-up through a V90 modem. One computer is acting as a server (Internet connection sharing) - handling the dial-up and sharing it on the network.
The LinkSys has been set up so that all of our workstations use FIXED IP addresses ( no DHCP ). The only protocol installed and bound on ANY of the workstations is TCP/IP. Other workstations can access the LinkSys seup page ( @ 192.168,0,2 ) mine can not - I get the "can not be displayed" nessage. So this problem does not involve interaction with the LinkSys or connection sharing software - I can't do anything requiring a browser.
Note that I can PING any WS on my site, or any off-site IP address with normal results. But WinSock appears to be inoperative, and I can't find a reason for it. Refering to the message above from "zxc47" - I have four different instances of WinSock in the registry, and none of them look like his description, so I don't really know how to proceed.
When I get a chance I will look for the DUN1.4 update and try it.
ROY
-
YeOldeStonecat
- SG VIP
- Posts: 51171
- Joined: Mon Jan 15, 2001 12:00 pm
- Location: Somewhere along the shoreline in New England
Give the DUN1.4 a try, it's under 500k, so you can download it somewhere else to a floppy.
I realize you had DSL at the old site, and I realize you have dial up at this new site. What I'm still not clear about, is you mention a "Linksys switch", and in the same sentence, "access the Linksys setup page". As far as I know, there are no plain Linksys switches which have a setup page, I only know of Linksys routers which have a setup page, and in my head, I'm picturing you using the old Linksys router just as a switch....not using it's WAN port and routing features. Just to clear this up, what is the model number of the Linksys?
Is there an expendible workstation to try? Running Windows setup over on top of itself (which "usually" keeps all programs fine). You can boot from a DOS floppy, copy the Windows directory to Winbak or something like that, then run Windows setup over on top of itself....if it's too hosed, you can copy the winbak directory back on top of itself. Or if you have a disk imaging system like Ghost or PQDI to create a backup image.
5 months...man, I'd be ripping what's left of my hair out.
I realize you had DSL at the old site, and I realize you have dial up at this new site. What I'm still not clear about, is you mention a "Linksys switch", and in the same sentence, "access the Linksys setup page". As far as I know, there are no plain Linksys switches which have a setup page, I only know of Linksys routers which have a setup page, and in my head, I'm picturing you using the old Linksys router just as a switch....not using it's WAN port and routing features. Just to clear this up, what is the model number of the Linksys?
Is there an expendible workstation to try? Running Windows setup over on top of itself (which "usually" keeps all programs fine). You can boot from a DOS floppy, copy the Windows directory to Winbak or something like that, then run Windows setup over on top of itself....if it's too hosed, you can copy the winbak directory back on top of itself. Or if you have a disk imaging system like Ghost or PQDI to create a backup image.
5 months...man, I'd be ripping what's left of my hair out.
MORNING WOOD Lumber Company
Guinness for Strength!!!
Guinness for Strength!!!
to: YeOldeStonecat
OK - it is a router, although LinkSys calls it a switch. I'm home at the moment and don't have the model # in front of me, but this thing has 8 ports which are routed/switched. It can act as a DHCP server, it does NAT, it cna do all kinds of other good things and it has a Setup Page ( actually about 5 ) whcih allows you to display and set all of its on-line parameters & defaults. I can get to that page form any of our other computers, but my gives me the "can not be displayed" error.
As for the "expendable workstation" I have tried just about everything except fdisk on MY workstation. I have run Windows setup at least 3 times - from the image stored on my HD, from the network, and from a CD. Nothing!
So, I will go look for DUN 1.4 - it probably can't hurt. As for the 5 months, there are a lot of other WSs around, so I don't really NEED the Inet on my desktop, but it is a pain.
Roy
As for the "expendable workstation" I have tried just about everything except fdisk on MY workstation. I have run Windows setup at least 3 times - from the image stored on my HD, from the network, and from a CD. Nothing!
So, I will go look for DUN 1.4 - it probably can't hurt. As for the 5 months, there are a lot of other WSs around, so I don't really NEED the Inet on my desktop, but it is a pain.
Roy
TO: zxc47
Mine system is running Win98 2nd Ed. , and the registry sure doesn't look like that.
When I do the search on WinSock I get about 12 different hits - two of them are exact duplicates, including the entire hive they are located in.. The others have various references to WinSock 1, WinSock 2, but no winsock32.
So I don't know - thanks for the info but it doesn't appear to apply. OR - my system is even more s.....d up thenI thought.
Roy
When I do the search on WinSock I get about 12 different hits - two of them are exact duplicates, including the entire hive they are located in.. The others have various references to WinSock 1, WinSock 2, but no winsock32.
So I don't know - thanks for the info but it doesn't appear to apply. OR - my system is even more s.....d up thenI thought.
Roy
-
Kip Patterson
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
to: Kip Patterson
OK - I'm at home now, but I'll give that a try next week.
Roy
Roy