27,100 posts on "unable to browse the network" and no answer

Discussion in 'Windows Networking' started by Richard B, Feb 25, 2004.

  1. Richard B

    Richard B Guest

    I have read several hundred of these posts. This seems to be a serious
    problem for all Windows OS's. A small percentage of these problems look to
    be configuration errors or the autologon key and are fixed, but following
    the threads, it appears that most problems are never resolved. I've been
    through every procedure that I've read (short of reinstalling the OS)
    without success. Is this some kind of major bug in Windows? What is Micro-
    soft's overall response to this problem?
    My small "C" network works just fine. The troubled machine is a Compaq
    2120, without a netcard, running Win 98, set up the same as the others.
    It absolutely cannot see itself in Network Neighborhood or ping itself.
    There is always the "not logged on" message. It can find itself in the
    find box, but cannot be opened. It can, through DCC and Hyperterminal
    connect to, find, ping the other computers and go Internet. I have seen
    machines without netcards, using Windows Logon that can browse themselves.
    Is there any surefire answer? Any and all help is greatly appreciated.
    Richard
     
    Richard B, Feb 25, 2004
    #1
    1. Advertisements

  2. I'm not quite sure what you're hoping to accomplish here. If you have no
    network card, what exactly are you trying to fix? What possible good can
    you be doing by "browsing your own machine" instead of using Explorer?
     
    Richard G. Harper, Feb 26, 2004
    #2
    1. Advertisements

  3. Richard B

    Gerry Voras Guest

    There are for things you need for a a network client:

    1) An Authentication Client (typically Client for MS Networks)
    2) A NIC and drivers
    3) A Protocol (typically TCP/IP with associated winsock drivers)
    4) optionally, a service (typically File and Print Sharing)

    If you haven't set up any of these, the you won't have a Network
    Neighborhood icon. If you don't set up all of these, then NetHood won't do
    anything. Sometimes, you can browse locally if you have Client for MS
    Networks installed in the network stack, AND you have declared a shared
    resource. But honestly, what would be the point of doing this if Windows
    Explorer is working?

    To prove this, open up a command line and type in "PING 127.0.0.1" and hit
    return. If you get "command or file not found" then TCP/IP is not
    installed. If you get something else like "destination unreachable" then
    you have no working transciever (a NIC or modem).

    If you use Hyperterminal, you are creating a SLIP or PPP connection, which
    substitutes for the above in a network sense. However, Hyperterm is not
    NetHood aware and does not use an MS authentication client. And you
    probably not pinging from the local machine, but from the machine you have a
    terminal session established with (basically, a remote shell).

    DCC is a whole other matter, because it does require elements of the network
    stack to work. I've never tried pinging through it, because I usually opt
    for NetBEUI instead of TCP/IP when I establish this kind of connection;
    also, NetHood usually just slows things down for me in DCC. I usually skip
    the whole thing altogether and use Intersvr in real-mode.

    Basically, I think you are overreacting just a bit. Understanding
    networking takes time and effort -- its not supposed to be easy. Even these
    days, a good MCP or MVP can earn a living fixing these kind of problems for
    people. That's why this news group exists, too.
     
    Gerry Voras, Feb 26, 2004
    #3
  4. Richard B

    Gerry Voras Guest

    Damn, sorry. I hit "reply all" and ended up crossposting. Sorry about the
    breach in ettiquite.
     
    Gerry Voras, Feb 26, 2004
    #4
  5. Richard B

    Richard B Guest

    Gentlemen,
    To explain, this machine is used by a rep who has compiled a lot of
    valuable data on it. We need to tranfer information effectively. With DUN
    and DCC the computer connects, but never opens a window. This is where we
    get the "unable to browse network" and "not logged on" messages. Since this
    also is the case for Network Neighborhood, it was assumed that fixng it in
    NN would fix it elsewhere. It was just a guess that if the machine could see
    itself, it would be logged on. We've worked on this thing for a few weeks
    using info from these posts, and all of us haved learned a lot. If we had
    known, we would have used another machine, but now we are just looking for
    an immediate solution. My surprise was the number of posts on this subject,
    and I can see that it could keep an MCP busy! Now that that Intersvr has
    been mentioned, that may be our solution.
    I should mention that since looking at these newsgroups, we've fixed
    a few other problems, and truly thank all respondents.
    Richard
     
    Richard B, Feb 26, 2004
    #5
  6. Richard B

    Gerry Voras Guest

    OK, I get this now. Here's what you might try:

    1) YOur network stack currently probably consists of the following
    components:
    a) Client for MS Networks
    b) Dial-up Adaptor
    c) TCP-IP for DUN

    2) The prefered client is probably Client for MS Networks. Change it to
    Windows Client. You may need to delete all *.pwl files on the computer and
    rebuild a local user account with password.

    3) in the Client for MS Networks, blank out the current domain setting.
    Your user is probably trying to log into a network that is non-existant. If
    this is Win95, you might just delete the Client altogether, but it might
    screw up connecting back to the home office domain through the modem later
    on -- so just leave it in. When your user dials back into the home domain,
    he'll have to enter in the proper domain name.

    4) File and Print Sharing Services. Once installed, click on the resource
    box that you want shared (files, in this case). Be very careful with this
    on, because when the user is dialed into the Internet, the hard drive will
    be open to EVERYBODY. Also, you will need to set up "share" level resources
    as opposed to "user" level -- if its "user" level, the setup will start
    looking for a non-existant domain.

    5) In My Computer, bring up the properties list for the C: drive and share
    this drive with the name of "C". Use "share" permissions, requiring a
    password for both reading and writing. Again, this is very dangerous should
    the computer connect to the Internet.

    NetHood should now show a shared resource called "C". Clicking on it will
    bring up a read access prompt.

    I tried this in the lab today, and it seemed to work. Your milage may vary,
    however. As a professional, I would consider this a non-optimal setup, but
    it could be useful if you are demonstrating how to access shared network
    resources. However, if this is the case, then the local admin should
    provide a demonstration computer on the network in question, or simply map
    drive letters to domain shares so that Explorer would be used instead.

    Also, most admins will use Poledit or TweakUI to prevent the appearance or
    use of NetHood in many domain network PC situations anyway. So the above is
    definately not a universal solution for training purposes.

    Finally, Intersvr (that I mentioned) is only a DOS, very old school file
    transfer program. I wouldn't bother with it in a user training program -- I
    spent 15 hours teaching an advanced administration class how to use it and
    things like it properly. In the end, the students decided that they would
    rather have a real network than use some of the emergency stuff like this.
    I guess I'm getting old.
     
    Gerry Voras, Feb 27, 2004
    #6
  7. Richard B

    Gerry Voras Guest

    Oh, one last thing (I keep getting more and more info every time I read your
    posts) -- get a network card and do a backup to protect your rep's "valuable
    data". Offload that stuff to a server, at the very least, and it would take
    far less time with a NIC rather than using DCC.
     
    Gerry Voras, Feb 27, 2004
    #7
  8. Richard B

    Richard B Guest

    Following through on previous post. Our biggest mistake was not checking the
    machine we used for connectivity. One man actually broke out a pair of Intersvr
    floppies, but it seemed to balk at the Fat32 redirected drive. Boss want to
    pull the drive. We're trying!
    Thank you again, Richard
     
    Richard B, Feb 28, 2004
    #8
  9. Richard B

    Gerry Voras Guest

    Yea, intersvr will do that unless you are using the most recent copies.
    Since it is real mode, it won't work all that well with the gui anyhow. Do
    yourself a favor and get a NIC.
     
    Gerry Voras, Feb 28, 2004
    #9
  10. Richard B

    Richard B Guest

    Gerry,
    Appreciate your interest. This computer was not expandable. Over the
    weekend our workhorse finally swapped drives with a communicating machine,
    setup and got our data transferred and backed up. Problem solved the hard
    way. I've taken the old machine home, reloaded it and intend to use it to
    learn more. I will continue to follow these newsgroups regularly. I've
    gained in insight into your world and appreciate what you do. I'll bet so
    do many others.
    Thanks, Richard
     
    Richard B, Mar 4, 2004
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.