Home Networking Problems

[TCarff]

I have been trying to connect 4 computers at home. I was given 3 isa RealTek nic cards and can't get them to work. I bought 2 pci netgear cards and a netgear hub. The computers with the netgear cards work fine. But the computers with the RealTeak cards don't. The cards install fine and win98 says they're working fine, but all they see in the network neighborhood is themselves. I've tried just connecting 3 together (one 1 using a Realtek card) and that doesn't work. I've tried replacing the RealTek card with another one. Always the same thing. Tried using NE2000 Compatible driver, as well as the driver for the card on the win98 CD, as well as the win98 drivers on RealTeks site. Nothing works. Anyone have any ideas?

[Eccentric]

Network Neighborhood is not a good place to see if you network is operational. Reason being is unless you have File an print sharing enabled then there will not be anything in there. Go into Control Panel, Network, Access Control, and enable File and print sharing.

[TCarff]

Been there, done that. I have file sharing on all my computers. What is another good way to see if the network is operational?

[Eccentric]

Two ways I know of. Most NIC cards have LED on them which usual flash green if working. Try ping tests. If you're using TCP/IP try pinging one of the other machines IP's. If it works, then it's operational. If it doesn't then it's not.
Using NetBEUI. Share some files on the machine that's working. Then try to access them on the machine that's supposedly not working using this syntax:
//<computer>/<path>
replacing computer with the NetBEUI hostname.

What protocol are you using? NetBEUI, TCP/IP, IPX/SPX?

[TCarff]

I'm using TCP/IP, and yes I have that setup right. The 2 computers work fine and I can they can ping each other. The link LED comes on the card and the hub, so there's a link. Then the activity light does some blinking along with some of the other connections on the hub (like they are talking to each other) but that's about it. I've tried pinging from the machine that doesn't work, but not pinging that machine from another one.

[hackerheadquarters]

I'm having the same problem. Anyone know of the solution. Would it having something to do with the network cards. 2 being 10/100 fast ethernet, and the others only being 10based

------------------
JuSt Do It
* *
** **
******
****
**
hhspprt@yahoo.com
http://www.geocities.com/SiliconValley/Station/3512

[TCrom]

This may seem trivial, but have you checked the cables for the two computers that DON'T work. Try switching the cables with two that you know work. The only other thing that I can think of is that maybe you need to set the default protocols on the two RealTek cards or that there may be a conflict with the addresses.

[tfarley]

I am not sure about the netgear hub, but a hub must be autosensing to pick up the different speed nic cards like TCrom said.

[crackerboy]

Like Eccentric noted, make sure you have the netBEUI protocol installed and enabled on all machines. That was my problem just the other day. Good luck http://www.hardwarecentral.com/discussion/smile.gif

[bserviss]

Another trivial reply - I remember reading in my setup docs that in order to see all the computers the "workgroup" has to be the same for everyone on the network. This info is listed in the Control Panel->Network->identification.

Hope this helps!

B

[Eccentric]

Network Neighborhood uses NETBEUI! If you want to see all of the PC's they need to all have NetBEUI installed, be indentified under the Identification tab. They don't have to be in the same workgroup, It's just that you have to click on entire network to see them if they're not in the same workgroup.

[aab101]

Hi--actually, NetBEUI does not have to be installed & bound to the NIC in order to "see" the other computers in Network Neighborhood. NetBEUI & TCP/IP are simply different protocols that can be used. However, some believe that NetBEUI is easier to use than TCP/IP since you don't have to worry about IP numbers; but, if you want to share an Internet connection, TCP/IP has to be installed (often in conjunction with NetBEUI).

[This message has been edited by aab101 (edited 02-21-99).]

[Eccentric]

You're right. Actually and logically it doesn't have to be installed. As long as you have TCP/IP, IPX/SPX, or NetBEUI installed then Network Neighborhood should have no problems resolving and identifying NetBIOS names. However, the fact of life is that on 75% of computers I've used Network Neighborhood doesn't list computers without NetBEUI installed. Crackerboy had this exact same problem, and I advised him to install NetBEUI, and all of his problems whisked away. Maybe it was a coincedence? Or maybe it was Micro****.

------------------
Eccentric
"Content Unix User"


[This message has been edited by Eccentric (edited 02-22-99).]

