Connecting to Websites (WME)

[supered55]

When l try to connect to two particular sites l have a problem.
The message in the taskbar says, WEBSITE FOUND WAITING FOR A REPLY, thats it until the connection times out.
This happened at CNETDOWNLOAD.com and GIBSON RESEARCH CORP.
The problem cleared up, came back, cleared up.
l can connect to CNET ok at the moment but not GRC.
What l want to know is, is the problem at my end or theirs?
I.E. is 5.5
64MB RAM
Dialup connection 56k modem
OS is WINME

[DanK]

Don't know what the cause is but i just tried the CNET and GIBSON RESEARCH CORP sites and they have loaded fine.
When the page times out anything happen when u refresh the page?

[supered55]

When l tried to connect to GRC the message in the taskbar said OPENING PAGE etc, the internet bar in the taskbar moved about a third of the way and stopped. l refreshed the page when it timed out, there was no message in the taskbar, the internet bar moved its usual third of the way and after a few mins a message in the taskbar said DONE.

[TonyKlein]

If it's just about certain sites, it's usually a cache problem:

Close Internet Explorer and Outlook Express.
Go to Control Panel/Internet Options, and clear your temporary Internet files.
Now click on Settings/show files, and delete your cookies.
Or, if you're running IE 6.0, click 'delete cookies'.

Also go to Start/Find/files or folders, and search for a file called HOSTS (not HOSTS.SAM which is a sample file).
If you find it, open it and delete all web page entries.


Try that, and please post back with the results.

Good luck, Tony

[supered55]

l've cleared TEMP INT FILES and COOKIES
When l typed HOSTS in search two files came up. l opened them with INT EXPL, l don't know what they mean so have copied them below (the problem is still there )

HOSTS (SAM FILE 736 bytes )

Copyright (c) 1998 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98 # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost


LM HOSTS (SAM FILE 3.62kb )

# Copyright (c) 1998 Microsoft Corp. # # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBios # over TCP/IP) stack for Windows98 # # This file contains the mappings of IP addresses to NT computernames # (NetBIOS) names. Each entry should be kept on an individual line. # The IP address should be placed in the first column followed by the # corresponding computername. The address and the comptername # should be separated by at least one space or tab. The "#" character # is generally used to denote the start of a comment (see the exceptions # below). # # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts # files and offers the following extensions: # # #PRE # #DOM: # #INCLUDE # #BEGIN_ALTERNATE # #END_ALTERNATE # \0xnn (non-printing character support) # # Following any entry in the file with the characters "#PRE" will cause # the entry to be preloaded into the name cache. By default, entries are # not preloaded, but are parsed only after dynamic name resolution fails. # # Following an entry with the "#DOM:" tag will associate the # entry with the domain specified by . This affects how the # browser and logon services behave in TCP/IP environments. To preload # the host name associated with #DOM entry, it is necessary to also add a # #PRE to the line. The is always preloaded although it will not # be shown when the name cache is viewed. # # Specifying "#INCLUDE " will force the RFC NetBIOS (NBT) # software to seek the specified and parse it as if it were # local. is generally a UNC-based name, allowing a # centralized lmhosts file to be maintained on a server. # It is ALWAYS necessary to provide a mapping for the IP address of the # server prior to the #INCLUDE. This mapping must use the #PRE directive. # In addtion the share "public" in the example below must be in the # LanManServer list of "NullSessionShares" in order for client machines to # be able to read the lmhosts file successfully. This key is under # \machine\system\currentcontrolset\services\lanmans erver\parameters\nullsessionshares # in the registry. Simply add "public" to the list found there. # # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE # statements to be grouped together. Any single successful include # will cause the group to succeed. # # Finally, non-printing characters can be embedded in mappings by # first surrounding the NetBIOS name in quotations, then using the # \0xnn notation to specify a hex value for a non-printing character. # # The following example illustrates all of these extensions: # # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC # 102.54.94.102 "appname \0x14" #special app server # 102.54.94.123 popular #PRE #source server # 102.54.94.117 localsrv #PRE #needed for the include # # #BEGIN_ALTERNATE # #INCLUDE \\localsrv\public\lmhosts # #INCLUDE \\rhino\public\lmhosts # #END_ALTERNATE # # In the above example, the "appname" server contains a special # character in its name, the "popular" and "localsrv" server names are # preloaded, and the "rhino" server name is specified so it can be used # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" # system is unavailable. # # Note that the whole file is parsed including comments on each lookup, # so keeping the number of comments to a minimum will improve performance. # Therefore it is not advisable to simply add lmhosts file entries onto the # end of this file.

[TonyKlein]

Well, we can conclude that you've nothing in your Hosts file, I guess.

Did you do the other things I proposed, and what's the result?

[supered55]

l've emptied TEMP INT FILES, deleted COOKIES.
CNETDOWNLOAD was a problem, resolved itself, problem recurred but is now OK. GRC wouldn't load then after a week it did, now it won't. l haven't noticed this problem on any other sites

[TonyKlein]

It's sometimes useful to clear your cache in MS-DOS.

It's more thorough, and I've seen a number of cases where that fixed it, whereas doing it in Windows didn't do the trick.

So boot into Ms-DOS with a boot disk, and type the following lines, pressing ENTER after each one:

cd\
cd windows
smartdrv
deltree tempor~1
deltree history
deltree cookies

NOTE: Press Y if you are prompted to confirm any deletion

Type win (or 'exit') followed by clicking enter in order to return to Windows.

Also check the following:

