Help - win98 internet trouble!!
 

I just changed motherboard,CPU,cabinet on my comp leaving the cards and harddisks the same. After instaslling the drivers for all hardware, windows was running ok, everything functioning, but I cant browse the net.

I have internet access thru a LAN card and also thru dialup on an internal modem. The Lan card shows me the other users on network neighbourhood but when I try to browse the net I get a 'would you like to connect message'. Earlier I just had to open my browser and it would start browsing using the internet on lan. There was no configuration involved as I had done a fresh win install recently and it had functioned without problems.

WHen I dial up using my modem it connect s to the ISP and the connected icon appears on the system tray, but I still cant browse any site, it keeps trying to 'find the site'. I've tested Netscape, Opera, telnet, ftp, outlook express, nothing works . IE5.5 sometimes crashes when I'm trying to browse.

I did a reinstall of windows over trhe old one and the problem persists. I tried deleting and reinstalling IE5.5, same problem persists. I have checked for TCPIP protocol installed on my system and its there.

Any idea what might be the problem? I'm really desparate here, typing from another comp. I need internet fast as I'm losing money eevryday. Any help really appreciated!

Hypo, try checking your connection settings... If using IE, "Tools" menu, "Internet Options", "Connections" tab.. and make sure it's checked to never dial a connection or dial when network connection not present.... and try that first... we'll go from there. http://bbs.gofuckyourself.com/board/wink.gif
Also check your DNS settings to see if they're right.... if they are, try a different DNS server... your regular one could be down or something.

[This message has been edited by Amputate Your Head (edited 08-30-2001).]

Ok Amp (now that's a much better name!), I made it Never Dial a Connection, but that didnt solve it.

Also its not just a LAN error or dialup error, the error seems to eb generalised, so I cant connect to the net using LAN or even when dialed into my isp using my modem.

Plus its not just an IE5.5. error, I cant access the net thru my telnet client, outlook express or ftp client either.

Ok, here's a detailed error I get when using getright or ftp client -


Error creating socket for Network Communication!

Socket Error: Address family not supported by Protocol family


Anyone recognise this? How do I fix this?

Good ol' Microsoft...

Had the exact same problem.. Bought all new hardware.. kept the same HDD.... Reinstalled drivers etc... stupid Win98 wouldn't let me connect to the net.

Solution: bought and installed Win2k Pro. It's really stable and really fast. Never crashed since I got it. I reboot about once a week now =)

hmmm.... it's sounding like a TCP/IP problem... if you can connect through the same line on the LAN with a different machine then your line and everything behind it is clean... so you might try nuking TCP/IP and reinstalling it... my best suggestion other than installing Win2KPro...
something similar to this happened on one of my machines from simply changing the Workgroup... all the sudden nothing worked anymore... had the same exact symtoms you are having, except it was a Win2K machine. All the other machines worked fine except for that one. Ended up reinstalling.

I removed and re-added TCP - problem is still there..
I did find several search results on google for the error but no tips on how to solve it -
http://www.google.com/search?hl=en&safe=off&q=windows+Address+family+not +supported+by+Protocol+family&btnG=Google+Search

Here's some info on the Microsoft site, I dont understand it at all -

http://msdn.microsoft.com/library/de...kmsgs/3133.asp


Error Message:
WINSOCK Error: Address family not supported by protocol family.

Explanation:
An address incompatible with the requested protocol was used. For example, you might not be able to use NS addresses with ARPA Internet protocols. This error occurs with the socket() function, which takes the socket type (protocol) and address family as input parameters. It also occurs with functions that take a socket handle and a sockaddr structure as input parameters. A socket already has a type (a protocol), and each sockaddr structure has an address family field to define its format. A function fails with WSAEAFNOSUPPORT if the address family referenced in sockaddr is not compatible with the referenced socket's protocol.

User Action:
Developer suggestions: Since there is only one corresponding protocol for each of the datagram and datastream socket types in the Internet address family, leave the value in the protocol input parameter as socket(). Alternatively, you could call getprotobyname() or WSAAsyncGetProtoByName() to get the appropriate protocol value from the network system.

Sounds like a problem I had several months ago when I reformatted, couldn't get the ethernet card working, but I had let windows do the plug and play on it. I reinstalled using the software that came with the card and everything was ok. Good luck.

okay, i'm not the smartest person when it comes to this but is it possible that you don't have WINSOCK installed?



------------------
tit,
A revolution in adult content: EROTICOPY

DAMN... now you're telling me that I have to buy Microsoft Socks so Win98 will work right??

No wonder this thing keeps shutting down!

Fuck!

Try this.

It will also take care of your pop up problems on The Hun. ( if your having any )
http://www.apple.com/powermac/expansion.html

hey if your using internet sharing or anything like that be sure you have all the microsoft protocols installed like ipx, netbeui, netbios and all that good stuff

I removed and reinstalled TCP/IP and winsock, but the problem refuses to go. Any other ideas?

I'm going to reinstall windows if nothing works, but that meansd installing a hell lot of software and configuring them again.

If you re-install Windows over the old version you already have it shouldn't affect the software you already have on the system. You DO have to go back to MS and re-install all the patches and updates etc. Thats about the only real headache. (Since MS stuff likes to be patched one at a time to get the best results that is a time thing). Just make sure you go right over the existing windows copy. (A new drive or directory installation WILL disconnect your other software)

But 99.9% of the time, no probs happen with the other progs. This system has had a reinstallation once every 6-8 months for 2 yrs now. Haven't lost one program yet. http://bbs.gofuckyourself.com/board/wink.gif But if you have data files from something really important like Quicken etc, you want to be safe and floppy backup for that. JIC!

Oh and assuming you installed the new drivers and whatnot for the motherboard etc, did you see if CMOS recognized the new MB and chipset/s?