Solved

WIN 95 LAN

Posted on 1998-07-02
112
906 Views
Last Modified: 2013-12-23
I have four computers in my office all set up with win 95
each has an eterEZ 8416 card and all are cabled into an
unmanged 9 port 10 base-T ethernet hub
1.) I have been un sucessful in configuring computers to
    see each other,  what do i need to do?
2.) I have been unable to set the larger of the four
    systems to be an administrator, what needs to be done?
3.) Do i need additional software to use the LAN for this
    office site?
4.) I have set up the following in my network neighborhood
    a. CONFIG;
       [MS Networks][MS Family Logon]
       [AOL adapter\enhanced NDIS driver,TCP/IP]
       [Dial up adapter\enhanced,IPX/SPX-record a log-IPX
        header]
       [SMC eterez (8416)\enhanced-network monitor driver
        NET Beui]
   b.) IPX/SPX Dial up [net bios over ipx/spx]
                       [force even ...not present]
                       [frame type ...auto]
                       [max conn .....4]
                       [max sock .....2]
                       [Netwrk add ...0]
                       [source rte ...16 entry cache]
        {client MSNET,File Prnt Share MSnet,MSFAm,MS SNMP,
          NetBIOS IPX/SPX}
        [MS NETWRK Monitor Driver (SMC 8416 )]
          netwrk adapters
            000 ... SMC8000w.vxd
            001 ... PPPMAC.VXD
            002 ... AOLMAC.VXD
       MS Netwrk Monitor Agent
   [netbeui smc8416]
      client for MSNetwrk
      file prnt share MSNEtwrk
      MS Fam Logon
         Max sessions ...10
         NCBS         ...12
           set protocal as default
I hope that some body will be able to set me straight onto
the right path or give me direction into correcting my
failure

thank you

Michael
0
Comment
Question by:MJCSR
112 Comments
 

Author Comment

by:MJCSR
Comment Utility
Edited text of question
0
 
LVL 3

Expert Comment

by:jjmartin
Comment Utility
It sounds like you have all the hardware and software you need to connect these PC's.  I have connected four PC's myself using network cards and a hub.  Windows 95 is the only software you need.  If the network cards are installed and working correctly with no conflicts, and the hub is working, then check your cables.  You must be using the proper type of cable (RJ-45 crossover cable is it I believe), or the PC's will never see eachother.  Also, check and make sure that all your resources are shared on each PC.  Try deleting and reinstalling your network protocals.  Make sure you have the client for microsoft networks installed on each PC as well.  Give this a shot and let me know if you get anything going.  If this doesn't work, I may have some more things for you to try.  Good Luck.
0
 

Author Comment

by:MJCSR
Comment Utility
At this time I am useing twisted pair on all connections from computers to hub into the RJ-45 STP.  all connections are from ports 1-4, all connections are going into hub. should there be any coming out? ports 5-8 or out or to the 1 bnc port.
still confused?
thank you

0
 
LVL 3

Expert Comment

by:jjmartin
Comment Utility
As long as all the PC's have a good connection to the hub, that is all you need.  There is nothing needed in the bnc port or ports 5-8.  I will check my notes on this and see what else I did.  I will have to get back to you later.

Check to make sure the twisted pair is the correct type.  There are two types.  One works, one doesn't, and they look pretty much the same, except, one will have more wires inside of it.  Check your book for the Hub and it should tell you how many wires should be inside your cable.

P.S.  I have never done anything as frustrating as setting up a windows 95 peer to peer network.
0
 

Author Comment

by:MJCSR
Comment Utility
Have checked twisted pair they seem to be the right amount of wires 4 sets of two each all in the same sequence on both ends.
as far as the right type i was unaware of any diferences this is what i have;
"LUCENT - C  SYSTIMAX  1061C4  4/24  CM  VERIFIED CAT 5  EL046345  02434  ET"

THANK YOU FOR YOUR CONTINUING EFFORTS

Michael
0
 
LVL 3

Expert Comment

by:jjmartin
Comment Utility
Try another type of cable.  I think that is most likely your problem.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
IMHO, it is NOT a cabling problem.  It's hard to believe that ALL four cables are bad.  Make sure that all LEDs (on the hub and on the computer's network card) are on/green.  If you have a cable connected to a hub's port and it isn't lighted, most of the time, then you have a cabling problem.

To correct some statements, there are two types of twisted pair cabling:  straight and crossover.  Crossover cables are used ONLY between two similar devices (e.g. hub-to-hub, computer-to-computer).  Straight cables are used (in this case) to connect the computer to the hub.

Yes, you have all the hardware and software necessary to connect to another computer.  According to your description of the Network Neighborhood's Properties, you have a tangled mess.  Thus, Windows 95 doesn't know what to do, and you can't see other computers.

Do you have a modem AND ethernet card?  Are you using AOL?  Are you also on a Novell network?

To unravel the mess, delete everything in the Network Neighborhood Properties EXCEPT for your network adapter (eterEZ 8416).  Then, install "Client for Microsoft Networks".  I believe this should also give you NetBeui and IPX compatibility, automatically.  Now, install file and print sharing.  You should now be able to see the other computers.

If you have a Novell network, now add the "Client for Novell Netware".  If you have AOL, install its adapter.

Now, if your network does not connect out to the world and you need to use the modem to connect to AOL, install the dial-up adapter BEFORE the AOL adapter.

(Please note that order MATTERS.)  I hope this helps.

--MikroData (jkjung)
0
 

Author Comment

by:MJCSR
Comment Utility
Thank you for your time and effort jjmartin,  but unfortunetly i do not have the resources to rip out and replace the cable throughout our office. Although i will keepthis in mind as an extreme and last resort, but i will try the response from jkjung first.

Michael
0
 

Author Comment

by:MJCSR
Comment Utility
Hello jkjung I see I have drawn fire from the rest of the group now.
Yes it is a very tangled mess that i have created.
I do have a modem that is used for faxes and AOL, this is set up on all computers.
Yes each system has its own access to AOL and at this time is our only avenue onto the net.
No I do not belive we are or have a norvell Network.
(do i need another program to use LAN?)

Upon your suggestions i have removed all but the EtherEz 8416 adaptor from network neighborhood.

loaded now is
 CLIENT      Client for MS NW
 ADAPTER     AOL Adapter
 ADAPTER     SMC EtherEZ (8416)
 PROTOCOL    IPX/SPX-compatable Protocol -> SMC EtherEZ (8416)
 PROTOCOL    TCP/IP -> AOL Adapter
 SERVICE     File and printer sharing for MS NW

I have placed this information upon all systems and lo and behold still Nothing
computers still only recognize themselves
all systems have the same group name but different computer names
and different descriptions, all are set up to share files with the same passwords for access
all computers sign on with client for MS NW with password
I do thank you for your intelegent response and assistance hope that you can continue to assist in this disaster.

Thank You
Truly

Michael
MJCSr.
0
 
LVL 3

Expert Comment

by:jjmartin
Comment Utility
Here are a few last ditch effort things to try(before recabling).  Try bringing up Network neighborhood several times.  I have had the problem where a PC will not show up in the network the first time I open Network neighborhood.  In the run menu off the start button, type in one of the other PC's host names and see if that will bring it up.  Try running "net start" in the run menu.  
       I have gone through this before.  Trying everything programaticaly to get the PC's to talk to eachother, pracatically pulling my hair out in the process.  Finaly I discovered it was a hardware problem - I wasn't using the right type of cable(I discovered this after replacing the Hub and network cards).  Once I had the right cable, and the network cards were setup properly with the proper proticals, the PC's just found eachother.  That is why I think this is a hardware problem somewhere, maybe even the hub.  It sounds like you are doing everything else correctly.

