poinsy
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> 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.
> 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.
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.
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.
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
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
make sure
First two from winipcfg rest 0.0
First two from winipcfg rest 0.0
ASKER
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
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
Re-install Windows' "TCP/IP" services,
and bind it to Windows' "Dial Up Adapter".
and bind it to Windows' "Dial Up Adapter".
Re-install Windows' "TCP/IP" services,
and bind it to Windows' "Dial Up Adapter".
and bind it to Windows' "Dial Up Adapter".
to use winipcfg u need to be connected
it just displays the IP address,
which u can put in DNS
it just displays the IP address,
which u can put in DNS
ASKER
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
Anyway, recovering the wsock.ddl from the win95 disks sorted it.
Thanks for all your help.
Paul T
ASKER
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