DUN/IE not working

What TCP/IP settings does your ISP require? Have you checked with them on the DUN settings?

When you switch to DUN to connect, did you switch IE to "Never dial a connection"?

Are you hearing the modem dial out? Do you see your login authenticated?

all tcpip settings are correct, I can establish a connection through my ISP via DUN but when you click on IE you get the message "this page cannot be viewed". If no connection is established with my ISP and you click on IE then there is no attempt by IE to establish a connection.

I would first try to ping some servers after connecting via a command window...maybe ftp to something like ftp.microosft.com to see what kind of response you get. You may want to do an winipcfg (I think this was included in ME) and also ping the gateway you're getting. You should be able to figure out from there if it's your dun connection or IE latching onto it.

One thing that threw me once with IE5 and above was the settings you can set for a specific DUN connection. Just like there's a proxy area in IE, there's also a proxy setting you can set for the dialup. If you go to the connection tab, choose your dialup and click settings there is a completely independent group of proxy settings specific to that dialup.

One thing I've never liked with IE was the auto detect proxy. My personal experience has been that works about 2/3 of the time. I generally turn that off amd manually set them if you're using them.

If anything I would recreate my dialup from the connection wizard button in the IE properties and then running from there

Good luck to you

Mark

Did you set the IP addresses for primary and secondary DNS? Omitting that will stop you cold every time.

I would right click on the default connectoid and double check all tcp/ip settings. Does your IPS use Primary and Secondary or does it use DHCP. Check the Wins Resolution setting..probably should be set to disable. Go to Control Panel\Internet Options\Connection and make certain "Always Dial My Default" is checked. Highlight the default connection and then click settings. Then under Dial up Setting click on Properties then Server Types. Under the "Advanced Options" check boxes usually the only thing checked should be "Enable Software Compression" and "TCP\IP". Note I said usually...I have seen providers that require the Log On to Network.

I would also right click Network Neighborhood and check the TCP\IP Dialup Adapter settings there. Make certain DNS is and Wins Resolution is correctly set.

I think I may have the answer for you. Been racking the old brain and remember encountering this very problem several times before and this resolved it. Go to explorer and do a file search for winsock.dll and wsock32.dll. If you find more than one instance you should rename redundant to .old Wsock32.dll is typically found in windows\system and winsock.dll is typically found in c:\windows

Perform a "Find / Files or Folders" for wsock32.dll. Rename any copy not in the windows\System folder. I've seen this produce the problem you describe on several machines (including my own). More details can be found in the Microsoft Knowledge Base article Q175722.

This question was closed by the author