0
 

Author Comment

by:MJCSR
Comment Utility
to jjmartin

Try running "net start" in the run menu.
 
Error 3545: You cannot start or stop the network from within an MS-DOS window.

Michael


0
 

Expert Comment

by:kiljoy
Comment Utility
MJCSR:

Two things to try:

1) Make sure your RJ45 plugs are correctly attached to the cable.  BTW, you do have the right type of cable (CAT5=catergory 5).  I think this is the order: The plug should be attached so that with the connector pins facing down and away from you and the wire leading from the plug towards you.  The wires (I think!) should be in this order (from RIGHT to LEFT) BrWh,Br,GrWh,Bl,BlWh,Gr,OrWh,Or.  This may not be the correct order but I think it is.  Also, realize that those wires are not supposed to be in sequential order.  The Gr is supposed to be separated from the GrWh.

2) Make sure your hub can support 9 connections.  I have a hub just like yours that uses the 8th port OR the BNC connector.  Try disconnecting BNC or port 8 and see if it works.  Also, with the computer(s) connected to the bnc port, the BNC cable should not go directly into the hub.  You need a T-connector for each device on the BNC cable, and terminators for both ends.

Good Luck.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to kiljoy:
  Yes, this is the correct order for a 10/100-BaseT wire on both ends.  However, you listed the order from pin8 to pin1.  It doesn't matter, since the order is correct (from right to left), if it is looked at upside-down.
  MJCSR only has four computers.  Did you give him another five computers to hook up to his hub?  Correct me on this, if I'm wrong.

--MikroData (jkjung)
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to MJCSR:
  I looked at your new Network Neighborhood.  You are missing one thing.  It is required for computers to communicate over a local area network.  Once you've installed this component, PRESTO!  Actually, it is in my answer you rejected.
  Also, check BOTH the hub and the back of the computer (where the NIC is) to make sure that the "link" lights are on.

I hope this helps.

--MikroData (jkjung)
0
 
LVL 7

Expert Comment

by:Eric B
Comment Utility
why do you have only IPX???? Use netbeui to bind your smc card!
0
 

Expert Comment

by:kiljoy
Comment Utility
comment to jkjung:
Thanks for verifying the pin order.  I listed it that way because strangely, that is how I remember it in my head.

No I did not give MJCSR an additional 5 computers (ha!).  I don't know what I was thinking, sorry.


0
 

Author Comment

by:MJCSR
Comment Utility
kiljoy
Thank you for the input and sequencing
That was the first thing that was checked and verified
cables are same at both ends and hub does recognize the computers exist
Oh And thanks for the xtra systems
sorry but does not help in my situation
0
 

Author Comment

by:MJCSR
Comment Utility
jkjung

Again i have looked back over your Answer and find only two differences those being
1 Protocol NetBeui which when installed gives me an reeor message upon start up " while trying to load protocol 0
                        error 254"
removed it does not
and
2. Novell network, now add the "Client for Novell Netware".  
   I do not believe that i have this program
     reason being that also upon start up now i recieve another type of message " Novell Compatible shell is not available, see your net work administrator for assistance"

well i keep administering but am un able to help

what is the next step that i should take?

do i need to find this novell network, and is this another program that i need?

I thank you for your info again and am still attempting to resolve this matter

truly

Michael
MJCSr.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
You don't have a Novell network, thus, you don't need to install Client for Novell Netware.  Also, you don't need IPX, because that is used for Novell networks.  Take those out.

To use NetBEUI, you need to have Client for Microsoft Networks.  Make sure THAT is installed, also.  (Yes, this was the protocol I was referring to in my last comment.)

Side note:
  Did you want to assign accounts?  The Windows95 login screen that you see only allows for a different desktop (among other user settings).  It can be bypassed by pressing ESC.
  What did you want to do with an "administrator" computer?  In a peer-to-peer network (what everyone is commenting about), every computer has EQUAL rights on the network.  Of course, each computer has its own individuality (passworded login for sharing).
  One reason for using peer-to-peer networking is to be able to transfer files with ease between computers.

I hope this helps.

--MikroData (jkjung)
0
 

Author Comment

by:MJCSR
Comment Utility
MikroData (jkjung)
thanks for the additional input have removed the ipx as stated perhaps this will also remove the (Netware compatable shell is not available contact administrator for help) mesage that i have been recieving will now attempt to do the same with my other computers
Keeping my fingers crossed on this one

truly

Michael
MJCSr
0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
Netware message should only show up if you have Client for Netware (or Netware Shell) loaded under networks.  If you do, remove it, there's no reason for Netware for a network this size.

I've found IPX to be a simple protocol to configure (though slow) to at least get a peer-to-peer win95 network running.  Refine to better protocols AFTER you get contact.

You said each computer could see itself.  Have you tried to browse through the computer?  I believe the local computer will show up without any network activity at all, but if you can't browse thru its directories, there is possibly a cabling/hub problem.

If you haven't already:  Right-click on Network Neighborhood, Find Computer, type in one of the other computer names.  If browse master (or is it LM announce?) under file and printer sharing is turned to true, you shouldn't need to do this, but it's good to check.

You should NOT get a netBEUI error, even if the protocol is not in use.  This means that you either have bad networking files (microsoft), or the protocol is having a problem with the card/cables/hub.

Make sure you don't have different versions of the win95 CD when you're loading protocols.  If they're on the drive, you may have a bad .cab file.

One last thing - when you try to browse the network, or do a find for a computer (there SHOULD be a pause while it looks) - does the light on the hub under that computer's connection flash at all?  It should display some form of activity....
0
 
LVL 5

Expert Comment

by:bchew
Comment Utility
I suspect, as others have, that you may have a cable problem.  Do you have RJ45 wall outlets and a jumper cable from the wall to the PC?  If so, and if the building wiring is crossed you can correct the problem by using a cross-over jumper between your NIC and the wall without having to re-wire the building.  The same applies if you have a patch panel in your closet with the hub and the hub is connected with jumpers to the patch panel.
0
 

Author Comment

by:MJCSR
Comment Utility
to kmarf
I have tried to look for other computers and still nothing but my own
when i Explore my netwrk neighbrhd
i see the following arrangements
Network
   |_____ Entire Network
   |       |_____ LAPE  ( work group same on all )
   |               |_____ ENG ( my system )
   |
   |_____ ENG ( again my system )

I no longer have the Novell error thanks
but i still see only one computer plus its shadow on each system

when i browse or explore the network the hub does not flash

on my hub i have green lights for:
power
systems tp1-tp4 on the Rx side
and red light on partitionside of bnc

thanks

Michael
MJCSr
0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
Looks like there's the problem, need a solution.  Might vary with hubs, but those I've worked with always indicate when there's activity reaching it.

I've heard cabling stories of old wiring with bizarre nonstandard color progressions.  

You said you checked cable, was that just the patch from the PC to the wall?  Maybe pull one of the panels out of the wall and make sure the colors are the same...
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
If there is a connection at the wall, there are two types of jacks (once you remove the cover):  the one that looks like it's for a telephone (four screws) and the one that uses a punch-down tool.  Personally, I like the one that you punch down.

I don't remember the order for the punch-down jack, because I always use the numbers labeled on it.  I've only done the one with the four screws once, so I can't give the order for that either.

Unless you have a tone tester (like the ones the telephone company uses when they come to your house to find out whether you have a bad wall connection or whatever), you can't really test the jack THOROUGHLY.  Just pull the hub off the wall and run two cables DIRECTLY from the computers to the hub.  That eliminates the likelihood that it's a jack problem.

However, it don't sound like MJCSR has this kind of a setup.

