Handshake on Modem but unable to establish connection

http://support.microsoft.com/support.../Q191/4/94.asp (MSDUN13)Also if you run regclean it may possibly screww up your Symantec products,old 3 year old bug I found and Symantec posted.I never did hear what OS it was,but sounds like Win95 or wWin95B (osr2). To verify ,go to my computer and then dialup networking and double click on the ISP attempting to connect too.It probably will work,Install MSDUN13.Also it is good idea to use Microsoft Network for "primary Logon server" and NOT family or windows logon. Also all you need is Microsoft Network,dial up adapter and TCP/IP,all of that other stuff in your case is junk. If you are using Win98/se use DUN40 .Anytime you need to find something and fast I personally use GOOGLE.COM. After you install the new DUN ,use the MS connection wizard to set your setting and in 95/B/C/D/E/F put 0.0.0.0.0 for the IP addressbecause almost every ISP automatically assign now a days.How this helps,if not you may contact me directly if you wish,solving tough dogs I thrive and live for.
[email protected]

Dale P. Baker

Quote:

---

<font face="Tahoma, Arial, Helvetica, Verdana, Geneva" size="2">Originally posted by pm4345:
Hi guys and gals,

Customer called and said modem won't connect. Said fine bring it in. Tried it, does the 'hand shake' but right after trying to verify the username and password, it says can't establish a connection. I tried my password, does the same. I replaced the modem with two different ones, same problem.

Removed all protocols and reinstalled again.
Extracted a new copy of all winsock files and replaced the old ones. Even upgraded IE5 to IE 5.5 but no go. Any suggestions?

</font>

---

I don't think your problem has to do with the IP stack. I think we need to focus on the modem itself. Somewhere in the '98 dialler you should find something which will cause the modem to log what it's doing (I don't have a '98 machine in front of me but I think you'll find a check box called "append to log". This will log all the interactions between the PC and the modem - the init string, the dial string and the responses. The one we're interested in is the "CONNECT" string - the one that TAPI takes as a cue to hand over the com port to the IP stack so that PPP can do its thing.
Now most modem manufacturers (probably at the instigation of MS) set the init string to that modem will say CONNECT or CONNECT + DTE speed the speed of the port to the computer, *not* the speed that the modem trained at. Whether the modem trained with error correction or not is left out also.
Why do we care about all this?
Because the speed of the carrier and whether we trained with error correction (preferably LAPM/ V42bis give us an idea as to how well the the modem trained. If it got a V90 full rate (56000bps) but no error correction, it may be too flakey to pass any useful data - like your PPP logon - without corrupting it.
So my advice - find your modem documentation, look out the string to get extended result codes, put it in the extra init string under advanced properties, and look to see whether it trained at full speed *and with error correction*.
If it looks (from the log) that it's having a hard time maintaining a connection the it's either the line or the modem. If it's the former you'll just have to slow down the speed. Sometimes modems can get training patterns over a line - they just can't make any data move over it.

I had the same problem today on a win95 osr2.5 box. I completely uninstalled dialup networking via the add/remove programs, restarted the pc, reinstalled dialup networking, restarted, tried again. Worked great. Thats only fixed problems like that for me twice. Just thought I would mention it. Good luck. https://forums.windrivers.com/

What does Device Manager show?
Any port or IRQ conflicts?
Also, is the drive still compressed?

This may sound quite dumb, but, humor me. call ISP and see if they have any odd username requirements. Back in the day I had a netcom account and would ony connect if I used the format [email protected] in the username feild of DUN. If I rember correctly I got the same error when it done any other way. Good Luck.

My two cents.Is the user name and password in the connection tab of internet explorer,under settings?And what isp is she using.Some are hard coded,some are given a ip adress automatically.If the modems dialing,it's not the modem.If you have doubt it is the modem,use the diag property in the modem section of the control panel.Check the telephony section while your there.Reinstall the isp in internet explorer in the connection tab under setup.And worse comes to worse,put the cd in and reinstall the os.Good luck

I've seen this happen many times...in fact just the other day... I too tried extracting a new copy of winsock.dll and wsock32.dll and it did not work... Even made sure all other modems and even the .inf files were gone through safe mode (you know ghosting). I knew I'd seen the problem many times before (when Win95 was new) but forgot the solution Doh! Anyway Murphy's law again...last thing to try works...

1) Remove DUN (Control Panel...Add/Remove Programs...Windows Setup...Communications...(uncheck Dial up Networking))

2) Restart Windows

3) Reinstall Dial up Networking then restart again...should do the trick...

If there is a network cable installed, then disable the modem and try again.

Also try re=install client for Microsoft networks if you have not done so already.

------------------
You never Know everything!!!!!

You have of course tried another ISP?

If it dials and squarks, you know for sure it ain't your modem, try connecting via the icon in dialup networking, see what that says is your non correction error, then look it up!

enter safe mode <quick way from windows - restart in dos, then at prompt - c:\windows>win /d:m

remove all evidence of modems, should be a few by now, also look for any serial mouse that may be the cause of the problem even if it shouldn't be installed - had that happen recently.

Check country settings are correct, connection will be much degraded - had that happen too.

You mention using Norton, I'm unclear if it was already installed, get rid of it...I have solved far too many modem connection issues by uninstalling Norton (2000, 2001). This app swamps dial-up connections. I had one customer who refused to allow me to ditch Norton even after several lengthy visits. She relented after the fourth visit, mildly hysterical (so was I, her half dead dog kept sneezing and farting on me). Immediate connection. I installed AVG and left with head held high, smelling like a skunk and covered in fluff.

Telecos have a page in their helpdesk manual that only contain the words `its a hardware fault'...first or second page in.

check out msconfig/startup as well, something may be loading that invokes rnaap.

Beware the Hybris virus too

You might try turning on modem logging and PPP logging, then try connecting, then open the logs and see if it gives you a clue as to why it's not connecting. At least maybe you will be able to refine your search...

In your dialup networking window rightclick on the dun and choose properties. on the modem settings click configure. Click the options tab. Check the box marked "bring up a terminal after dialing". ok everything and dial. This will bring up a terminal after dialing and allow you to log in manually. This may show you some information about the password handshake process you can't see otherwise. If you get nothing but garbage in the terminal then the modem just isn't negotiating with the ISP and I would blame the ISP at that point. There used to be a few ISP's in our area where this was the only way to log in, their password dialog was funky and always refused a login normally.

------------------
What's the differance between 'twisted' and 'torqued' anyways?

simple solution maybe, not alot of work.

Call the ISP. Check on their status. are they having problems, upgrading or such?

maybe already posted.

--------

More coffee any one

who are they trying to connect to ?
maybe a issue with winsock2
AOL messes up winsock2 really bad
this doesn't sound like a modem hardware issue
slow down the modem aswell with an AT command

Get another HDD with just win98SE on it and install the drivers for your clients computer. Try to connect and see if it works. If it does reinstall the OS on original HDD. If not yell at the ISP https://forums.windrivers.com/