[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 429
  • Last Modified:

Modem won't stop handshaking

My Windows 98 was dialing up fine to a certain ISP using its internal modem.

Then I added another ISP entry,and the modem won't stop handshaking. It keeps going on "Dialing..." and it never reaches the "Verfiying your username and password..." stage. After a while it just drops the line.

This happens to both my old and new ISP DUN setup.

I tried reinstalling winsock, reinstalling Dial-up Networking and I even reinstalled my Win98 SE!! Still, the situation didn't change.

I've also tried using an external modem instead, and I've also
tried using another phone line. But the problem remains, and DUN keeps handshaking without logging in.

Could anyone enlighten me on this? I could give you a log of my failed dial-up session if you need it.

Thanks
0
jap_e
Asked:
jap_e
  • 7
  • 4
1 Solution
 
jap_eAuthor Commented:
Edited text of question.
0
 
sorgieCommented:
go to control panel and open the network icon. highlite your entries and check all the properties to make sure they are not changed. things such as dns disabled, obtain IP adresss automatically which you will find in the tcp/ip properties.
0
 
jap_eAuthor Commented:
Yup, I've checked all those settings which you've mentioned.  They are NOT changed.
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
femson7Commented:
Never Ending Link Negotiation eh? :))) Like the never ending story. :)))

This is caused by:

Rank #1 - Line Noise. Recheck your premise wirings, your phone extensions etc. Disable call waiting, conference call etc.

Rank #2 - Hardware Protocol incompatibility; eg v90 handshake sequence, x2, k56flex, symbol rates used, phase roll, etc.

Rank #3 - Incorrectly setup modem, modem driver, wait for carrier setting etc.

Rank #4 - This one is rare, a broken modem, eg flash rom got corrupted, or just plain and simple fried modem.

Discussion of each of the above will immediately follow.
0
 
femson7Commented:
#1 LINE NOISE
-----------------

This is the most usual reason for modems not connecting. It accounts for about 90% incident. And it happens w/o warning. Like I am using the modem right now, and then wham! Got disconnected, and my modem won't connect anymore. Coz I didn't know that the wirings got suddenly knawed at by some mice.

Line noise is caused by faulty premise wirings, off-hooked telephone equipments/extensions, dirty RJ11C contacts, old and worn out telephone wirings etc. Anything that will introduce signals other than the carriers themselves is considered noise. Sometimes, it comes from an appliance plugged in, like motorized appliances: aircon, fans, or noise generating appliances or things, like flourescent lights, TVs, amateur radio equipments, etc. For a complete list of interference causing equipments/machineries etc, contact FCC. :))


RESOLUTION
---------------

Check your premise wirings. If all is ok, check for other sources of interferences like the ones I mentioned above. Clean RJ11C wire contacts.

Outside your house, check the telco's line coming into your house.

If everything has been checked, as far as line noise is concerned within your premises, and your premises proximity, call your telco if they are doing some cable maintenance within the same locality or central office (CO). If none, then proceed to the #2
0
 
femson7Commented:
Rank #2 - Hardware Protocol incompatibility; eg v90 handshake sequence, x2, k56flex, symbol rates used, phase roll, etc.

CAUSES
---------

Business rivalry between modem manufactures; Hehe Also caused by buggy implementations of ITU-T standards; Symbol rate confusion;

RESOLUTION
---------------

First disable v90, then if still not working disable x2 or k56flex, if this won't work still, disable V34 or V34+, and use V32 instead. This should work if things are within this level. If not, and the symptoms persisted, please proceed to #3
0
 
femson7Commented:
Rank #3 - Incorrectly setup modem, modem driver, wait for carrier setting etc.

CAUSES
---------

Software glitch. User induced. Outdated INF drivers, connect time set too short, unusual error-correction incompatibility;

RESOLUTION
---------------

To verify if you indeed have a faulty configuration, check your port rates, by:

START button, then SETTINGS, then CONTROL PANEL.
Select the MODEMS applet;
Click on PROPERTIES

On the GENERAL TAB, make sure to select MAXIMUM SPEED of 115200.

Then click on CONNECTIONS TAB of this same window, and check for start stop, and parity bits, it should be 8,none,1;

Now click on ADVANCED button, and put a check on ERROR CONTROL and REQUIRED to connect if they are not checked; uncheck them if they are checked.

Put a check on FLOW CONTROL and choose HARDWARE FLOW CONTROL (RTS/CTS) if they are unchecked; if they are checked, uncheck them.

Put a check on APPEND TO LOG then close by selecting OK on this window and the following window. Close the CONTROL PANEL folder.

Right click on MY COMPUTER icon on your desktop and then PROPERTIES, then goto DEVICE MANAGER tab, and expand the PORTS (COM & LPT) and right click on the port # that your modem is using and then properties.

Goto the PORT SETTINGS TAB, and verify that you have set it the data , stop, and parity bits to 8,none,1; FLOW CONTROL should be HARDWARE. Close by clicking ok and closing the MY COMPUTER properties.

Run a terminal software, like Telix, Procomm, or hyperterminal. If you chose to use hyperterminal, just click cancel when prompted for connection name. This will bring you straight to command mode or terminal mode.

Type AT&F1, followed by enter, even if you can't see it, just type it. And if it returns ERROR, type AT&F then enter.

Now type ATE1, then dial to your ISP, by typing ATDT <ISP telephone number> followed by enter. Wait till you see CONNECT etc/etc/etc/etc message. You won't see the etc, but it will be replaced by the link's protocol and compression protocol if you successfully connect. Once you see it, you were able to properly established that you have a working modem!

Hangup the connection by typing three plus signs. Type each one and pause for half a second between them. (+++) you will see ok, and then type ATH followed by enter.

Now, type AT&W. Note: if you have a dual NVRAM profile modem, (modems with two user setting memory area), use AT&W0 then enter, AT&W1 then enter, and so on.

Type invoke DUN, and bring up the properties for your connection, and configure your modem there. In the EXTRA SETTINGS under the modem configuration within DUN, put ATZ or if you have a dual NVRAM modem, ATZ0 or ATZ1.

Close this window and any other window. Connect to your ISP using this connection entry.

If the same thing happens, proceed to #4
0
 
femson7Commented:
Rank #4 - Broken Modem. Now this one is OUCH!

Causes
--------

Lightning, line surge, static electricity, a retirable modem, poor quality, etc.

Resolution
------------

Pluck the modem out of your PC if it's internal, or disconnect all cables if external, ship back to your modem's manufacturer. Consult your user manual for instructions on how to return modems.

If still under warranty, you're in luck! If not, well, errr, happy holidays my friend. I hope you'll be able to get your system back on.


If after the 3 previous post, have been tried INDIVIDUALLY, combine each one with the other in the list, and if still won't work fine, reject my answer. :))))
0
 
jap_eAuthor Commented:
Solid answer!  This morning after 3 hours of trying everything you mentioned, plus mucking around with the AT command set, I reaslised that the modem responded "error" on the self-test AT&T.

I'm now considering buying a new USB modem instead.

Thanks for your answer.
0
 
femson7Commented:
Have you checked out the pros and cons of USB Modems?
0
 
femson7Commented:
And btw, thank you very much. And Happy Holidays!!
0
 
jap_eAuthor Commented:
I don't know much about USB modems.  What could be bad about them?
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now