All the hubs I've seen should have flashing LEDs when the network is accessed.  Look in the manual or information about the hub on the web to see if it is supposed to flash with network traffic.

Just a wild idea:  Connect ONLY two computers to the hub, instead of all four.  Play around with using different (combinations of) ports each time.  Avoid using ports 1 and 9.

By the way, what is the brand and model name of the hub?

I hope this helps.

--MikroData (jkjung)
0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
might even be able to persuade someone to let you borrow a tester.  The place we get our cable from has a couple they loan out - they figure it's a good bet you'll buy a few things from them if it tests bad.
0
 
LVL 5

Expert Comment

by:tcalesa
Comment Utility
You could buy a cheap crossover cable, connect two computers together and see if the problem goes away. if so, you have either a bad hub or cabling. If not, uninstall all networking components from the two computers, and reinstall the very basic networking software needed for the two to talk to each other. start with MS client/Netbuei only on your NICs. if it starts working, add other packages one by one until they either all work or you find the culprit.
If the basic config doesn't work, try using real mode netbios drivers (I have a couple of really flaky cards that need that)
Hope this helps.
Tim
0
 

Author Comment

by:MJCSR
Comment Utility
jkjung
 I have had the cables all checked out by the phone company who installed all(but one which is disconected)are functioning from wall junction box (behind computer terminal)to junction box at Hub. jumper cables also tested from computer to wall and from hub to box. ( we are in a two story bldg that has had new wire and cable installed hub and my computer are located on second floor and other three are on 1st.
Hub Brand is "LanPro-9 PORT 10Base-T ETHERNET HUB" lights are to be steady green unless problem then steady red.

Still will try to only config two first then three then replace
the bad jumper on the last one

thank you for the update and the continued responses!

truly

Michael
MJCSr.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Just for the curious...

Information about the hub in question is located here:
  http://www.edimax.com/er5390s.htm

--MikroData (jkjung)
0
 
LVL 1

Expert Comment

by:rosscoe
Comment Utility
Please could you re-post the contents of your Network Neighbourhood properties box. It doesn't sound to me like you have a clue how to install protocols and adapters and I think that you STILL have a problem with this.

We need to know that

1. your network adapters are installed properly (are there yellow exclaimation marks in device manager?)
2. You have a common network protocol installed on each machine (NetBeui is technically the best and most simple choice here)
3. That you have microsoft client installed and that you have enabled file and printer sharing on each machine
4. Lastly that you have actually SHARED a resource on each computer.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to rosscoe:
  You do not need a shared resource to see another computer on the network.  Thus, file and printer sharing is not necessary to resolve this problem.

--MikroData (jkjung)
0
 

Author Comment

by:MJCSR
Comment Utility
--MikroData (jkjung)

have contacted http://www.edimax.com/er5390s.htm ms judy chung has responded semms to be alittle confusion here though aparently ther is supposed to be some kind of software included with this hub to initiate? will keep watching for new comments and hopefully one may finaly be prosed as an answer to my problem, Again thank you for hanging in there with me on this.

truly

Michael
MJCSr.
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to rosscoe:

re-post the contents of your Network Neighbourhood properties box
    a. Client for ms netwrks
       AOL adapter
       Smc EtherEz (8416)
       Netbuei->SMC (8416)
       TCp/IP-> AOL adapter
       file and print share for MS netwrk
       
1. your network adapters are installed properly (are there yellow exclaimation marks in device manager?)
   a.  no flags or errors
2. You have a common network protocol installed on each machine (NetBeui is technically the best and most simple choice here)
   a.  same set up on all computers
3. That you have microsoft client installed and that you have enabled file and printer sharing on each machine
   a.  same set up on all computers
4. Lastly that you have actually SHARED a resource on each computer.
   a.  same set up on all computers

0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
"supposed to be some kind of software included with this hub to initiate?"
A representative of the manufacturing company told you this?  And didn't tell you how to get said software?  
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
The web site did not mention any software.  Besides, I've NEVER EVER seen software that is required for a hub to work.

The only time you need software is for the network card.  If you have a router, you need software to configure it, but you don't have one, so this is irrelavant.

You may want to search the web for updated drivers for the network cards.  Although this is an unlikely to be the cause of the problem, we want to eliminate this possibility.

I hope this helps.

--MikroData (jkjung)
0
 
LVL 5

Expert Comment

by:tcalesa
Comment Utility
Dump all of the extra stuff like the AOL service and tcp/ip. Make two computers so that only the NIC and Netbuei and MS client software show in the properties.

See if your workstations see each other. If not, try using the real mode NDIS drivers for the card rather than the 32bit driver.

If they still don't see each other, buy an inexpensive crossover patch cable and connect them directly to each other. Try again.

If they do, start replacing this config with the one you desire one component at a time. test and move on to the next.
0
 

Author Comment

by:MJCSR
Comment Utility
TO all
SORRY MY ERROR NO SOFTWARE!

to tcalesa,
I have tried to bring these systems down to bare bones as
suggested, with no conclusion found. ie.. MSNET, Ether, NetB, F&P
the only time i was able to see more than one computer, was when i laplinked into my laptop through printer cable.

at times when i start up systems i can not even browse the network neighborhood. unable to link directly with other computers except through jumper but still even with jumpers there is only one system on each computer.
0
 

Author Comment

by:MJCSR
Comment Utility
to MikroData (jkjung

have found updated drivers for my SMC ISA card will attempt to reinstall and or configure such, this might be a very good
thought.

Michael
MJCSr.
0
 

Author Comment

by:MJCSR
Comment Utility
To ALL
have updated my SMC Drivers.
still only see one computer per system.
boy this is exhausting.
have even removed all but MS Net/ SMC adapt / NetB
and tied cables direct to junction boxes but without any different results.  am begining to belive that (besides that i do not have a clue as to what and or how to set this lan up) i may have some kind of hardware problem. but i am not an expert nor do i claim to be in this field.
hope that we can reslove this in time am going to up the anti another notch ( if it will let me)

thank you one and all
and please dont give up on me yet

truly

Michael
MJCSR
0
 

Author Comment

by:MJCSR
Comment Utility
Adjusted points to 250
0
 
LVL 1

Expert Comment

by:bumperz
Comment Utility
Is your frame type set to auto? I so try the other 2 options.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Hmmm...Let's start all over...(Have those ethernet card drivers handy on a disk as well as your Windows 95 CD.  Also, ask AOL to send you a copy of their software, if you don't have one lying around to reinstall.)

Delete EVERYTHING from the Network control panel.  Click OK to close the window, but DON'T restart.

Open the System control panel.  Make sure that "Network adapters" is not present in the second tab (Device Manager).  If so, double-click it and delete those items.

In the same area at the bottom, click on Refresh.  If nothing happens, try it again.  Repeat, if necessary.  The "Update Driver Wizard" window should appear, and ask you to insert the disk with the ethernet drivers on them (if it detects the ethernet card).  (If it says that it can't find certain files, try "a:", "d:", "c:\windows", and "c:\windows\system".)

If it doesn't detect the ethernet card, restart your computer, and try the "Refresh" again, if you haven't gotten any prompts at startup.  If still nothing, you will need to use the "Add New Hardware" in the Control Panels.

Once the ethernet card drivers are installed, your Network control panel should automatically have several items installed, including MS Networking, IPX-SPX compatible, and NetBEUI.  (Restart to "enable" changes.)

If you do this to all the computers, each should be able to see each other.

Explanation:
  Windows 95B is a bit funny/picky in handling driver installations.  If they were installed incorrectly the first time (or subsequent times), they tend to become problematic and its BAD "signature" is retained in the registry.

I hope this helps (and I didn't forget any steps;  I'm doing this from memory).  If it doesn't work, let me know, and I will, personally, do this on my two computers at home.  (I need to do it, anyway, but haven't had the chance.)

--MikroData (jkjung)
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
You may want to leave one computer alone, so you can get back to us with the results.

--MikroData (jkjung)
0
 

Author Comment

by:MJCSR
Comment Utility
comment to MikroData (jkjung)
I have gone through all the steps you have laid out
guess you need to try this at home or elsewhere
the following is the information i have on my computers to set up
still each only recognizes itself within the work group inside
the entire network plus one shadow of itself under entire
network
Still can see hub lit with good connection signal light and each
computer says its network card is operational.
again HELP

NETWORK NEIGHBORHOOD “ENG”

eng is my computer, AGM, ACCT and COMM are the others only
working with ENG and AGM at this time)

