DNS Error

I have just fitted a new modem (D-Link DFM-560E). It appears that I can connect to my ISP - user name & password appears to verify ok, but no pages can be viewed. I get "The page cannot....DNS Error or Server not found".
I suspect that it could be a driver problem, it is using the comm.drv driver.

Could this be the problem
This is IE5 on Windows 95.

Cheers
Poinsy
poinsyAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
OttaConnect With a Mentor Commented:
> could be a driver problem.

I disagree.

When you connect to your ISP,
it sends the IP-address(es) of the DNS-servers to your computer.
If you've configured to "disable DNS",
then your computer will reject that information, and will lead to the error-message you've encountered.

The "technical support" desk at your ISP
should be able to work with you,
and correct your misconfiguration.
After all, you are paying them for "service", and if they cannot provide such "service", you should switch to an ISP which can provide "value-for-your-money".
0
 
poinsyAuthor Commented:
Thanks Otta, I do have the DNS setting disabled, however, this is also the case on my other PC (which has a different modem) and this works fine. Both are pointing to the same ISP (I get this same problem with any ISP).

This problem PC is actually a friend's, I am trying to get them on-line. The reason I mentioned the driver is because when I visited the modem supplier's web-site to download the latest driver (on my PC), the 'inf' file downloaded does not exist anywhere on the problem PC. It is using the 'comm.drv' driver. I am wondering whether my friend did not install a driver and perhaps the new device was auto detected and a standard driver used.

Cheers
Poinsy
0
 
OttaCommented:
> I do have the DNS setting disabled...
> I get this same problem with any ISP

Sounds like your hardware is OK,
but your "configuration" is incorrect.

Does it work any better when you "enable" this setting?

Does it work any better when you explicitly add '209.162.56.82' and/or '204.212.160.126' as the IP-addresses for the DNS-servers?


Also, some modems are "hardware-only" modems,
and, as such, do not require any(!) "driver" software.
You don't need to worry about a "driver" for your PC's computer;
similarly, you don't need to worry about a "driver" for a "hardware-only" modem.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
OttaCommented:
Oops!
Change my last two lines to read:
... You don't need to worry about a "driver" for your PC's keyboard;
similarly, you don't need to worry about a "driver" for a "hardware-only" modem.
0
 
amit_panjwaniCommented:
when u r connected

run winipcfg

if u see a ip address, u r onLine

Next make ur IP address as following

First two from winipcfg rest   0.0

ie is winipcfg display 204.45.55.4

Just Punch in 204.45.0.0 in ur address

may be that should work out
0
 
amit_panjwaniCommented:
make sure
First two from winipcfg rest   0.0
0
 
poinsyAuthor Commented:
Thank you for your suggestions.
I tried ping & winipcfg without success.

PING
====
I tried 127.0.0.1, localhost and others, it returns
"Unable to initialise Windows Sockets interface, error code 6"

WINIPCFG
========
When I try this, I get
"Failed to initialise Winsock" error

Both the above happen whether or not I have dialled up through DUN.

Things seem to be pointing at Winsock or TCP/IP I think.

Any more help would be greatly appreciated.

Cheers
Poinsy
0
 
OttaCommented:
Re-install Windows' "TCP/IP" services,
and bind it to Windows' "Dial Up Adapter".
0
 
OttaCommented:
Re-install Windows' "TCP/IP" services,
and bind it to Windows' "Dial Up Adapter".
0
 
amit_panjwaniCommented:
to use winipcfg u need to be connected

it just displays the IP address,

which u can put in DNS
0
 
poinsyAuthor Commented:
I have actually solved this problem now. The ping & winipcfg problems pointed me in the right direction. By searching through the Microsoft Support pages, I determined that this error can happen when an invalid or corrupt wsock.ddl file has been installed, possibly by third party software. I imagine that Freeserve (a UK free ISP) is the culprit. But it is not my machine, so I do not know the exact history. I do know that Freeserve happily overwrites files, yet does not provide an uninstall facility !

Anyway, recovering the wsock.ddl from the win95 disks sorted it.

Thanks for all your help.

Paul T
0
All Courses

From novice to tech pro — start learning today.