In need of LAN help...

[Pace]

Yeah, try typing \\KruzinsPC into address bar (if you've got IE).

And can you ping either machine from each other?

Is it only Network Neighborhood that don't work? Does any games etc. work?

Paul.

[Electric Amish]

I was going to mention the same thing as Pace..

Try to ping each other.

My friends and I use Realtek's in our network. My friends SWEAR that the Realtek's are crap...now...Since we've had a couple of network problems that sound just like yours...

We never figured out exactly what the cause was. We had 2 machines that wouldn't talk to each other. They'd ping, and show up on network neighborhood, but you couldn't transfer files...

I would try the uninstall/reinstall as well.

There is also a documented problem with the Realtek drivers in 98..I read is somewhere, it supposedly corrupts tranferred files. I'd go directly to the newest Realtek drivers...

amish

[Taz]

I would steer clear of anything with a Realtek name on it, anyone remember the video cards they used to make, they made Oak look good

Setup both PC's up with just TCP/IP and manualy create an LMHOSTS. file in the Windows directory of both PC's. Note this file does not have an extension. In that file add a line which has the other machines IP address then a tab, the other machines name another tab and finally #PRE.

On machine A which has as IP address of 192.168.0.1 the file would look like this :-

192.168.0.2 MachineB #PRE

On machine B it would look like this :-

192.168.0.1 MachineA #PRE

It should now know exactly where each machine is without resorting to broadcasts.

[Delany]

Hi Guys,

I can't offer any suggestions other than ones people have already mentioned, it is a common problem though, I used to get it a bit when setting up our gaming networks.

The Realtek problem is with the Standard Windows driver for it, if you use it, the card wont see anything etc and will corrupt files etc. The Realtek driver fixes THAT problem.

Anyhow, good luck with it, it's bound to be something really simple, they always are...

------------------
Gigabyte GA686BX, 128MB PC100 Ram, Millenium G400 MAX, Creative Labs SBLive!, Netgear FA310TX, AOpen DVD-1040 Pro Drive, Imation LS120, 5.2 & 12.7GB Quantum HD's, Everything being driven by Win98...or occassionally Redhat Linux 6.0

Bored Yet?

[Vlip]

I've been doing networks with my friends for years now. Most of them do have Realtek based cards. And we always got it to work.
These cards works perfectly with the standard windows 98 drivers.
I don't really see why you've got so many problems with them.
But I still agree with the statement that others brands (3com) are still way better than Realtek. So Kruzin, if you wanna change...

Vlip

[Jeff]

remove all entries in the network properties. close, do not reboot. Find the .inf file for the network card in the inf directory and (I am guessing that you have the install disks for the NIC) delete it. Reboot and install network. Only use MS Client, NIC, TCP/IP and File and Print Sharing for MS Network. Configure TCP/IP.

This has fixed abunch of weird problems at work.

[Dilitante1]

Gentlemen, you have missed the obvious question, do the NICs support crossed cables? This is a must and most manufacturers recommend against this. Checklist for network connectivity:
1. Sharing
2. identical protocals (I prefer TCP/IP and Netbui<---only to make it easy to locate systems )
3. Same workgroup name
4. Unique IP addresses

You also mention a Motherboard replacement, are you sure all the bios settings are identical? I'll be back....

-Dil

[Jupp]

Kruzin,

first thing I would do (if tcp/ip is still installed) is trying to ping the other workstation.

If this works, your cabling is ok. Afterwards open a dos box and issue a 'net view' command. Are both comps listed?

Try to map a shared drive with 'net use drive: \\computername\share' If this doesn't work, try 'net use drive: \\ip-addy\share'.

Does it work with the name or just with the ip-addy? As TAZ mentioned, check your lmhosts file. Maybe you've changed the computer names and you still have the old names in the lmhosts file. Either delete or edit the lmhosts file on BOTH machines and (from a dos box) type 'nbtstat -R'. This purges and reloads the nametable cache.

Usually there is no need for a lmhosts file on such a small network. It's mainly used to establish communication between WINS servers across routers.

Oh, something more:
After changing the mobo, did Windoze identify all devices on that comp? How many nics are listed on that computer? Did you check this in safe mode? Oh well, I guess you know this stuff .

Happy networking.

R.

------------------
P3B-F/P3-700E/256MB
G400Max/SBLive

[Electric Amish]

Crossed cabling works on my Realteks here at my house..

amish

[Jammrock]

Some of my friends have RealTek based cards and we have this problem all the time. To solve it we go Start -> Find -> Computers (or Ctrl+Win+F for shortcutters) and type in the missing machine name. You can always find the other computer this way, and after it is found it will normally show up in Network Neighborhood.

Jammrock

------------------
Athlon 650, Biostar board, 128 MB PC133 (Crucial), G400 32 MB DH, SB Live! w/ Digital I/O, 10/100 NIC, lots of case fans, etc...

[DentyCracker]

Strangely enough I have Realtek ISA boards 8019 in both machines at home and have never had that problem. Also have 2 Realtek PCI (8029) cards here at work and no problems either, using the win98SE built in driver. My brother has had a problem with the 8029 card in his job, similar to what you describe, I guess it is a combination of hardware that causes it. No probs at home where on machine is almost constantly running win2k (233 MHz PCCHIPS POS has been up for over a week on win2k). Finally got legit win2kpro btw, the CD is very pretty.

[Kruzin]

Thanks for all the suggestions guys.
It'll be a couple days before I can take the time to really mess with it again.

I did try a couple of quick things today...

making an lmhosts file did not help.
niether machine can ping the other.
running a net view command from my PC shows both, running it from the boss's only shows his.
using the start>find>computer, niether machine can find the other.

Wierd stuff. Networks can be such a pain
Next chance I get, I'll wipe all the drivers and protocals (again) and see what happens....

[giskard]

I had EXACTLY the same problem with my home network a couple of months ago using a Realtek NIC. I ditched the windows driver and grabbed one from here: http://www.realtek.com.tw/cn/driver/driver.htm

Problem solved.

Cheers,
Giskard.

[Kruzin]

Well, had a little bit of time to mess with it today.
Still no joy.
I completely removed both NICs, protocols, and INFs from both machines.
Swapped them around (Boss's NIC now in my PC, and mine in his).
Reloaded, both with the mfg's latest drivers.
Still the same thing. My machine sees his, but his will not see mine.

grrr.........

[Taz]

If you can't ping from either machine but one can see the other when you browse, you must have more than TCP/IP loaded i.e. IPX/SPX and/or Netbui. I would stick to just one protocol preferably TCP/IP.