Client Ms Networks
      Quick Logon

AOL Adapter
      Driver Type
            Enhanced mode (32 bit and 16 bit) NDIS Driver
      Bindings
            TCP/IP -> AOL Adapter
SMC EtherEZ (8416)
      Driver Type
            Enhanced mode (32 bit and 16 bit) NDIS Driver
      Bindings
            IPX/SPX-compatible Protocol -> SMC EtherEZ (8416)
            NetBEUI -> SMC EtherEZ (8416)
      Resources (only shows on my computer “ENG”)
            Configuration type:
                  Current Config
            I/O address range:
                  240-25F
            Interrupt (IRQ):
                  10
            Memory address
                  C8000-CBFFF
IPX/SPX-compatible protocol -> SMC EtherEZ (8416)
      Bindings
            Client for Microsoft Networks
            File and printer sharing for Microsoft Networks
      Advanced
      Force Even Length Packets
                  Yes
            Frame Type
                  Auto
            Maximum Connections
                  10
            Maximum Sockets
                  2
            Network Address
                  0
            Source Routing
                  16-entry cache (recommended)
Set this protocol to be the default protocol.
                  Unavailable
      NetBIOS
            Unchecked
NetBEUI
      Bindings
            Client for Microsoft Networks
            File and printer sharing for Microsoft Networks
Advanced
      Maximum Sessions
            10
      NCBS
            12
      Set this protocol to be the default protocol
            Available (checked)

TCP/IP -> AOL Adapter
      Bindings
            None
      Advanced
            Property:
      None
            Set this protocol to be the default protocol
                  Available (not checked)
            NetBIOS
                  I want to enable NetBIOS over TCP/IP
                        Available (not checked)
            DNS Configuration
                  Disable DNS (checked)
            Gateway
                  Empty (Available)
            WINS Configuration
                  Disable WINS Resolution (checked)
            IP Address
                  Obtain an IP address automatically
File and printer sharing for Microsoft Networks
      Advanced
            Property:
                  Browse Master
                        Automatic
                  LM Announce
                        YES


0
 

Author Comment

by:MJCSR
Comment Utility
Adjusted points to 275
0
 
LVL 3

Expert Comment

by:jjmartin
Comment Utility
I know I have said this before, but I think you have the wrong cable type somewhere.  This sounds EXACTLY like the problem I had.  I worked for weeks, uninstalling and reinstalling drivers and software.  Then, I changed cables, and it all instantly worked.  Take a couple of PC's, put them right next to each other and hook them togtether with a new cable, card to card.  Try a couple different kinds.  I know you said you didn't have the resources to rewire the building, but at least this would identify if that was the problem.
0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
Wheee!  This has been a long history of notes to read through.

Here's my piece:  I don't like IPX/SPX for MS File sharing.  It just causes problems.  I've had best success with TCP/IP, which has been previously almost unmentioned here.