[TCarff]

Well I installed NetBEUI on my computers. I still didn't have any luck. The computer that wasn't being seen, could be seen by the other 2 computers, but it still couldn't see them.

[Tanner69]

You might want to try to enable browse master in the properties for netbeui. it is defaulted to automatic, but for me it didn't work. When i turned it on and rebooted i was all good and could see the other computers.

[TCrom]

You might also want to check to see that the same protocol is the default on all the computers by checking the 'make default' box.

[TCarff]

I don't have browse master under the properties for netbeui. It gives me 2 settings but they are numbers.

[TCrom]

At times I wonder why the HECK I'm going into this field as a profession!!!!!!!!!

[beatle]

Just a thought, on impulse from your last post TCrom: I was first exposed to the wonders of digital computing ~17-18 years ago and was impressed. It wasn't until ~14 yrs ago that I got my hands on some "real stuff" & became able to generate stuff that was useful to others (via BASIC). Got interested in that for awhile right about time 1st versions of Windows & Quarterdeck were taunting us w/visions of real multitasking (which for most people meant being able to do something else while you waited on a print job). This environment spawned the desire to equip my BASIC programs w/a "foolproof" user interface and I did manage to generate a suite of well log conversion programs w/a reasonable interface - the code to perform the actual functions of the suite represented ~10 lines out of ~1800. I got a book called "Supercharged Graphics" & learned how to setup a menu bar w/drop down menus that was "mouseable". Somebody then gave me a C compiler & I 1st envisioned a future in ranching 1's & 0's .After getting out the standard "Hello World" I realized that I needed to know how these things can work for us (in a very real time sense), but also realized that I am not of the personality to do that full-time. We (my partner & I) still rely on what I can figure out & we have things working, but I long for the day when that can be somebody else's job. I enjoy a victory over the inscrutable digits - and I realize we wouldn't have survived what we have w/o what I've learned (very important part here, pal) - but I realized after the first rush (or 2nd...) of thrill of understanding just what we can do w/these things, that being there maker/keeper was not my ultimately rewarding position vis a vis the beige babies.
Boy! Did I have some time on my hands tonight or what?

[TCrom]

Beatle,
Boy....did you have some time on your hands or what........So you've been doing this for how many years?? I spent the better portion of my last 20 in the military. Worked for a Market Research company for a few years ,while tinkering with computers on the side, and for a parts manufacturer until I recently decided I wanted to make these THINGS talk to each other. So far so good, and the market for us isn't slowing down. Here's to you and to me and to another 20 or so......

[This message has been edited by TCrom (edited 03-02-99).]

[ducttape]

If you're using TCP/IP you could try making a host table for all the machines. Also, sometimes a computer won't work properly in Net Hood if they aren't actually sharing anything. Try setting a folder to share. These are just some of the things that have worked for me in my experiences with Net Hood.

[rktech]

I had a problem similar and found that matching the IRQ's on the network card was the way to made it work. Go to control panel/system/device manager and change the setting. Be sure to pull out the conflicting device and reinstall it after you make the change. Mine congflicted with the modem. My Irq's were set at 10 or 11 and this solved the problem.

[timbo]

Just thought id clarify a couple of things:
NetHood filesharing (uses SMB protocol) works
over TCP/IP through what is called protocol encapsulation. SMB protocol is actually "hidden" inside the TCP/IP protocol. Thats the way samba (linux SMB equiv) can talk to each other with SMB over the internet (TCP/IP).
Also, no ammount of fiddling around with nethood settings will solve your problems if
you cant even a simple ICMP packet to the problem machines. Mess with your card settings, as they are most likely the culprit.

[TCarff]

Well I thought I'd let you all know that I just bought a new network card and didn't have any problems. Once installed the 3 computers saw each other right away. Thank you all for your help.

[Ludwig]

I'm new to networking... I just want to ask... could I use the UTP (RJ45) connector to connect two PCs, using a twisted-pair cable? Or do I still need a hub? Or should I just use the BNC (coax) connectors?

The PCs have both BNC and UTP connectors (combo), I prefer to use the UTP thus a cheaper cable, if possible. Please help ASAP. Thanks

[ducttape]

You don't need a hub. You can do it with a cross over cable. A normal cable won't work.