From: Aron Roberts (aron@socrates.berkeley.edu)
Date: Wed Sep 25 2002 - 18:16:15 PDT
At 16:10 -0700 2002-09-25, tacito wrote:
>Yesterday and today I have trouble dialing into several Home IP
>accounts. I tried all the Home-IP numbers - Warhol, Lucent and
>General. It gives me an error message saying that "the computer
>you're dialing into does not respond to a network request. Check
>your server settings". I checked and unchecked "log into network" in
>my dial up properties but it did not help. I know my password and
>username is correct. Is Home-IP down?
For what it may be worth in helping you sort out the underlying
causes of this problem, I was able to successfully connect by dialing
into the Lucent service at 5:30 pm today, Wednesday, 9/25.
Yesterday's usage stats for the various campus dial-up modem pools
associated with the Home IP Service do not reflect any obvious
service outages:
http://ack.berkeley.edu/dcns/modems/modem-stats.html
(The Warhol service was recently transitioned to use the Lucent
modems, which most likely explains the green 'flatline' for that
specific service in the graph on the above-mentioned page.)
Nor does the recorded message at the "Central Computing Service
status recording" number, 642-4920, mention any Home IP Service
outages.
As a result, the problems you're experiencing might at least
potentially reflect an issue specific to your environment: software
(installation or configuration), modem, phone connection, or the like.
The most likely source of help is a Microsoft Knowledge Base
article specifically mentioning this error message:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299387
If for some reason the steps suggested don't work, a broad array of
other resources, both specific and general, are listed below.
Aron Roberts
Workstation Software Support Group
--Searching for a fragment of the error phrase you mentioned, "does not respond to a network request" (enclosed in double quotes exactly as shown here) in the Google search engine:
<http://www.google.com/search?q=%22does%20not%20respond%20to%20a%20network%20request%22>
brought up a list of links to Web pages that provide a variety of troubleshooting suggestions for this problem. (Unfortunately, doing a search like this can generate some 'hit or miss' results.) Most of these pages suggest re-configuring or re-installing various Windows networking components.
Some examples of pages which appear to provide relatively easy to understand (if perhaps not always trivial to carry out ;-) suggestions, some of these perhaps with ISP-specific configuration details, included:
http://support.aceinternet.co.uk/faq.asp?id=22 http://www.pacific.net.in/TS/dialing/connect015.html http://www.ecr.net/nonetreq.htm http://support.lexis-nexis.com/lexiscom/record.asp?ArticleID=ID_error_650 http://www.acer.co.in/mmpc/modem.htm#q5
If one or more of the suggestions provided on sites such as those above don't prove helpful, going through step-by-step articles on troubleshooting dial-up connection problems -- including turning on connection logging, if feasible -- may help in tracking down the source of the problem. The following are some articles on the Connecting@Berkeley Web site that may help:
http://cab.berkeley.edu/help/cd-help-win/ts-nt.html (General troubleshooting tips for Windows NT/2000/XP)
http://cab/help/cd-help-win/ts-9x.html (Detailed troubleshooting tips for Windows 95/98) http://cab.berkeley.edu/archive/faq/Win-CAB_Help/windows-logging.html (Enabling dial-up connection logging in Windows 95/98 [old article])
And just for completeness, in case a similar question might arise on this list in the future from a Macintosh user:
<http://cab.berkeley.edu/help/cd-help-mac/Mac%20OS%208%269/Documentation/Troubleshooting/index.html#Modem> (Detailed troubleshooting tips for Mac OS 8/9)
<http://cab.berkeley.edu/help/cd-help-mac/Mac%20OS%20X/Documentation/index.html#troubleshooting> (General troubleshooting tips for Mac OS X)
In addition to these C@B-related documents, above, both Microsoft <http://support.microsoft.com> and Apple <http://kbase.info.apple.com/> offer many articles on troubleshooting dial-up problems in their respective knowledge bases. A few representative examples include:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299387 [The specific article listing your error message, mentioned above]
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q308022 (General troubleshooting tips for Windows XP, with links to other articles)
http://docs.info.apple.com/article.html?artnum=106447 (Enabling dial-up connection logging in Mac OS X) http://docs.info.apple.com/article.html?artnum=106796 (Links to many dial-up and network troubleshooting articles for Mac OS X)
------------------------------------------------------------------------ The following was automatically added to this message by the list server:
For information about Micronet, including subscribing to or unsubscribing from its mailing list and finding out about upcoming meetings, please visit the Micronet Web site: <http://micronet.berkeley.edu/>.
This archive was generated by hypermail 2b29 : Wed Sep 25 2002 - 18:20:51 PDT