I'd suggest adding TCP/IP so that it's bound ( -> ) to your SMC cards.  Select a block of dummy address (since this isn't on the Inet anyway) and give each PC it's own address.  I like to use 111.111.111.xxx because it's quick to type.  :)

Set the subnet mask to 255.255.255.0 on all machines and give them each a unique address (111.111.111.1, 111.111.111.2, ...).

Make sure (if you're using OSR2) that "I want to enable NetBIOS over TCP/IP" is checked.

Also, make sure that "Set this protocol to be the default protocol" is checked (at the bottom of the advanced tab) for your TCP/IP -> SMC card.

On the Bindings tab for your TCP/IP -> (AOL Adaptor and/or Dial-Up adaptor) make sure to *uncheck* both Client for MS and F&P Shareing for MS.  It may whine about things, but don't let it dissuade you.

Remove all traces of IPX/SPX from all the machines.

Make sure that all machines have F & P Shareing for MS Nets and that they all have "Browse Master" set to "Auto".

Best of luck!
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
I GOT IT!  *Charlie waving his golden ticket.*  We all missed the OBVIOUS.  (I would post this as my answer, but I can't now.)

When you have MS Networks installed, there should be a second tab, called "Identification".  Each of the computers should have a unique "Computer Name".  However, EVERY computer needs to have the SAME "Workgroup" name.  You can leave the "Comments" blank.

I still haven't tried it on my computers, yet, but try this, first.  I'll try it on my computers after hearing the results.  I hope this helps.

--MikroData (jkjung)
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to MikroData (jkjung)

Sorry wrong again
all computers have different names:
ENG
AGM
ACCT
COMM
All computers have same work group:
LAPE
all computers have different descriptions:
MJCSR
DM
SK
JL
will try the proposed answer above but i belive we already went TCP... with erors but not assigned address
thanks
MJCSR
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to : shermanj
will try this proposed answer and keep my fingers crossed (until i need them that is)
thank you
Michael
MJCSr
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to shermanj
well i have tried it out (your proposed answer)
unfortunately still no recognition of other computers through
network neighborhood (WIN 95)
i even went further and tried both systems as servers, desk tops and alternated desk top and server without results.

boy yhis is getting heavy hope EE has a large enough data file system for this question's logs of ccomments and answers.
hard to believe been at this for mostly 20 days ( 3 mos prior to
the discovery of EE though)

well lets sharpen some more pencils and clean our lenses some
more because i am going to have to reject this as an ansered
solution also

Michael
MJCSR
0
 

Author Comment

by:MJCSR
Comment Utility
Adjusted points to 280
0
 

Expert Comment

by:mike88
Comment Utility
Does windows95 prompt you to logon to a network when you boot into win95? If yes, can you see yourself in network neighborhood? If yes, well your driver and win95 is talking to your NIC.   Next enable all shares.  If still not working, try with just this three components in the Network Property in of one system; MS Clients,  EZ-8416 and Netbeui(use just Netbeui in all machines). If that still doesn't work you have problem in between the system and not the setting in windows95.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
If you haven't done anything to the setup since 7/21/98, I think that all your drivers are properly installed.  You may just need a bit of tweaking.  For the heck of it, in the Network control panel, click on "File and Print Sharing".  Make a check next to "I want to share my files." (or something to that effect).

If that doesn't work, you need to put two computers next to the hub, and use two cables.  Instead of connecting them up to the jack, connect them DIRECTLY into the hub.  This will eliminate the possibility of an overrun of wiring.  (I don't know how the telephone company tested the wiring--I've seen idiots come out to look at problems--, but I believe they use tone testers.  That really doesn't tell how much degradation of data is happening.)  I know that it's only a two-story building, but I want to eliminate this possibility of the building contractor making a mistake or something.

I will try to make time to hook up my home LAN tomorrow to help you.  I hope this helps.

P.S.  Where are you loacated (city/state)?

--MikroData (jkjung)
0
 
LVL 1

Expert Comment

by:johnsand
Comment Utility
 To have all the computers communicate with each other, there are only 4 software requirements:
    You need these installed.
        1. Client for Microsoft Networks
        2. Adapter Driver
        3. Netbeui
        4. File Sharing must be turned on (And Printer if you want to share printers)

    A problem I have seen many times is if you have a "Combination" card (one that has Thin Ethernet, Thick Ethernet, and RJ-45) connections or any combination of the above. The cards default to Thin Ethernet (coaxial connection).   Run the setup for your card and make sure it has the RJ-45 connection enabled and selected as the default.  If the card driver is natively built into 95, then the option for connection type should be under the advanced tab of the driver. Also, if it has the option for Auto-Detecting the connection type, then force it to RJ-45.  I have seen this fail also..

Hope this helps...
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to --MikroData (jkjung)
"File and Print Sharing".  done so
phone company ran wire in existing building (barn storage shed)
came back out and retested after installed
Ocean Springs, MS LapeEng@AOL.COM or MJCorzineSR@Yahoo.COM
thanks
looks like we have another explorer on site will give : johnsand
a try at problem resolution
truly

Michael
MJCSr
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 

Author Comment

by:MJCSR
Comment Utility
Comment to all
veiwing my Autoexec.bat file i have found some disturbing information but am unsure if this may be affecting these systems

rem - By Windows 95 Network - C:\WINDOWS\net start
rem - By Windows 95 Network - C:\WINDOWS\net start
rem - By Windows 95 Network - C:\WINDOWS\net start
rem - By Windows 95 Network - C:\WINDOWS\net start
rem  - By Windows 95 Network for Netware Upgrade - C:\WINDOWS\lsl.com
rem  - By Windows 95 Network for Netware Upgrade - C:\WINDOWS\smc8000.com
rem  - By Windows 95 Network for Netware Upgrade - C:\WINDOWS\odihlp.exe
rem  - By Windows 95 Network for Netware Upgrade - C:\WINDOWS\ipxodi.com
rem  - By Windows 95 Network for Netware Upgrade - C:\WINDOWS\netx
rem - By Windows 95 Network - call C:\WINDOWS\SYSTEM\_nwnds.bat C:\WINDOWS\SYSTEM
SET MSINPUT=C:\MSINPUT
rem - By Windows 95 Network - call C:\WINDOWS\SYSTEM\_nwnds.bat C:\WINDOWS\SYSTEM
rem - By Windows 95 Network - call C:\WINDOWS\SYSTEM\_nwnds.bat C:\WINDOWS\SYSTEM
rem - By Windows 95 Network - C:\WINDOWS\net start
REM - by MS DLC 32 - C:\WINDOWS\dlchlp.exe
rem - By Windows 95 Network - call C:\WINDOWS\SYSTEM\_nwnds.bat C:\WINDOWS\SYSTEM
rem - By Windows Setup - lh C:\WINDOWS\COMMAND\MSCDEX.EXE /d:mscd001
REM C:\CDROM\MSCDEX.EXE /D:MSCD001




SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\WINMCAD;C:\Marks


0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
Wow!  That's some wierd crap!  It's caused by trying to run NDIS2 or ODI network interface card drivers.  Been fiddling with your NIC driver settings?  ;)  Just leave it set to NDIS3.  32 and 16 bit NDIS driver.
0
 

Author Comment

by:MJCSR
Comment Utility
Additional comments to all

SMC EtherEz SuperDisk test results for System 1 (ENG)

Network Interface Failed ( Selection Unresolved) details to follow

LAN Controller is unable to transmit a packet.
Perhaps the LAN cable is not properly terminated.
Two options available

A. run  NO CABLE ATTACHED
        Loopback test Passed
B. 1. Run Attached Network Cable
        Loopback test failed
   2. Run Attached test Cable  
        for 10BASE-T attach an ISOLATED CONCENTRATOR
      (UNKOWN REFERENCING)

Michael
MJCSr


0
 

Author Comment

by:MJCSR
Comment Utility
comment to johnsand

well i have set each system up again and still no communication between any of the systems.
in addition i have ru a diagnostic on the SMC card
after which i had removed system 1 from the hub attachment
(hub still recognized system 1 as tied into it ??)
after disconect lited hub began to blink ocassionaly.
checking each other system i was unable to log onto network neighborhood but was able to search for other computers
system 2 finds itself and system 4 but does not see system 4
system 3 finds itself and system 4 but does not see system 4
system 4 finds and sees itself only

still have a mess of confusion will now run diagnostics on SMC card on other systems and see what is said then

at this time i will have to reject answer given as being unresolved

thank you and hope that you can continue with your assistance

Michael
MJCSr
0
 

Author Comment

by:MJCSR
Comment Utility
Adjusted points to 285
0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
Ummm... what is the distinction between "finds" and "sees"?

That message it gives about not being properly terminated sounds like it's trying to use 10base-2 (thinnet).  See if there's a settingin the NIC config software for TP (Twisted Pair) versus BNC or AUI.  May also show as 10base-T, 10base-2, and 10base-5, respectively.

Try setting TCP/IP back up (if it's not still) per my previous instructions, and see if you can "ping localhost" or another address on your LAN.  If you can't ping localhost, something's wrong with the software.  If you can ping localhost, but can't ping another address, you've got a hardware problem.  That'll get our discussion narrowed some, anyway.  Please post the results of "ping localhost" and "ping 111.111.111.2" (assuming you're running this on 111.111.111.1).
0
 

Author Comment

by:MJCSR
Comment Utility
comment to shermanj

find a computer / or files
sees a computer (those that are shown under network neighborhood
(NIC?)
through dos
c:\ping -a 111.111.111.1
bytes=32 time<10ms ttl=32
bytes=32 time<10ms ttl=32
bytes=32 time=1ms ttl=32
bytes=32 time=1ms ttl=32

c:\ping -a 111.111.111.2,3,4
request timed out
request timed out
request timed out
request timed out

in addition i have replaced cable for system 1
and still recieve the same error message
loopback test failed
cable not attached

Michael
MJCSr

0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
Okay, with those ping results it *MUST* be a hardware problem.  Bad cables, NIC's (Network Interface Card), hub, or bad configuration of the NIC(s).  Is the card a combo card (supports different types of cableing)?  If so, did you check the media type setting for the card?  Should be 10base-T or TP or Twisted Pair or some such.

You might try a 3Com NIC card.  They cost a little more, but you get your money's worth: very reliable.  Get one that's TP only.  That way, there's no worries about media type settings.  :)

See if the cables run past any flourescent lights or transformers: things that can cause lots of interference.  If so, get them away somehow.
0
 
LVL 1

Expert Comment

by:johnsand
Comment Utility
 That sounds like an interrupt problem...   Did I read that your settings were I/O 240 and IRQ 10 and Memory at C8000?

  I have had the best luck at   I/O 360  IRQ 5 or 10  and Memory at either d8000 or e0000
  C8000 is normally the start of the High Memory area, and if DOS is loading High, that can cause a problem.
  IRQ 10 is sometimes in use by Add-On cards (my old Mitsumi CD Card used IRQ 10)
  Also, if you are using a Plug & Play system, Turn off Plug & Play for whatever IRQ you are using.  If Win95 doesn't detect your card, sometimes it'll throw your Video Card at IRQ 10. If you set the PNP IRQ 10 as ISA instead of PNP, it will ignore IRQ 10 when moving the cards around.
  Bummer if I'm right here as I won't get any points...  :-(
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to MJCSR:
  I just finished setting up my two-computer LAN at home.  I used an 8-port hub, 2 straight-though RJ45 cables, and 2 generic NICs.  One computer is using Windows 98 (new, Pentium II 300), and the other is 95 w/IE 4 (Pentium 90).  Both computers have AOL and another ISP.
  I had no problems on the computer with Windows 98.  When it came to my P90, it gave me the problem that you described.  I tried the solutions I gave you, and they didn't work.
  Every time I rebooted and Windows started, it would give me a Windows login prompt, even though the Primary Logon was set to "Windows Logon".  I kept dismissing it by pressing ESC, instead of entering any information.  Finally, I entered a username (no password), and my network came up!
  At that time, I was able to see both computers (mine and the other one).  These are my Network settings (for Win95; 98 had the correct Realtek driver):
    Client for Microsoft Networks
    PCI I/O Mode Ethernet Adapter
    Dial-up Adapter
    AOL Adapter
    NetBEUI -> PCI I/O Mode Ethernet Adapter
    TCP/IP -> Dial-up Adapter
    TCP/IP -> AOL Adapter
    File and print share for Microsoft Networks
All the internet settings, here, have been left at default.
  To get yours working, change your Primary Logon to "Client for Microsoft Networks". and Restart.  Upon Windoes login prompt, give yourself a username that you want.  (It's okay to leave the password field blank.)
  Go back into the Network control panel, and this time, change it back to "Windows Logon".  Restart again.
  Windows should prompt you for a username/password.  Give it the same one you just created.
  Once your at the desktop, open up the Network Neighborhood, and you should be able to see everyone.

I hope this helps.

--MikroData
0
 

Author Comment

by:MJCSR
Comment Utility
to shermanj
I believe you might be correct on the one count of hardware
Bad EtherEz card )problems with system #1
although your proposed answer did not help with solution to the problem presented with other three systems were hardware is functioning
will keep trying at this end to resolve this continuing problem
0
 

Author Comment

by:MJCSR
Comment Utility
comment to johnsand
unfortunately resources will not allow me to change to the specified data. PnP is off, have additional info on systems will post later today
thanks
MJCSr.
0
 

Author Comment

by:MJCSR
Comment Utility
comment to jkjung
looks very familiar am working on set up and have additional info to add later today

Thanks
MJCsr
0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
hmmm... I'd leave the default logon set to M$ client if I were you...  Just have to always log in.  Blank passwds ok, but not blank usernames...  Yeah, looks like jkjung has it there, except that I'd leave TCP/IP attached to the ENet card for debugging purposes...  Your call, though, MJCSR.
0
 

Author Comment

by:MJCSR
Comment Utility
Comment and update to all:
well here is some more confusion to add to the pile of match wood.

From Computer 3 (acct)/ While doing search for computer 4 (Comm), # 4 is found entire network\lape\. upon double click
within the search window I am able to access the shared files on
#4. upon exploring network neighborhood I receive an error message as follows
      EXPLORING NETWORK NEIGHBORHOOD
X      UNABLE TO BROWSE THE NETWORK THE NETWORK IS NOT
        ACCESSIBLE FOR MORE INFO LOOK IN THE HELP INDEX AT THE
        TOPIC “NETWORK TROUBLE SHOOTING”
Also From computer 2 (agm) The same process can be done for #4 and same results.  Also upon exploring netwrk neigh. #4 is not
shown on explore tree In addition neither #3 or #2 will find
each other or recognize each other.

The following is now the operating setup for each system:
System # typical role of machine (computer name\work group\)
(I have tried Net Serv on all and on just one with no change in
 results)
#1 desktop(ENG\LAPE\)// #2 desktop(AGM\LAPE\)//
#3 desktop(ACCT\LAPE\)// #4 desktop(COMM\LAPE\)

    CONFIGURATION
      Client for MS Networks:
            Quick Logon
      AOL Adapter :
            TYPE; Enhanced Mode (32 bit and 16 bit )
                                         NDIS Driver
            Bindings;       TCP/IP -> AOL Adapter
      SMC EtherEZ (8416) :
            Driver type ;       Enhanced mode(32 bit and 16 bit)
                                                  NDIS Driver
            Bindings :       NetBEUI -> SMC EtherEZ (8416)
            The following Resource only appears on #1
            I/O and IRQ are same on all,  
                Mem Address only on #1
            Resources :       I/O :             240-25F
                        IRQ :             10
                        Mem Add :      C8000-CBFFF
      NetBEUI _> SMC EtherEZ (8416) :
            Bindings ;Client for MS Net File and Print Share
            Advanced ; Max Sessions ; 10
                       NCBS ;         12
                  Set as default proto.
      TCP/IP -> AOL Adapter :
            IP Address ;       Obtain
            WINS Conf. ;       Disable
            Gateway ;       EMPTY
            DNS Config ;       Disable
            NetBIOS ;       UNAVAILABLE
            Advanced ;       None
            Bindings ;       None Checked
      File and Print Share for MS NetWrks :
            Advanced ;       Browse Master ;       Automatic
                        LM Anounce ;       Yes
     IDENTIFICATION
              #1      #2      #3      #4
Computer Name : ENG       AGM      ACCT      COMM
WorkGroup :       LAPE       LAPE      LAPE      LAPE
Computer Description :       
               MJCSR       DM      SK      JL
    ACCESS CONTROL :
            Share Level

Well is this a finer mess or what
I did raise the points earlier but looks like i will need to add some more.  hope that this information helps
0
 
LVL 1

Expert Comment

by:shermanj
Comment Utility
LM announce should be NO.  Setting it to yes sends LAN Manager broadcasts, which are worthless in a Win95 only network.  Only affects network performance.

Hmmm... May I suggest...  Back to TCP/IP?  :)  If you decide to try it, please post results of ping and nbtstat commands: (capital A is important)
ping 111.111.111.1
nbtstat -A 111.111.111.1
ping 111.111.111.2
nbtstat -A 111.111.111.2




Nbtstat gets some NetBIOS name information from the NetBIOS over TCP interface, which can be useful in debugging networking problems...
0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
this probably isn't a factor, as it'll take you a while to get between the computers in different rooms, but win95 peer-to-peer computers can sometimes take as long as two minutes to resolve all the computer names and workgroup information between themselves.
  Thought I'd throw it in, as I've done my share of over-troubleshooting due to impatience.  ;)
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Hmm...What happens when you disable "Set as default protocol"?  If there is no change, alternate the default protocol to each of the protocols to see if there is any affect.

kmarf has a point.  Although I don't think this is the problem, give it a try.  Let the computers "sit" there for 10-30 minutes after starting it up.  Afterwards, see if there is any change.

The other day, I was working with a Win95 w/IE4 computer in one gateway to realize an NT Server in a sub-gateway.  It couldn't see it in the Network Neighborhood so that the network printer could be added.  I was, finally, able to use the Find command in the Start menu to search for the server.  The computer name was used as the search string.

I hope this helps.

--MikroData (jkjung)
0
 

Expert Comment

by:Gbeason
Comment Utility
Make sure you don't have any special characters in you computer names and be sure your computers are in the same workgroup.  Also make sure your cards are plugged in.  Some time people look over the ovious.  Here is how we have a win95 network set up.

Also change the Browse Master from Auto to Enabled.

Try to connect to the computer and shared resorces from the run command.  //computer/resorces/

I just looked and you need to have binding checked.
Change the quick logon to Logon and restore.
Try taking out TCP/IP.
0
 

Author Comment

by:MJCSR
Comment Utility
comment to Gbeason
I am in reciept of your proposed answer and will attempt to use this as a resolution to this massive head ache
upon completion I will evaluate and grade

thank you
truly

Michael
MJCSr.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Did you try my suggestion (7/29/98)?  Also, since I think we have all exhausted our suggestions and you want to "resolve" this issue, how are you determining who gets points/a grade?
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to jkjung.

Well believe it or not i did try you suggestions
and so far i have the following info to add:

now on (Comm), # 4 I can see (ACCT) #3 and (AGM) #2 but can not access them, but while on both #3 and #2 i am able to access #4

on (ACCT) # 3 i see only (comm)#4 and
on (AGM) #2 i see only (comm) #4
from (Acct) #3 i can not find (AGM) #2 and again
on (agm)#2 i an not find #3

After changing to the last suggestion of (tcp/ip)
i have lost all contact with #3 and #2 from #4
and #4 from #3 and  #2

so i will be attempting to redo the protocals and try to find these systems again.

as far as the grade i will announce the success of the LAN
and will review all proposed answers i will reopen question, raise the anti one more time and then ask that person (who has supplied the best and close's answer) to propose an additional statement of perhapes (eureka!!) in the form of a question and will then award a grade.
(if this is a succesful resolution then the grade will be an "A")
best of luck to all

thank you
Michael
MJCSr.

0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Hmmm.  It seems that the settings are not the same for all the computers.  Set the settings back to what it was before, so that you can see at least #2, #3, and #4.

In order to access a computer, you should have something shared.  To share an item, right-click a directory and select Sharing.  In that window, mark Shared.  You don't need to modify the Shared Name.  Click Apply, then OK.

I hope this helps.

--MikroData (jkjung)
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
P.S.  I sent you an e-mail.
0
 

Author Comment

by:MJCSR
Comment Utility
Well it seems that we are getting closer still yet.
reset all systems and this is what i have now

Syst #1 (ENG) at times sees all other systems and then at times only #1 (ENG) and #4 (COMM
Upon trying to explore all other sytems (when the icons appear)I receive error message as follows
EXPLORING -ACCT, -AGM
“X the computer or share name could not be found!
    Make sure you typed it correctly, and try again!”
Syst. #2 (AGM) reads only #4(Comm)
Same error message occurs when find or run commands are used
Syst #3 (Acct) reads only # 4(Comm)
Same error when find or run commands are used
Syst #4 sees all syst but can not access any at all
All systems are set with same parameters


In order for me to send info from #1 or #2 to #3 I must go VIA #4
To send from #3 to #1 or #2 VIA #4 also
Seems that (#1, #2, #3) can read #4 but not each other and that
#4 can not read any

so we have gotten closer and if we can get this resolved soon
it should be good for all

MikroData

I got got your EM thanks but hope that we can resolve
this some other way
besides you probably would not like the sandy beaches, tourist and casinos that are so abundant on the Mississippi Gulf Coast

Thank you
Michael
MJCSr


 



0
 

Expert Comment

by:Gbeason
Comment Utility
So Why did you reget my answer.  Now that I have set up 2 12 comptuer networks I with the same proticals that have been tried, I have to say that it must be the hub (no computer sees each other and if it were a cable or card problem, then it would the other computers would see each other.)
   Why don't you try taking moving two computers together and then connecting them directly to the hub.  Then change the hub.  I know that hubs are a little expensive but for 50 dollars this would be worth it.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
At this point, the only thing I can think of (because I am not there in person) is that there are MINUTE differences between the setup of each of the computers.  My suggestion is to back up all data, format (not quick) the drives, then set up (as closely as you can) Windows 95 on each of the computers.  You should not install anything else (third-party drivers, programs, etc.), until you have gotten the computers to successfully see each other on the network.

I hope this helps.

--MikroData (jkjung)

P.S.  I don't see why I would "not like the sandy beaches, tourist and casinos".  This type of scenery is commonplace in Southern California.
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to Gbeason

the reason I rejected your answer is the same reason that I have rejected the others ( MY SYSTEMS ARE STILL NOT FUNCTIONING PER MY ORIGINAL REQUEST)
that aside I belive that you have been close to the answer so far and i will have this hub rechecked as only on occasions do i see activity (blinking lights)

thank you
Michael
MJCSr
0
 

Author Comment

by:MJCSR
Comment Utility
comment to jkjung

I will also try your proposed resolution but will first verify that the hub is not the problem.

Thank you
Michael
MJCSr

ps. Missouri area as you originally stated does not have many "sandy beaches, tourist and casinos" that I know of perhaps river front or lake front but not like the salty stuff.
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to all

I have tried to change work group
"LAPE" to "Lape" and this does not seem to make a difference
all computer names are in CAPS but read IE Eng, Agm, Comm, Acct
additional question
does it make a difference if each computer is set up as a server or as desk top?
came accross another error message that says "SERVER//Comp. not accessable"?

Thank you all
MJCSr.
0
 

Expert Comment

by:eventus
Comment Utility
gee ! Go back to the roots ! At ftp://www.smc.com/pub/nics/ethernet/8416/gsd310.exe you can download all the drivers for the 8416 card. Start 2 of your PC´s in dos mode and run the diagnose tool setting up one pc as initiator and one pc as responder - do these pc´s find each other ? if not you have a hardware (most likely cabeling or irq / io trouble) otherwise it is in deep a software problem. It might be helpful if you watch the lights on your hub while doing this - it tells a lot about where the problem is.
0
 
LVL 1

Expert Comment

by:notanexpert
Comment Utility
I know I'll get killed for this superflous comment, but uh ... try Macs with AppleShare IP? ;)
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to notanexpert:
  Actually, with Macs, you won't need AppleShare IP.  AppleTalk networking works out-of-the-box with its personal file sharing.

Those iMacs are nice.  I demoed them for Apple the other day.  They would work nicely for what MJCSR wants to do, but he probably doesn't want to spend $1299 x 4.

--MikroData (jkjung)
0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
As long as we're throwing comments that may get us shot...
Set up a peer-to-peer windows network today - easiest thing I've ever done.  It was win98, believe it or not.  For whatever reason, they've done marvels.  Now, this may not apply at all to the older SMC cards, but score 1 for (to balance the few dozen against) win98.
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to kmarf:
  Windows is only easy when it works.  I'm not going to drink to the more-than-many times it DOESN'T work.  I only agree that Windows 98 is more stable and has more support.  However, I've patched up Windows 95 so much that it thinks/works like it is 98!
0
 

Expert Comment

by:TheDragon
Comment Utility
1st thing to do is to make sure your network is working:
All network cards(all I've worked with) come with a dos utility to check/config the network.  This utility usually can act as a client(Receiver-RX) or a server(Transmitter-TX)
Shut down to dos(not dos window)(sidenote: above when u try to use "net start" and "net use", that too has to be done from dos, not dos window).
run this utility, set one machine to be the transmitter and others to be receiver.  Usually you will see a packet counter on server showing number of packets sent.  Receiver will show packets received and possible speed of network.
If this works, then we can assume your network works.
If it doesn't:
try different machines as transmiter
check back of card for flashing led, if it has a led.
also chek hub for flashing led
if you have led's and none of them are flashing when they are in trasnmit mode. Then I would next check the IRQ setting on the network card.  Many of the cards are software programmable through the set config program you are using to test network. Some are jumper programmable. some are both :)
irq 10 is usually a good one to use. and 0300 is usually a good base address

Anyway If the network test does work then your problem is in windows.  I will help you with that after I hear your result of this.

TheDragon

0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Some hubs/switches may be VERY particular on the wiring that you use.  I had switched from a hub to a Cisco switch, and half of my cables didn't work any more.  If I wiggled it around in the port, it may give me a link, though some stations still couldn't access anything.  I had no problems when I moved it back to the hub.  (A LED on the hub/switch/card is meaningless, unless you perform further tests.)

I hope this helps.

--MikroData (jkjung)
0
 

Expert Comment

by:acoker
Comment Utility
Please excuse if this has already been mentioned, I only scanned the above text after the first 20+pages.

Try using only netbeui protocol bound to the nic.  ensure that other computers on the network have a shared resource.
0
 

Author Comment

by:MJCSR
Comment Utility
in Review of recent comments
0
 

Expert Comment

by:timothymarsh
Comment Utility
I will go through what you will have to do to get the network up and going please bear with me.

First in the network control panel delete everything except your networkcard driver.

Add the following components
*NetBEUI   (add,protocol,microsoft,netBEUI

click File and Print Sharing button
Select both click OK
double click the component for you net card, click the bindings tab, make shure only netBEUI is selected click OK
now double click the netBEUI component make sure all are selected
Close network control panel restart if needed
Open MY COMPUTER right click drive you want to share, click sharing, change apropriate settings ,close
restart
Do same on all machines
goto network neighbourhood
suprise succes

0
 
LVL 1

Expert Comment

by:kmarf
Comment Utility
apologies as usual if this has been brought up and I missed it.
Are these RJ-45 only cards (if so, nevermind)?  If they're combo, have you specified the adapter type in both the card and windows?  
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to timothymarsh:
  Did you even READ _any_ of the comments before posting your answer?

--MIkroData
0
 

Author Comment

by:MJCSR
Comment Utility
comment to timothymarsh
sorry but all of that has been tried back in the very begining
please take the time to read the most recent of entries and rejected answers

comment to all
well we are back on line so to speak now that the
Himmacane has passed

will be setting systems back up this week and hopefully be able to start again

thanks to all for your patients

MJCSr
Michael
0
 

Author Comment

by:MJCSR
Comment Utility
already tried and failed
0
 

Author Comment

by:MJCSR
Comment Utility
comment to kmarf
yes i believe that all of them are RJ-45

MJCSr

0
 

Author Comment

by:MJCSR
Comment Utility
comment to jkjung

thanks

MJCSr
0
 

Expert Comment

by:MoonlightMedia
Comment Utility
This is a real SAGA ! I have reviewed all of the advice you have received and although
most of it is technically correct and well thought out, it doesn't address (although it
was suggested) your real problem. Troubleshooting any problem is almost an artform.
You need to simplify your situation as much as possible. I would suggest that you stop
trying to get four computers to talk and just try to get two of them to talk completely and
correctly. Connect DIRECTLY to the hub with RJ45 CAT 5 cables. If you don't trust what
you have -- Buy New Ones ! Use the information everyone has given you to set up
the simplest form of networking you can. Use NETBUEI - I don't care if it's slow or
inefficient, IT WORKS. Lose the AOL adapter until you can talk between two systems.
Run the diagnostics on the NICs and then between the two computers. If the hub
doesn't show activity there is a problem - many NIC's have activity indicators right on
them - Are thes lights blinking when you send or receive ? If you can't make it work
with the hub, get a null (reversed on one end) cable and try it directly without the hub.

I've spent lots of my life wandering in a forest and unable to see the trees. If you don't
simplify this, you will be here for a long, long time. Everybody gave you great advice
but what your not getting is a simplified approach to a problem. If you can find out
what does work, the bad apple will fall out of the tree, probably right on your head.
0
 

Author Comment

by:MJCSR
Comment Utility
Comment to MoonlightMedia
thanks for the advise
now that all my systems are being re-started from new
(thanks to the him-a-cane) i will hopefully be able to adjust and tweak this puppy through
although i am able to read from
eng to comm and
agm to comm and
acct to comm and
comm to eng
but
still not read from
eng to acct or
eng to agm or
agm to acct or
agm to eng or
comm to acct or
comm to agm or
acct to agm or
acct to eng or
acct to comm

will try to debug this over the following week

thank you
MJCSr
Michael

0
 

Author Comment

by:MJCSR
Comment Utility
Comment to MoonlightMedia
thanks for the advise
now that all my systems are being re-started from new
(thanks to the him-a-cane) i will hopefully be able to adjust and tweak this puppy through
although i am able to read from
eng to comm and
agm to comm and
acct to comm and
comm to eng
but
still not read from
eng to acct or
eng to agm or
agm to acct or
agm to eng or
comm to acct or
comm to agm or
acct to agm or
acct to eng or
acct to comm

will try to debug this over the following week

thank you
MJCSr
Michael

0
 

Author Comment

by:MJCSR
Comment Utility
THANKS FOR THE INPUT BUT BELIVE THAT YOUR ANSWER IS A COMPILATION OF ALL THAT HAS BEEN PROPOSED TO DATE
THANKS
mjcsr
0
 
LVL 1

Expert Comment

by:jb123
Comment Utility
After reading this whole thing, I would just like to say as a relative newcomer to EE that I am extremely impressed with the willingness of everyone to help this man out. I've met some jaded people in this business but you guys are the best. It's too bad it doesn't work this way, but those who've kept with it should all get the points. Bravo!
On the technical side I would add just one thing - don't trust Device Manager to show hardware conflicts. Open the properties of the device (NIC in this case) and go to the Resources tab. I've seen many times an indication here that there is a conflict that didn't show up as a yellow exclamation point in the Device Manager window. This often happens when a NIC comes from the factory preset to an IRQ but is installed with a different one. Yes, this even happens in the world of plug and play if the person installing is not paying attention.
0
 

Expert Comment

by:ricardopascual
Comment Utility
On networking only and assuming your network cards work:

if you are not using Novell then scrap IPX/spx and just use TCP/ip set each computer with an Ip address as follows:
123.123.123.1
123.123.123.2
123.123.123.3
123.123.123.4 etc etc
subnet mask for each should be 255.255.255.0
make sure your c:\drives are shared.
Restart the machine
once back in windows
in the dos command of one of the machines type:
ping 123.123.123.1
or 2 , or 3, or 4 etc etc

if you get a reply for any of these then the machine can see that machine if you get a timed out then the machines cannot see each other and you have to look at the your cabing/cards/hub situation if not

map a drive in network neighbourhod
\\123.123.123.3\c
you should see the drive


0
 
LVL 2

Expert Comment

by:jagoodie
Comment Utility
do you need tcpip? if not just use netbeui, it does not require configuration and will get you going faster (it was built for small lans).
do share something though- good advise.
0
 
LVL 2

Accepted Solution

by:
jkjung earned 400 total points
Comment Utility
Disconnect all devices from all the COM ports.  From the System properties' Device Manager tab in the Control Panels, disable _all_ COM devices, located in the Ports section.  After disabling them, click on "Refresh".  If any other ports are found, disable those too.

You want to do this, because COM ports, sometimes, tend to use resources necessary with other devices, such as your network or modem cards.

Once you get both of them at satisfactory levels, reenable one COM port at a time, making sure that they don't use the same (or have conflicting) IRQ, DMA, or I/O Range as any other device.

I hope this helps.

--MikroData
0
 
LVL 2

Expert Comment

by:jkjung
Comment Utility
Comment to jagoodie:
  Why are you adding load time to our web browsers?...Please READ the MASSIVE log.  This message already too long--LOG[ged]OUT.
0
 

Author Comment

by:MJCSR
Comment Utility
Ureekkaa!

com ports was the solution to the problems encountered
seems that an outside program (add on) was selecting the com port equired for the ethernet this affected and infected the systems trying to use it

well this has been a saga we could write a novell (best seller )
about

thank you one and all for the informative responses and the continued support throughout this ordeal

yours truly

Michael J.  Corzine,  Sr.
MJCorzineSr@yahoo.com

next questions will involve inter office postoffice
with MS outlook 98
this is a new one and perhaps some of you could get a jump on this one

MJCSr
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Suggested Solutions

FIPS stands for the Federal Information Processing Standardisation and FIPS 140-2 is a collection of standards that are generically associated with hardware and software cryptography. In most cases, people can refer to this as the method of encrypti…
The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now