Site Search

Site Info

Home » Forums » Forum Archives » Networking and Internet Sharing » Topic # 702

Computer A sees Computer B, but B is blind toward A
Otto Feb-27-01 02:38 PM
From : Frustrated

Re. : Home networks

I have been trying to get a simple ethernet between two computers going and have failed miserably, despite your and other peoples write-ups on the subject.
I am not a computer expert, however, I am not a computer dummy either. I do all my installations and modifications since the days of early DOS.
Perhaps you can help.

Operating conditions.

Windows 98, second edition on both computers
Computer 1) 133 Mhz pentiun, no name.
Computer 2) 200 Mhz pentium Compac

Wire medium : Thin coax with two 50 Ohm terminations *)
*) In my case coax is preferable, because, being a radio amateur, I have strong RF fields in the area.
Adapters : Realtec 8019 Ethernet in both computers
Installed drivers. (Best driver according to Windows).
Installed I/R and I/O according to network configuration need.
No conflicts. No I/R conflicts.
Device manager: No yellow marks, adapter present.

Network listings: Client for Microsoft networks
Protocol > Binding
Protocol> Binding
Client for Microsoft Networks *)

*) I have tried Windows Log on as well, NO change
Protocol: Installed IPX/SPX for LAN and TCP/IP for later internet share.
TSP/IP Identity, name and workgroup entered in an identical manner on both.
Sharing activated
Win Res and DNS Disabled.
IP address entered properly, 192 168 0 1, or (2) and 255 255 255 0.
Nothing in gateway
File and printer sharing activated

Pinging from DOS works fine from either computer. BUT:
Sitting at the originating computer P133:
Going into Network Neighborhood I find the originating computer (P133) and the remote computer listed (P200).
Clicking on either will bring up the individual shared items, as it should.

Going to the remote computer (P200), I also see both listed in Network neighborhood
Clicking on its own listing (P200), the drives and folders appear as expected.
Clicking on to P133 however causes the machine to poll endlessly, until finally after about 30 seconds the drives of the other computer (P133) appear.
That is to say, communication from P200 to P133 does not work properly, wheras communication from P133 to P200 works fine.

I tried just about everything but standing on my head, nothing worked. Eventually I ripped the adapters out and replaced them with ethernet 32 bit adapters RLT 8029.
Same result !!
I am beginning to believe that this may be caused by a Windows setting, which they do not care to talk about, or perhaps a Bios setting.

I would appreciate any ideas on the subject before this thing drives me mad.



1. RE: Computer A sees Computer B, but B is blind toward A
lbyard Feb-27-01 04:27 PM
In response to message 0
Otto, Try mapping the drives (http://duxcw.com/digest/Howto/network/net2pc/map.htm) and not using Quick Logon in Client for Microsoft Networks. You may have a flaky cable or bad ends (RG58 connectors). See http://duxcw.com/faq/network/thinwire.htm for details on the cabling. The wire should be stranded (RG58A/U); the kind of connector used can make a difference. T’s and terminators must be used at both ends. One terminator should be grounded. The other should not be grounded—can cause a dangerous ground-loop condition. Try disabling the Browse Master on the lesser-used/slower computer (file and printer sharing Properties; not the button). Shielded TP cable and RJ45’s are available. See ICC (http://icc.com/pcs-Patch%20Cords%20-%20ScTP%20Cat%205.htm ), (Black Box (http://catalog.blackbox.com/BlackBox/Templates/blackbox/default.asp), AIM (http://www.aimelectronics.net/), etc. Larry

2. RE: Computer A sees Computer B, but B is blind toward A
Otto Feb-27-01 04:39 PM
In response to message 1
Thanks Larry, will try all suggestions and let you know.
OK on ground loop, presently none are grounded.
Would you recommend going to shielded TP cable as opposed to my present thin RG58 with a solid center conductor?

3. RE: Computer A sees Computer B, but B is blind toward A
lbyard Feb-27-01 05:04 PM
In response to message 2
It's up to you… It would be faster and may even have less EMI, but I don't know that for sure. I don't know if you can get a shielded crossover cable, which would eliminate the need for a hub of switch. Let us know if you try it, Ok? Larry

6. RE: Computer A sees Computer B, but B is blind toward A
Otto Mar-04-01 10:42 PM
In response to message 3
I found the problem. My Realtec 8019 adapter was set to 10 Base T, instead of 10 Base 2.
I missed the small print in the setup program.
Thanks again for trying to help.

4. RE: Computer A sees Computer B, but B is blind toward A
radiostud2000 Mar-01-01 11:22 PM
In response to message 0
There is one thing that stands out in my mind that it could be. I worked on a small peer-to-peer network once and had the same problem. It came down to editing a file called LMHOSTS. This is a simple text file that contains IP addresses and computer names. IF you look in the windows directory you should see a lmhosts.sam file. This is a sample file. In this file you will see some examples but they make it look to complicated. This is all you have to do.

Using Notepad or another text editor, create a file with the following entries:
xxx.xxx.xxx.xxx computername
xxx.xxx.xxx.xxx computername
Win95/98: Name the file LMHOSTS and save it in your Windows directory (usually C:\Windows )
NT: Name the file LMHOSTS and save it in C:\winnt\system32\drivers\etc
You may have to rename it after saving--you do NOT want a .txt extension on the filename!

xxx is the ip address and computername is the identity. put the ip's of both computers in this file.

This is the onlything I can think of right now.

As far as your cabling issue, might I suggest CAT 5 Shielded Twisted Pair. (STP) This is the same as regular CAT 5 cable except it is shielded. This will allow you to run a regulare 10Bast-T Ethernet card in your computers as well as use standard cable with RJ-45 connectors. This will be nice if you devide to put a friends computer on your network or you devide to expand.

Just a few thoughts. I hope they provide you with some help. Please write me back if these tips work for you,

Drew Smith

5. RE: Computer A sees Computer B, but B is blind toward A
Otto Mar-04-01 10:38 PM
In response to message 4
Thanks Drew

I had already tried that SAM file approach to no avail.
I did eventually find the problem. One of my network cards is a Realtec 8019, which is "programmable" by means of a set up program.In the setup program there is an ever so small provision with which to set to 10Base2, or 10 Base T.
Mine was on 10 Base T. After that adjustment and scepticism on my part, all went well.
Thanks for your reply.

7. RE: Computer A sees Computer B, but B is blind toward A
lbyard Mar-05-01 04:29 PM
In response to message 5
I should have thought of that. Also, some of them do it automaitcally, others have a jumper.

| Home | Guides | How to | Reviews | Online Store | FAQ | Forums | Forum Archives |
| Links | News | Newsletter | About Dux | Advertising | Contact Info | Privacy |