Connecting Peer-to-Peer in Win98

[NetNeighbor]

I am trying to connect 2 P-200 PCs via Peer-to-Peer configuration. I'm currently using coax and have confirmed that I get a signal across from end to end.<br>
<br>
I have also set up resources on each PC to be sharable (after installing MS File/Print sharing protocol). <br>
<br>
I'm using TCP for communications. I have set each PC up with the same workgroup (down to case-sensitivity) and assigned specific IP addresses for each (10.10.10.1 and 10.10.10.2). Each PC shows itself in the Network Neighborhood and can ping itself via computer name but does not see the other.<br>
<br>
I've run 'route print' and can post results (if necessary) but I think it might be something more benign. I'm using coax that was used for cable TV converter box (not sure of the ohm rating).<br>
<br>
Is there a rating I need to look for to do this? I'm using coax because it was readily handy (i.e. already paid for [g]) and am considering getting a RJ-45 crossover cable but don't want to spend the money if I don't have to.<br>
<br>
Does this sound like a problem anyone else has run across and, if so, got any solutions?<br>
<br>
Thanks in advance ...

 

[KneeBreaker]

What about your network mask for the IP addresses? It probably should be 255.255.0.0, if you haven't set that up. As far as the cable connection, I cannot tell you much about coax, but an RJ45 crossover cable isn't that expensive, (less than $10), and if your network card will handle an ethernet connection I would suggest going that route.

 

[NetNeighbor]

The Subnet max was set to 255.255.255.0, not 255.255.0.0.<br>
<br>
As for the NIC, it handles both RJ45 and coax, but I used coax as I already had it. I need about 60 ft of Cat-5 to get to the other PC and that's a little more than $10. Most places don't sell lengths of more than 25 ft. with plugs, and the tool is around $30 - I can't see buying the tool for a one-time shot ...

 

[vkurikala]

Coaxial cable requires a terminator of 50 ohm on both ends and one of these should be grounded. Please check this. Ethernet coaxial cable is called RG-58 cable and is written on the cable sleeve.

 

[NetNeighbor]

Coaxial connections require a terminator even if I'm plugging them directly into the port on the NIC and not using the "T"?

 

[vkurikala]

Yes. They require a terminator at both ends even for two PCs. You need to connect a T at every NIC.

 

[gharlane]

