• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Modem connects to ISP but does not do anything?

G

gtd2000

Platinum Member
I use an ASDL connection but I also have my 56K modem connection - recently I can connect to the server (with 56K modem) but can't browse or receive/send e-mail - is this a protocol problem or soemthing???
I've tried all the various access numbers and have no conflicts etc...
ASDL connection is fine..
 
Basically it connects to the ISP - I get about 2oo to 300kb of info when it connects - then it all stops - web pages do not load - no sign of any activity or green flashing modem lights in the system tray
could it be something to do with having my LAN card as the main type of connection?
 
This happens a few times to me too. Usually I reboot the system and sometimes it goes away. Are you using a winmodem by the way? I'm using one and I'm guessing that the winmodems have problems with some of the software part.
 
Hmm, might have something to do with TCP/IP and the NIC. Get connected, then go to Start->Run, and type winipcfg (short for WINdows IP ConFiGuration).

Select the PPP Adaptor and see if you're getting assigned an IP address. You should also check your DNS settings for that adaptor as well.

Having the settings for OE and IE set to LAN just means that those apps are going to assume that you're connected and not attempt to establish a connection for you. Shouldn't be a problem.
 
Go into dun and choose the properties of that connection then try disabling log onto network. You may need a flash or driver update too.
 
I agree with compuwiz, it sounds like your comp is trying to log onto the networks, me roomates have had this problem. it should disappear if you disable that setting.

good luck
 
Having the "log onto network" setting checked in the DUN connectiod properties will usually just result in it taking MUCH longer to authenticate when connecting.

I can't say it wouldn't cause that problem, but the symptoms displayed here aren't indicative of that problem. I honestly can't say I've ever seen that symptom from that option. This conclusion comes from 2 years of supporting customers for an ISP, so I might have a small clue here. 🙂 Granted I haven't done much dial-up support in about 9 months, but I don't think that much has changed.

I'm not saying don't check the properties there, but there are other things I would look at there first. Like:

1) Make sure the only protocol checked is TCP/IP.

2) Under the TCP/IP settings box, make sure that "User IP header compression" and "Use default gateway on remote network" are checked.

3) Does your ISP supply you with name servers? You should also enter those IP numbers in the Primary and Secondary Nameserver entries there. You should also probably have the "Server assigned IP" radio button dotted.

4) Finally, yeah, drivers. This can be a killer. Make sure you have the latest ones and that they're properly installed.
 
I have the same problem ,all settings are correct,isp is up,phone line ok and I can use another computer and connect fine.I am on my second new modem and still nothing.I connect,get about 300k and that's it. I get this message in the ie header res://c:\windows\system\shdoclc.dll. Thanks for any help.
 
Try searching for these two files:

winsock.dll
wsock32.dll

For Windows 98/98SE these are located in and should be this size:

winsock.dll c:\windows 21KB
wsock32.dll c:\windows\system 40KB

If you have Win95 goto this link and choose the appropriate version and search for the filenames to see the proper size.

http://search.support.microsoft.com/kb/psssearch.asp?SPR=w95&T=B&KT=PHRASE&T1=7d&LQ=wsock32.dll&PQ=PastQuery&S=F&A=T&DU=C&FR=0&D=win98x%2Bor%2Bwin95x%2Bor%2Bcustserv%2Bor%2Bcrossnet&LPR=%22windows+95%22&LNG=ENG&VR=http%3A%2F%2Fsupport.microsoft.com%2Fsupport%3Bhttp%3A%2F%2Fsupport.microsoft.com%2Fservicedesks%2Fwebcasts&CAT=Support&VRL=ENG&SA=GN&Go.x=21&Go.y=22

Hmm, that probably won't linkify, but...

If you have these files:

1) Make sure they're the correct size;

2) Make sure you have one and only one of each in the proper directory;

3) Rename any other instances by changing to the extension to .old. You can just right click on them in the Find window and rename them from there. Do NOT delete them! I'm not telling you to delete them and am not responsible for anything bad that may result from you deleting them. Those other files may be used by other programs, probably not, and they shouldn't be, but you never know. So better safe than sorry. 🙂

[edit] Almost forgot...

4) You may not be able to rename the wsock32.dll file if it's in use by Windows. Reboot to the DOS command prompt (this will NOT work from a DOS window!), then cd to the directory where that file resides, the ren wsock32.dll wsock32.old then enter. Reboot.

[/edit]

[edited to correct error]
 
Thanks for your help. My wsock32.dll is only 40kb not 42,could that be the problem and if so how did it change all of a sudden?
 
Dang! Sorry. My fault here for not proofing my work. 40KB is the correct size. I was thinking the old Win95 winsock.dll file I think.

Again. 40KB is the correct size.

[edit]Also why I say don't delete them just rename them. Cause sometimes I'm the bonehead. 😉[/edit]
 
I have a suspicion that as I am setting the PC up fresh with a LAN connection it won't connect with the modem - will be formatting my spare PC tonight and setting up the modem in there to see what happens
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top