Printable View
Yet another tip.
In your Dial Up Adapter properties, look under the Bindings tab to make sure only TCP/IP is bound to it.
Remove any instances of NetBEUI, IPX/SPX and the like - and also remove them from the Server Types tab in your DUN properties.
------------------
https://forums.windrivers.com/ "Expect the unexpected"
------------------
What a pain to give some help. Had to register and both of my favorite usernames are already taken. Anyway:
Kind of glanced over the other replies but here's a couple of things that might help. Hopefully I'm not repeating anything already said.
One ISP here will not connect with Microsoft Family Logon installed. Don't know why, but installed, no connection. Removed Family Logon (nothing else) and it connects fine. Check to see if Microsoft Family Logon is installed in the Network Properties.
Another thing I've noticed with Norton, when you install it, it automatically sets itself to NOT check ALL files. Many of the new virus types (ie Kak worm) will not even be detected with this setting. When running a scan, I always go into Options and set Manual Scan options to all files and to conserve time not compressed files. If you find a virus, you may want to go back and do compressed files too, but with this option off it'll save you a ton of scan time. 'Sides, if the files are compressed, they aren't doing anything. Not too sure if the default settings with Norton even scan Winsock.dll.
I think you should focus on the networking and duns stack - This I think is also the Microsoft Family logon issue posted above.
I would blow away ALL network settings, close and let windows apply the files changes bu DO NOT reboot. Go back into network properties and re-add everything again. Whern you close out it will rebuild all files. Had this happen a ton of times with remote users. The next trick is to uninstall and reinstall duns from the add-remove windows componoents (like previously brought up). You should also post back here to let the other techs know what worked
------------------
them -... when I click on this it crashes.
me - OK, reboot and let's troublesho...
them - ...see, it did it again... me - sigh
After trying all of the above suggestions, I blew away windows. Tried installing it from the win98 directory (I did a deltree), and it still didn't help. Thought maybe the cab files were corrupt, so I ran setup from the CD and same thing.
Finally I contacted my friend FDISK, and he came over to help me out. I am also doing a low level format on the drive to make sure everything IS toast.
Will let you all know if that helps. Meanwhile, if you guys come up with something else, please post it here since I did make a backup before killing windows.
Thanks for all those who took the time to help me out.
------------------
Proud Member of the Windrivers Team :D
A simple fix may be just to use
+MS=v34 in the modem settings to slow the modem down to V34. I've seen this a lot on the cheaper (HP & Compaq modems). If it says dialing for several seconds after the handshake ends and stops or gets to verifying username and password, stops for several seconds then disconnects.....Try it.
Hope this might help.... https://forums.windrivers.com/
------------------
If walking is so good for you, then why does my mailman look like Jabba The Hut?
Check the encryption on your password if you are dialing into a unix server
regards and best of luck
throw some different memory in it.
------------------
"no eternal reward will forgive us now for wasting the dawn"
I've had some luck resolving DUN problems by completely removing the TCP/IP stack.
Error Message Occurs When You Run WINIPCFG at Microsoft Knowledge Base shows how to completely remove TCP/IP settings (registry included).
------------------
"Expect the unexpected" https://forums.windrivers.com/
------------------
Quote:
<font face="Tahoma, Arial, Helvetica, Verdana, Geneva" size="2">Originally posted by Vette2000:
A simple fix may be just to use
+MS=v34 in the modem settings to slow the modem down to V34. I've seen this a lot on the cheaper (HP & Compaq modems). If it says dialing for several seconds after the handshake ends and stops or gets to verifying username and password, stops for several seconds then disconnects.....Try it.
Hope this might help.... https://forums.windrivers.com/
</font>
Bet that's the fix, usd it before also
------------------
them -"When I click on this it crashes."
me - "OK, reboot and let's troublesho...
them - ... see, it did it again."
me - <sigh>