Forum Home
Press F1
Thread ID: 49974	2004-10-06 06:29:00	Modem will connect, but no intarweb!	Jamezo (1062)	Press F1

Post ID	Timestamp	Content	User
278630	2004-10-06 06:29:00	After reinstalling Win98 on an old gateway ages ago, I finally got around to setting up the modem, which did not set up properly using generic drivers, or the drivers found on the gateway restore CD. As it transpires, when searching for the new hardware, it appears as a 'PCI Communication Device' , and then it will install just fine from the drivers I got from driverguide.com. I set up the connection to Paradise ok, and it connects just fine, but it does not seem to send or receive anything, aside from the starting little spiel (which can be anywhere between 500 and 3000 bytes sent). No WWW, no email. I have tried adjusting the FIFO buffers (should I turn it off?), to no avail, I tried unplugging the sound cable (as it was making dial-up noise through the computer speakers even when the volume was set to off, it was worth a shot) The branding on the modem and the driver I downloaded for it identifies it as a Telepath Winmodem.	Jamezo (1062)
278631	2004-10-06 06:35:00	PS. it is installed on COM2, but before while trying to install it, I removed COM2 to see if would auto-detect the port when there was a device connected to it, as it has done with other modems I have installed. I cannot reinstall it right now, as I lack the Win98 cd. I am not sure if this should affect it, as if anything it sems to me as this would stop the modem connecting entirely. Under the Modem->Diagnostics panel, it queries the modem succesfully on COM2. might I only need to install this if I wanted to use the physical COM port?	Jamezo (1062)
278632	2004-10-06 06:41:00	sounds like it a problem with the TCP/IP setup. have you got TCP/IP enabled on the connection??	robsonde (120)
278633	2004-10-06 22:01:00	Could be a Winsock2 problem Download W2fix from here (www.bu.edu) and follow the instuctions on the page.	Davesdad (923)
278634	2004-10-06 23:47:00	I had the same problem with an old PC. I ended up ripping out the old ISA modem and chucking in a new $20 56K PCI modem - no problems after that.	HadO (796)
278635	2004-10-07 05:10:00	> The branding on the modem and the driver I downloaded > for it identifies it as a Telepath Winmodem. theres your problem, many people have problems with winmodems. do you have a firewall like zonealarm? it could be a setting or so try that fix from the link provided above or just get a 56k pci modem for a few bucks :D	Prescott (11)
278636	2004-10-07 05:22:00	I ran that program, it reinstalled DUN okay, (but I had to fetch a DLL elsewhere for it, as I didn't have the win98 cd!) still no improvement, I tried pinging paradise's homepage with no response. if it matters, I took off the 'TCP/IP -> dial up adapter' binding to 'client for microsoft networks'. should that matter? TCP/IP is still bound to the dial up adapter. no firewall installed. eek!	Jamezo (1062)
278637	2004-10-07 05:27:00	Most of the internal modems nowdays are Winmodems... It may be worth having a look at the markings on the chip of the modem and getting a driver that will work with that chipset instead - I have done that before with problematic modems and it works a dream!	wintertide (1306)
278638	2004-10-07 05:42:00	If i remember 9X right..... you go into the propertyies of the conection and go to one of the tabs and you get to select which protocals are used over the conection, make sure that TCP/IP is the only one ticked.	robsonde (120)
278639	2004-10-07 08:32:00	only TCP/IP is bound to the dial up adapter. I tried using a driver provided by the supposed chipset manufacturer, US robotics, I wasn't sure what model I should select, so I used the only one identified as a 56k. After restarting dutifully, it didn't work (it wouldn't even get a response from the modem) I am trying some various drivers from Lucent (who seem to be the real chipset manufacturers) and Gateway now	Jamezo (1062)
1 2