Thinkpads Forum

I got a used Thinkpad 600e 2645-4BU. Win 200 pro installed and all IBM drivers installed.

I was able to sign on my ISP dialup account. However the modem made a strange sound towards the end of the link negotiation, different from all other modems. (This is not the problem...)

Anyways, after dialtone, fuzzz, etc ...I got the two monitor icon on the bottom right, it says its connected at 44kps, there were some packets sent and received. However, when I open IE to visit yahoo, msn, or use media player to update, etc... I get the typical no connection screen in the browser.

I query the modem and it's ok.. I went to bios and ran diagnostics and it shows no problem on any hardware aspect (no specific modem test)..

Short of putting a PCMCIA modem that I don't have to test, Any help is appreciated....

Well, there's a problem with the MWave modem that usually manifests itself differently in 2k and XP than you describe. But try downloading and running the following patch (MWregfix.exe - for both the 770 and 600/E):

http://thinkpads.com/ftp_resource.htm

Doesn't sound like the "patch" issue here....That would show up as an inability to find the modem. I think it's a software issue. Go into Internet Explorer's Internet Options (under the Tools tab) and select "Connections." In that window, first click on the tab at the bottom "Lan Settings," and make sure everything is set to "Automatic." Then in the "Connections" window, click on the top called "Setup," and in the next window, select the last option, "LAN," then in the next window, DON'T select connect with a modem, but instead, connect with LAN...continue to the end of this wizard. This way, you will be able to get on the web wether you dial-up or use a network connection. Also, in the "Connection" window, set to "never dial a connection." Everytime you want to go on line you will have to bring up your dial-up connection to dial out, but this is a for sure way for your modem and communication software to really "talk" to each other....

If the above doesn't work, then next, make sure you have TCP/IP set up properly. To do this, right click on "My Network Places" on your desktop and select "properties." In the next window you will see your different connections. Select your ISP connection icon and right click on that and select "properties". In the next window click on the tab at the top labeled "Networking." In the next window you will see a rectangular window in the middle with "File sharing...", "Client for Microsoft Networks," and hopefully "TCP/IP." If you don't have TCP/IP, you can connect to your ISP but won't go anywhere...so, add it with the Install button there. If it's there, or once it's there, highlight it and click on the "properties" tab. Make sure that both obtain IP Address and DNS are set to Automatically detect in this next window. Now, make sure to click the "OK" button (This is very important...without it, you've not made any changes) and close out ("X" at top right corner) your ISP's "properties" and try to dial-up again. I hope you get connected now!

Edited: As an after thought, also make sure your ISP connection is set to use the modem in the laptop if that's what you are using. Are you using the internal modem or did you also install a pc card modem? To do this, go to the properties of your ISP connection (as outlined in paragraph 2, above", but instead of clicking on "networking," in the first window, you will see "Connecting using:" and in a slim rectangular window, the name of the modem being used to connect. Make sure this is the modem that you are using. Change it if it's not...and once again, make sure you click "Okay" before you "x out" of "properties" of your ISP connection. Guess that's all.

The link to the mwregfix.exe is dead and I can't seem to find it available at any of the links when I do a google search. Is there anyone that still has a link to the file that is alive? Any help is greatly appreciated.....

Even though I didn't need it, I just tried the link for mwregfix.exe posted by sktn77a. It downloaded just fine. Perhaps the connection was down for a bit.