//flex table opened by JP

Click to See Complete Forum and Search --> : Peer to Peer


Dkay
12-21-1999, 01:14 AM
I am trying to set a peer to peer network and I have the Cards installed and netbui and the computers are in the same workgroup with different names but i can't get them to recognize. I am using a xover cable.
I also tried it with a hub and 2 patch cables. Ant ideas guys???????

Tanks

Stan
12-21-1999, 01:32 AM
Hi

Check if you are using the correct drivers for the NICs.
Check if they are correctly installed under NT or 98 (whatever OS you are using...)

Stan

Dkay
12-21-1999, 08:16 AM
I am using the right drivers and under 98 SE it says that the device is working properly.
Also so you know I do not get any link or activity lights. even when using the hub.

Any help is useful I am stumped

Thanks,
Dave Kay

Stan
12-21-1999, 08:23 AM
No activity lights at all, even on the back of the NIC ?
If this is the case, I think the NIC is faulty.

Try to install it in another PCI (ISA) slot.

Stan

Eli
12-21-1999, 05:49 PM
Are there any jumpers on the NICs to select which cable type you're using? There is still the grim possibility of a bad NIC. I have one that flashes on boot and W9x detects just fine, but it doesn't do anything else...

Nathan
12-21-1999, 07:34 PM
Do you have Client for Microsoft Networks installed?

How about TCP/IP?

Do they see themselves on the network under Network Neighborhood?

[This message has been edited by Nathan (edited 12-21-1999).]

Nathan
12-21-1999, 07:41 PM
Does the NIC card appear correctly when you right click, properties, on Network Neighborhood?

Dkay
12-21-1999, 08:08 PM
Yes i can get the computers to see eachother and yes they are working properly in windows.
I dunno what else to do
Thanks,
Dve Kay

Mntsnow
12-21-1999, 08:38 PM
Well I see you said Yes i can get the computers to see eachother and yes they are working properly in windows

This makes me think that you can "see BOTH" computers in the network neighborhood but you are not "Connecting" Ie: SHARING files.

Have you SHARED any drives or folders? (to do this you need to right click on either a drive or folder and choose "sharing" and then set file permissions and dont forget to APPLY the changes. do this on BOTH machines and then try to connect http://www.sysopt.com/forum/smile.gif

Mntsnow

Dkay
12-21-1999, 10:08 PM
Okay I am sorry I reread that and I was mistaken about my wording there.

I can see my computer sometimes and the other can see itself but never eachother. I am sorry for that.

I can't get a link light no matter what i do I am tried 4 different network cards including an ISA. I checked the Crossover cable and I knwo it works. I dunno what to do. Could I have 3 or 4 bad cards?? This has gotta be some dumb little thing. I don't know what to do.

Thanks,
Dave Kay

Dkay
12-22-1999, 12:23 AM
Okay the light will flash one time on bootup.
I will try all of the PCI slots when I get back.
Okay lets just assume that the drivers or something is wrong in the configuration of the card although I don't think it is. Windows says that the card is working fine. One time on bootup I got an error to somewhat to the extent of:
your linksys card is not working correctly.
confused yet? http://www.sysopt.com/forum/smile.gif

This happened at the last bootup I did before giving up for the day.
Any other suggestions??????

Please I am confused.
This one has got me stumped.

Thanks all,
Dave Kay

Russianguy
12-22-1999, 09:27 PM
Dkay try to uninstall NIC. Install them agian.
Use TCP/IP protocol. Install drivers that come with NIC so that you will have TCP/IP instaled propely for your cards. Instal Client for Microsoft Netvork,File and Printer Sharing for microsoft netwotk. On TCP/IP protocol with your NIC name on properties check if IP addres obtaned automaticly. If it doesnt work with auto use that on host mashine IP addres
192.168.0.1 subnet mask 255.255.255.0
on another comp use Obtane IP addres automaticly or if it doesnt work IP addres
192.168.0.2 subnet mask 255.255.255.0
Both computers should to be on the same work group but with diferent names. IP addres 192.168.xxx.xxx is for LAN in subnet mask
fourth number shud mutch therd number in IP addres. Don't use NetBEUI. by the way cable in your case shold be a CAT-5 cable with RJ45 connectors, on one end of the cable with "A" standart on another end of the cable with "B" standart so that you don't nedd a hub for connecting 2 comps only.
B standart.
Good luck!


[This message has been edited by Russianguy (edited 12-22-1999).]

cyphen
12-27-1999, 09:32 AM
in the above scenario, you must also set under TCP/IP properties the default gateway to be 192.168.0.254

also did the installation disk come with some kind of test software? I know on mine i can boot to dos and run the diagnostic on each machine, setting one up as the server and the other as a client. If it works there then your problem is windows setup related. If not, it's hardware related.

you should get activity/link lights on bootup

Nathan
12-27-1999, 10:27 AM
I don't have the following addresses statically configured

1. My DNS is disabled

2. My Gateway is blank

3. Obtain IP address automatically

4. Use DHCP for WINS resolution

I have the following in Network properties;

1. Client for Microsoft Networks

2. Dial-up adapter

3. My NIC

4. NetBEUI, to the NIC

5. TCP/IP, for the Dialup Adapter & NIC.

6. File & printer sharing enabled.

My peer-to-peer works just fine with it set up this way.

I think Mntsnow is correct with what we have read so far. The thing that is suspect is the cabling. They may have given him the wrong ones. Then it might be the hub too. But you never know without being there.

ktwebb
12-27-1999, 02:38 PM
"in the above scenario, you must also set under TCP/IP properties the default gateway to be 192.168.0.254"

No you don't. He is trying to setup a 2 PC LAN with a crossover. Gateway means nothing in this situation. The gateway is used by the TCP/IP stack to seek out another IP with a different network ID. For example, if you were trying to ping yahoo 204.71.200.74, you would go through the gateway to get your echo. The gateway is the router.

[This message has been edited by ktwebb (edited 12-27-1999).]

socalgal
12-27-1999, 04:37 PM
When you have it all set up, don't forget to Unbind File/Print Sharing only on your TCP/IP pipeline(s) to the Internet, (either DialUp Adapter for 56K or the specific NIC for DSL [not sure about cable!]) for greater security. http://www.sysopt.com/forum/smile.gif

Nathan
12-27-1999, 07:35 PM
I guess we won't know what happens huh?

ANTONIO E GUERRA
12-27-1999, 10:38 PM
In addition, make sure that you have the right names, workgroup and ip address. Try to discard a faulty hardware problem first, such as a, bad network card, right appropriate network driver, etc.; then, identify and isolate the computer with the problem. Most likely there is a problem with one of the network cards or cables. If you have tcp/ip, try to ping all the computers and run ipconfig. It will require a lot of your patience. Work with someone else.

Dkay
12-27-1999, 10:49 PM
Thanks all of ou I just got back from up north
I will try thses great suggetions and gt back

cyphen
01-21-2000, 01:39 PM
i know this is old, but did you ever get it working?

also, i wanted to reply to ktwebb with a question. I'm not doubting you, but on my LAN at home, we couldn't get TCP/IP to work. Then we added the default gateway and it worked right away. Why is that? I guess it doesn't really matter, just curious...