Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Windows 95 Network configuration on 486

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Windows 95 Network configuration on 486

    I am attempting to connect a 486 running win95 to the internet.*

    The network adapter is a Novel/Anthem NE2000 compatible (from the auto-detect hardware wizard); I'm using the provided Microsoft TCP/IP protocol, and Client for Microsoft Networks.


    My Network config. panel looks like:

    Client for Microsoft Networks.........set to Quick logon

    NE2000 Compatible.....................Enhanced mode 32 & 16 bit NDIS driver
    ....................Bindings: TCP/IP,
    .................IRQ: 5, I/O address 300-31F (no conflicts)

    TCP/IP.................IP Address: 192.168.1.95
    .................Subnet Mask: 255.255.255.0
    .................Gateway: 192.168.1.254
    .................Bindings: Client for Microsoft Networks


    Primary Network Logon: Windows


    Ping, telnet, ftp .... neither or these work. Neither does Internet Explorer. (however, I can load the crynwr NE2000.COM driver successfully from the command line, and see my Ethernet Address).


    Running the Internet Setup Wizard (msie20.exe from ftp.micrsoft.com) doesnt help either.



    Any ideas on getting the computer connected?





    *because Windows 95 is an awesome and a hugely underrated operating system **


    **but not including the part where you have to restart your computer dozens and dozens of times as you troubleshoot/reconfgure settings in the control panel.
    Last edited by jonnymacuser; October 1, 2012, 12:06 AM.

    #2
    I don't see any name servers there. If that's all you're missing, then you should be able to ping the gateway (192.168.1.254) but not anything past that unless you use numbers for that as well.

    You're probably on top of it, but is your router set up correctly?
    WANTED: Cardinal 2450MNP modem.

    Comment


      #3
      Originally posted by Ole Juul View Post
      I don't see any name servers there. If that's all you're missing, then you should be able to ping the gateway (192.168.1.254) but not anything past that unless you use numbers for that as well.

      You're probably on top of it, but is your router set up correctly?
      I've got DNS set to 8.8.8.8 and 8.8.4.4 for google.

      My router? Like what should I look out for?

      Comment


        #4
        Originally posted by jonnymacuser View Post
        I've got DNS set to 8.8.8.8 and 8.8.4.4 for google.

        My router? Like what should I look out for?
        I don't know what to "look for", but it too should have an IP for the next router (your ISP) and be set up similar to your computer so it, in turn, can connect. So, can you ping 192.168.1.254?
        WANTED: Cardinal 2450MNP modem.

        Comment


          #5
          I guess I should have said exactly what the router should have. I'm assuming you use DHCP to get the info from your ISP, so things should look something like this?

          Connection Type DHCP
          IP Address xxx.xxx.xxx.xxx
          Subnet Mask 255.255.255.0
          Gateway xxx.xxx.xxx.xxx
          DNS xxx.xxx.xxx.xxx
          MTU 1500
          WANTED: Cardinal 2450MNP modem.

          Comment


            #6
            How are you trying to connect to the internet ? Cable, DSL, Phone, what ?
            What else do you have that's connected to the internet ?
            What are you trying to ping ?
            Like Ole Juul suggested, try pinging your gateway, but also try pinging yourself, and try pining 127.0.0.1
            These last two should tell you if there's anything odd going on with your stack.
            patscc

            Comment


              #7
              I think that the first thing is to try to connect to your router, usually routers are in 192.168.0.1 or 192.168.0.2, open internet explorer, and try. Also, enable drive sharing, and do as patscc said, try to enter in 127.0.0.1, you should see your computer.

              Comment


                #8
                Originally posted by Ole Juul View Post
                So, can you ping 192.168.1.254?
                Nope.

                When I try to ping the 2WIRE router:

                C:\...ping 192.168.1.254

                Request timed out.
                Request timed out.
                Request timed out.
                Request timed out.


                I'll try pinging myself and report back here.

                I've checked the cable (which goes from the computer > hub > router via ethernet cable) and it works fine for other machines.

                Under "TCP/IP Properties", when I set it to "Obtain an IP address from a DHCP server" -- an error message pops up, "The DHCP client was unable to obtain an IP address ...." Hence the static IP configuration I mentioned above.

                This is embarrassing.
                Last edited by jonnymacuser; October 1, 2012, 08:21 AM.

                Comment


                  #9
                  Do you have another computer hooked up to the hub ? If yes, see what it reports for it's configuration. You should at least be able to see if you've got the correct gateway.
                  patscc

                  Comment


                    #10
                    Double-check the IRQ--I've been tripped up by that on occasion. Windows will swear that everything is wonderful, yet the NIC operates as if it were made from clay. You should at least be able to ping your router--but remove the "Gateway" IP address first.

                    Also, W95 is extremely stupid about NIC auto-detect. What is the actual card that you have and do you have the configuration utility for it?
                    Last edited by Chuck(G); October 1, 2012, 10:41 AM.

                    Comment


                      #11
                      Originally posted by Chuck(G) View Post
                      Double-check the IRQ--I've been tripped up by that on occasion. Windows will swear that everything is wonderful, yet the NIC operates as if it were made from clay. You should at least be able to ping your router--but remove the "Gateway" IP address first.

                      Also, W95 is extremely stupid about NIC auto-detect. What is the actual card that you have and do you have the configuration utility for it?
                      The IRQ gets set to 3 after auto-detect & add new hardware.

                      However, the IRQ is shown as *3, meaning there is a conflict with COM2. So I've set it to 5 via the control panel.

                      The actual card? I wish I knew. The computer is a unisys cwd 486. Is there a way to see by examining the motherboard (I believe the card is integrated into the motherboard).

                      Comment


                        #12
                        If you can disable com and sound in the BIOS or via jumper, you might want to try that.
                        patscc

                        Comment


                          #13
                          There is also the possibility your NIC isn't making a proper link to your switch/hub/router, there are a number of early 10BaseT cards that don't link properly with modern 10/100/1000mbps switches/hubs/routers, I typically run all my vintage gear off its own older 10BaseT network hub.

                          I have an old Mac (with Asante NIC) and and old XT clone (with 3com 8-bit NIC) that will just not work (despite link lights) on my gigabit network gear, but works just fine hanging off an old 3com 10BaseT hub (which is connected to my gigabit network).

                          Not sure if this is your particular problem or not, but its worth mentioning.
                          My Vintage computer/blog site
                          Searching for a keyboard for a WYSEpc WY-1100.

                          Comment


                            #14
                            Ok, so I can ping the machine itself, when I do:

                            C:\...ping 127.0.0.1

                            Pinging 127.0.0.1 with 32 bytes of data:

                            Reply from 127.0.0.1: bytes=32 time=1ms TTL=32
                            Reply from 127.0.0.1: bytes=32 time=1ms TTL=32
                            Reply from 127.0.0.1: bytes=32 time=1ms TTL=32
                            Reply from 127.0.0.1: bytes=32 time=1ms TTL=32


                            And I do have an old 10BaseT hub in there between the computer and the 2WIRE gateway/router.


                            If I can successfully ping myself, does this mean that the problem is with the computer and the router talking to each other?

                            Comment


                              #15
                              Out of curiosity have you set the computer to DHCP rather than trying to set it static to see if it grabs an IP? If it cant pull a DHCP address its, in my experience, probably not TCP stack configuration, I would look to IRQ/IO configuration (try a free IRQ maybe?) or hardware link causes (bad cable, broken RJ45 plug on NIC?)

                              I was fighting a Dell laptop the other day that would not link up, took me like 4 hours of screwing with it to find out that the pins in the dang jack were bent out of place
                              My Vintage computer/blog site
                              Searching for a keyboard for a WYSEpc WY-1100.

                              Comment

                              Working...
                              X