it sounds like <br>
1. you need to use the correct cabling for your network.<br>
TV coax cable is the wrong kind of cable (RG-59),you need to use cable that is either, RG-58/U (solid copper core or RG-58 A/U (stranded copper core) with BNC connectors on both ends w/terminnation caps (rated @ 50 ohm)to prevent signal bounce.<br>
<br>
2. it would help to name both machines (different names for each individual machine).<br>
<br>
3. if you are only going to have 2 machines the coax is your best bet, crossover cable (CAT 5) you will only get approx. 9600 K/sec, whereas w/coax you will be able to get 10 Mb/sec transmission (theorectically) but still a lot faster than a crossover cable. also be aware to limit your distance to 100 meters (max)

 

[sijones]

Coax is the cheapist way of connecting and works great, I know because I had to put in a cheap network for internet access in work, I have the server in the office and three machines around 50 foot away, mine is setup as follows<br>
<br>
The name of the server: ALLANDALE <br>
IP 192.168.0.1 netmask 255.255.255.0<br>
Workgroup: ALLANDALEWORK<br>
<br>
The name of the other machines: (netmask as above)<br>
ALLANDALE2 IP: 192.168.0.2<br>
ALLANDALE3 IP: 192.168.0.3<br>
ALLANDALE4 IP: 192.168.0.4<br>
<br>
with all in the same workgroup.<br>
<br>
IP addresses are really important if you have one on the web, you need to use the following:<br>
<br>
192.168.0. 1 - 254<br>
<br>
these addresses are ones that will never be given out by the interNIC<br>
<br>
As said my computers are on the web so I have to be really careful, but using the RG58 (50ohm) cable with the terminators you shouldn't have a problem, you are using 75 ohm cable. If you don't set the IP addresses in the network panel, you cannot see the other computer in network nehibourhood, but if you do a find computer you can see it!! weird hey!!!<br>
<p>Simon Jones<br><a href=mailto:sijones@talk21.com>sijones@talk21.com</a><br><a href=

http://www.theallandale.co.uk>The

Allandale Youth Works</a><br>The above is all my own site I look after!!!<br>
God am good!!! and good lookin

 

[Guest_imported]

You've done everything right for the TCP/IP configuration part. What you forgot to do is to add a service in your Network Configuration. This service is 'File and Printer sharing on the Microsoft Network'. Once you achieve this then share the information on each end and you'll see the two computers. Because you are setting up a peer-to-peer network within Microsoft; thus, this service is a critical essential part in making the computers see each other.

 

[shaunkep]

Gharlane says that a crossover cable will only achieve about 9600 k/sec.&nbsp;&nbsp;Why is this?&nbsp;&nbsp;I've experienced this myself recently and was curious why I wasn't anywhere close to the 10Mb/sec transfer rate.&nbsp;&nbsp;Is it different with a hub and a straight through cable?

 

[wybnormal]

A crossover can rip upto 100Mbps full duplex, I've done this in a lab and I use 10/100 crossovers all the time for troubelshooting, configuring etc.<br><br>Personally in this case, I would either use Coax ( which he has) or use TWP ( cheap to setup) and IPX and get away from the fun of using IP on 2 systems. There is no need for IP in this case. <b>there is a need to make sure Netbios over IP or Netbios over IPX is enabled so the browser works correctly to advertise the share and so on.</b>n MS will tacitly recommend IPX for a peer to peer via crossover cable in their Technotes. Netbios will also do the trick if you want.<br><br>Yes his coax is incorrect BUT, for the short run he has, it will probably work. The reason for the RG58 is get the right distance. At 50 ohms, you will get the 185 meters. Using cable TV coax which is probably 75 ohms, you will lose distance but for under 20-30 feet, it doesnt care.<br><br>Mike

 

[Warped]

Hi<br><br>Once you have file and print sharing installed, after you reboot, make sure printing is enabled and also go back to the properties windows for networking and make one of your systems the browse master, I believe that is in the file and printing properties, but I could be wrong. Browse master will help see each other in the network neigbourhood. But only ONE can be the browse master, preferably the one that has file and print sharing installed.<br><br>vb<br>

 

[XoverIP]

FYI:<br><br>TCP/IP tranzmissions require that a computa requesting network attention, send some info to the host. The host then acknowlages this request.&nbsp;&nbsp;What happens next (part of what, at this point, already started happening) is syncroniztaion between the two computaz az they negotiate the peramaterz of the connection.&nbsp;&nbsp;Thiz haz been dubed 'the three whay handshake'.&nbsp;&nbsp;The 2 computers establish a connection, and that alone is alot ov data traffik known as overhead.&nbsp;&nbsp;TCP/IP is one of what is called Connection Protocols.<br><br>On the other hand, you have Connectonless Protocols, where a host, one might say, just goes a head and sendz the info, with out respekt to the syncronization i mentioned above.&nbsp;&nbsp;With yer network configured (protocol wize and cabling etc) you kan git the host to send your data with out all the overhead that is required for a TCP/IP connect.&nbsp;&nbsp;Examples of conectionless protocols are IPX and NETBIOS<br><br>As fer anyone dat sayz NETBIOS is not a routable protocol, and there for cannot be carried over, letz say, de internet, you are only abbout half right.&nbsp;&nbsp;Assuming you heard of the beautiful OSI model, think ov diz;<br><br>all you have to do iz encapsule the NETBIOS into a routable protocol.&nbsp;&nbsp;wham bam&nbsp;&nbsp;&nbsp;You could slip it right inbetwween a TCP/IP packet and da routaz whill neva know da difference.&nbsp;&nbsp;I hope someone at least learned a lil sumptin sumptin sumptin off ov dat...it took me like almost 5 minz to write<br><br>respekt 2 all

 

[Guest_imported]

For a 10 network address, you subnet mask should be 255.0.0.0 which is Class A (which goes from 1 or 126 as a network address)

 

[fenris]

for 2 computers shouldn't he be using 192.168.0.0/24 ?

 

[Guest_imported]

I have been trying to network a laptop and a Desktop both Pentiums and both on win98 through a PCMCIA and an ethernet card. 4 days and 3 microsoft certified fruitcakes and no luck. We cannot get the computers to see each other. Occassionally we get the lap top to identify the desktop name but thats as far as it goes. Getting desperate. The PC shop that sold us the gear have proven the cable (twisted pair) is OK. Other than that they offer no product support at all. Both the PCMICIA show in properties that they are working and the battle continues.
Help is there anyone out there who knows what they are doing.

 

[Guest_imported]

i have install in my operating system windows98 in this iinstall internet sharing but how to configure my lan for it i don't know..please taell me whole procegure

 

[nkingcade]

The first thing to check if you insist on using TCP\IP for this little network is the subnet mask. If you are going to use this protocol, spend the $10 to get a crossover cable. You may also want to consider using NETBEUI as an alternative if the only thing you are doing is file and print sharing. If these boxes are connecting to the Internet then forget this protocol as it is not routable. In addition, win98, win2k both have an auto configuration mechanism for DHCP if you chose to go that route. [sig][/sig]