Launch Microsoft Internet Explorer.
Go to Tools/Internet Options/Connections tab.
In the Dial-up settings area, select your ISP's connection so that it is highlighted, and then choose the Settings button.
Ensure that the Automatically detect settings, Use automatic configuration script, and Use a proxy server options are not selected, unless you're actually using a proxy, of course.
Choose the OK button.

Press the LAN Settings button, and do likewise.

Good luck,

[supered55]

Thanks for helping, you'll have to bear with me as l don't know much about dos.
l can access it by START/PROGRAMMES/ACCESSORIES/MS-DOS PROMPT
Will this be ok instead of using a disc.
l have a floppy l made WIN ME STARTUP DISC is this the bootup disc for accessing DOS
l'll get back to you later
Thanks

[TonyKlein]

Unfortunately you need to be in pure DOS, without Windows running for this.

It's not difficult:

If you start up with a boot disk, just type the lines exactly the way I've written them down at the blinking cursor.

You can't go wrong; curiously enough it's much easier to mess something up in Windows, than it is in MS-DOS.

Whenever the syntax isn't 100% right you get 'bad command or file name', so you can't really go wrong.

And the startup disk you've made ought to do fine.

Ga ahead, and do it. Sooner or later you'll really need to go there, and you'll be glad you had some practice doing something relatively simple like this. :)

Good luck, Tony

[supered55]

l'm afraid l'm going to have to ask you for a step by step guide about booting into pure dos with a startup floppy. l've put the floppy in the comp, switched on and l get four choices
1 help
2 boot up with cd rom support
3 bootup without cd rom support
4 minimal boot
when l press any number l get reams of info about drivers etc.
If you wouldn't mind giving me a quick step by step for this time and the future l'd much appreciate it. l'm thoroughly confused as l've only used the MS DOS PROMPT before.

[TonyKlein]

Hi Ed,

Choose 'bootup without cd rom support ', and apart from all the info about drivers etcetera, you should see a C: prompt with a blinking cursor, much like you do when you open a DOS prompt.

Something like C:\>

[Mosaic1]

Hi Tony,
I recently had the help of one of the Moderator at another Forum to write a bit about starting in DOS for WinME. He wanted to use the DOS edit function. He used the WInME bootdisk and chose "Minimal Boot"

I would think this might be the case here as well. Although no CD support could do it too. The objective is to get to an A prompt.

[supered55]

Thanks for your time Tony, l will have to try tomorrow (l'm in UK its 19-25 ) l'll let you know how it goes.
Perhaps you should write a tutorial about DOS

Cheers, Ed

[TonyKlein]

Mo,

The only experience I have with ME, is on my neigbours computer, on which I ran a scanreg /fix once.

If I remember well, It either booted straight into MS-DOS, or I else I must have chosen 'bootup without cd rom support'.

'Minimal Boot' I would have remembered, I think.

Can't be 100% sure, though.
Maybe someone else with access to a ME machine?

[TonyKlein]

<blockquote><font class="small">In reply to:</font><hr>

Perhaps you should write a tutorial about DOS

<hr></blockquote>

I don't think so, Ed, somehow...

I really know just about enough to get by, frankly.

Cheers, Tony

[TonyKlein]

<blockquote><font class="small">In reply to:</font><hr>

I would think this might be the case here as well. Although no CD support could do it too. The objective is to get to an A prompt.

<hr></blockquote>

You're right Mo,

Which reminds me I've omitted something in the commands I asked Ed to type:

He should first type C: and click enter, before typing the other commands.

Otherwise he'll be typing them in A:

Duh!

Thanks!

[supered55]

l used the NO CD ROM SUPPORT option and it worked fine, except typing in EXIT didn't do anything and typing WIN brought up the message, invalid shutdown scan disc checking drive etc. so l just switched the tower off, no problem.
Using the minimal boot option brought up an invalid command message when typing in the command CD WINDOWS and no y/n prompts on other commands so l think the No cd rom command is the way to go.
l checked the internet settings and they were OK, unfortunately the problem is still there.
When l click on Googles cache of GRC it opens the page and says 5 items remaining in the message tray, but it doesn't download the rest of the page.
Thanks for your help Tony, at least l've made a start on my DOS knowledge.
Cheers, ED

[supered55]

l've been able to access GRC after going to the following addresses and following the instructions.

http://www.winguides.com/registry/display.php/31/ (http://www.winguides.com/registry/display.php/30/>http://www.winguides.com/registry/display.php/30/</a>

<a)

Good ol Winguides

[TonyKlein]

Hi Ed,

I'm glad you were able to solve you problem, although I don't really understand how, if your MSTCP and MaxMTU settings weren't optimized before , this could possibly effect only the GRC site.

I suspect it may even have been a coincidence.

Whatever the reason, good to hear it has worked!

Cheers, Tony

[supered55]

Yesterday it was fine. Today the problem is back.
As you said it must have been a coincidence.
Oh well.

[gangsta]

I had a similar problem to yours that I was able to fix by replacing the Winsock files which seemed to have been corrupted/replaced by some adware.

before you begin delete all the protocol & network entries that use dial-up (i.e. TCP/IP or PPP etc) from your network icon in the CPanel.

Reboot & go to "safe mode" & delete/or rename/ all files in C:windows & System folders containing "winsock" & "wsock" in the name whatever the extention. (write down all the file names to enter them in the next step)

Then use the system file checker to restore the good version of the files from the windows CD (you need the CD to be accessible in safe mode)

you can access the SFC from the menu items in the System info utility in your Accessories&gt;system tools group.

after replacing all of them reboot & re-install your TCP/IP & dialers (make new connection in DUN folder).

you should be up & going now.