Click to See Complete Forum and Search --> : 2 PC Network...Can't See Each Other...HUH?


RedVR6
August 3rd, 2000, 01:04 PM
Hi guys...new here. Quite a resource!! I did a search through here for my problem and found a few things but was really of no help...So I was wondering if anyone could shed some light...

My brother recently set up a LAN at home (on 2 PCs w/ Win98 SE), using the Linksys Network Starter Kit.. installed all the protocols that they recommended, Client for MS, Netbeui, IPX/SPX, and TCP/IP (though Linksys does not seem to keen on that). Through no configuration were both computers visible in Network Neighborhood, or were they able to communicate. The PCs were each able to view themselves, but not eachother.
All hardware is installed without problems, connections are fine, and sharing is enabled.

IP address for PC 1 is 192.168.2.21
IP address for PC 2 is 192.168.2.22
both have Subnet Mask 255.255.255.0

All identification is correct (different names on each), and I have tried putting the PCs in separate workgroups, but the other workgroup won't even show up.

This is exactly how I set my network up at my house and had no problems...Any thoughts?

Thanks a lot!!

------------------
DBK

bpb123
August 3rd, 2000, 01:29 PM
I used to have a kinsys 10mb starter kit. I thought it was a piece of $h!+, but i kept it. You could try first to set the login for both computers to windows login. Also, you dont need ipx if you dont play ipx games. if settign to winblows http://discussions.hardwarecentral.com/tongue.gif login does not work, try setting the assign ip address automatically option.

ah6tyfour
August 3rd, 2000, 01:33 PM
are you sure the workgroup name is EXACTLY the same? if they are not the same, you will not be able to see each other....could it possibly be a cable problem? if each computer can see itself on netwrok neighborhood, that means its configured correctly. if you need more help, pleae post...good luck!

------------------
MAC= Must Achieve Corruptness!

RedVR6
August 3rd, 2000, 01:39 PM
I figured we had everything setup correctly, mainly since the machines could see themselves. We played with the cables...plugged them in different ports on the hub, etc. Still did not work. Maybe I will drop off some patch cable ot his house for him to try...could be crappy cable. Who knows.

As for the workgroup name...I am 110% sure it is the same on both machines. I made sure of that.

When he sees the posts I will have him use your tips...Thanks!!


------------------
DBK

[This message has been edited by RedVR6 (edited 08-03-2000).]

PeteS99
August 3rd, 2000, 06:01 PM
Hi all,

This discussion is based on my (lack of a) home LAN. The only protocol in use right now is TCP/IP. I tried switching to Windows logon, and also tried automatically obtaining an IP. No dice still!! The computers can still see themselves (and with the auto IP they sit on boot waiting for one to be assigned, annoying, so i switched back.). Any other ideas? Is there something screwy with my hub? I am about to fire off a note to Linksys... thanks all.

pete

------------------

-^-SAS S99-^-
http://go.to/SAS

RedVR6
August 3rd, 2000, 07:23 PM
Did you try other patch cable??? Hmmm.

------------------
DBK

PeteS99
August 3rd, 2000, 09:25 PM
i switched 'em, to no avail. they get the link status light, so they cant be bad...

also, i am about to hook up my DSL... anyone have good methods for sharing this (its Infospeed, and we only get one IP, not supposed to share http://discussions.hardwarecentral.com/wink.gif ). I am thinking maybe a router would save some trouble? For now, i plan to use RASPPPoe ( http://user.cs.tu-berlin.de/~normanb/ ).. that is assuming this &%@$*@# network decides to start working!!!

pete

ps- think VPN might help/hinder?

kwebb68
August 3rd, 2000, 10:27 PM
Email to Linksys is not going to help you. Not likely anyway. First to correct a couple of things. Different workgroups will not keep Machine A from seeing Machine B but is will make it more dificult. Secondly, you are going to want to use Client for Microsoft Networks as your Primary Login, not windows login.

Do not use Network Neighborhood as your source to test connectivity. It is fine as a utility but not as a connectivity tool. Your IP settings appear to be fine, so try to ping. That will tell you if your IP settings are o.k. and if the NIC's are working properly. Ping machine a from b or vice versa. If that fails, ping Machine a from Machine a, and/or ping the loopback address which is 127.0.0.1. That will tell you if the Card is working properly. If you can ping successfully, use the find computer option from the Start menu, or by right clicking on Network Neighborhood and using find from the properties menu. After trying these things, post back your results and we can go from there. Sidenote, you need to make sure you have shares on the remote PC's. That is another thing that will make the remote PC's not show up in Network Neighborhood. There are some master browser settings to try if you must use Network Neighborhood, but we need to see if your NIC's and protocol settings are setup correctly first.

PeteS99
August 4th, 2000, 01:15 AM
Here are the results of the pings...
Machine A to B.. no response
Machine B to A.. no response
Machine A to A.. reply
Machine B to B.. reply

(and for clarification, i am logging into Client for MS networks and the PCs are in the same workgroup)

next step??? thanks!

pete

kwebb68
August 4th, 2000, 08:04 AM
"they get the link status light, so they cant be bad"

Not necessarilty true. Link lights are a good indicator but not the final word at all. Are you getting a timed out response or destination unreachable message when you try to ping. Looks like your settings are o.k. so you might want to try removing the NIC driver, as well as your TCP/IP stack. Actually you might just remove all your data in the network control panel applet, reboot and reinstall everything back. If still no workie, you will need to get some known good hardware, i.e. a know good NIC (Prefereably two), as well as known good cables and start troubleshooting by process of elimination. If you have a bad card, is it almost certainly just one of the NIC's, same with the cables. The original post mentioned a kit but now what was in the kit. If you are using a hub, you may want to try getting a crossover.

jontem
August 4th, 2000, 08:46 AM
I had a similar problem with my two laptops.

When I set to login to the NT workgroup (e.g., "home") at startup (client for networking) and logged in on both machines (even though there were no way to get the "home" domain login authenticated - just press OK).

So tick that box om both comps and login to "home" at startup.

PeteS99
August 4th, 2000, 10:13 AM
All of the bad pings brought 'timed out' errors. The kit came with the 2 Linksys PCI cards a 5 port hub and cables. I have a Kingston NIC which I can try out. I have tried removing everything from the Network Panel except the Dial Up Adapter. First I will try swapping NICs, then a clean sweep, and then a crossover (if the NICs are working!). Thanks....

w5uc
August 4th, 2000, 09:57 PM
Check to see if you have a conflict with serial port interupts. a while back, I was trying to resolve a problem, and changed the IRQ for a serial port. After that I neither of my machines would see the other. After I went back to the original configuration, everything worked fine.

Tuttle
August 6th, 2000, 12:25 AM
For what it's worth, pinging 127.0.0.1 doesn't check any of the network adapters in a system, only the TCP/IP protocol install itself. To check the NIC, you need to ping the NIC's IP address.

PeteS99
August 7th, 2000, 05:22 PM
busy weekend.. i'm back. tried my old NIC (kingston) and it made no difference. the only conflict that i encountered was upon my original installation. i have an old SB AWE32 (ISA) sound card, which has an onboard IDE controller... that IDE controller and the NIC were battling for an IRQ (12) and i was having all sorts of problems.. finding the conflict, i disabled the IDE controller, and the NIC grabbed the IRQ, and no more problems (aside from the topic of this thread!). no other conflicts are listed in my device manager, at least..

PeteS99
August 7th, 2000, 08:32 PM
Ok, I have done a bit of research.. and I have come up with two questions...

"Use a PCI bus master slot. Most PCI local bus computers have master slots, slave slots, and/or "combo" slots that can act as either masters or slaves. The EtherPCI II card should be inserted into a master slot. See your PC's user guide to see which slots are which."

What PCI slots are 'masters'?? I have not heard of this terminology for PCI devices....

"Good IRQ values to try are 10, 11, 12 (if you do not have a Bus mouse), 9, and 5 (in that order). "

What is a Bus mouse???? I have a serial mouse, but its COM port is 3 or 4...

Thanks!!

pete

Tuttle
August 8th, 2000, 10:19 PM
A bus mouse is an old proprietary IBM thing. You'd know if you had one. I think whoever wrote that meant a PS/2 mouse, which has a little round 5-pin plug instead of the 9-/25-pin D shaped plug. PS/2 mice use IRQ12, so if you have one then that isn't available for other things. Serial mice like yours just use the IRQ of the COM port it's attached to, either IRQ4 (COM1/3) or IRQ3 (COM2/4).

nomad255
August 9th, 2000, 01:21 AM
hey redvr6 i think i have the exact kit that you bought and im having the same problems with it and im trying the same things that people have been metioning and noting seems to work.

RedVR6
August 9th, 2000, 10:33 AM
nomad,

Really? I am not sure what the status is with it as of now. Will have to see what my brother has to say. I am totally boggled.

------------------
DBK

PeteS99
August 9th, 2000, 10:42 AM
(thanks for those explanations... not the problems, unfortunately.)

the status? utter frustration. i am out of ideas, and patience. i think i might return it and get something else... hopefully NECX will take it back? i dont think i want to deal with this kit anymore, its just way too much of a hassle...

RedVR6
August 9th, 2000, 10:44 AM
NECX is going to hit you with a restocking fee. See if you can sell it here or PCM....Probably your best bet. Maybe I will come by tonight.

------------------
DBK

PeteS99
August 9th, 2000, 10:49 AM
maybe we can try swapping this HW with yours sometime? test each card, hub, cable?

RedVR6
August 9th, 2000, 10:53 AM
If you want. Lemme know. I am running a 3Com on my Windows box...same hub. The Linux box has an on board NIC.

I am still thinking there is a cable problem....

------------------
DBK

nomad255
August 9th, 2000, 11:34 PM
i fixed my problem they have a newer version of the kit now so i exchanged it and it works great. i havent had any problems after i got the new kit

PeteS99
August 10th, 2000, 12:36 AM
nomad, where did you get yours? and what is new in the newer version? i'm jealous!!

nomad255
August 10th, 2000, 03:11 AM
i just picked mine up at compusa.
im not sure of the new version i think its like 6 or something

PeteS99
August 10th, 2000, 01:14 PM
hmm. just looked online, they are still selling the same one i have... dunno.

cnp1
August 10th, 2000, 06:12 PM
Sometimes it helps to have the IRQs, etc. set identically on both machine's NICs in peer to peer networks. You should try using an x-over cable to see if your two puters can see each other.

netjason
August 10th, 2000, 09:18 PM
I have just bought the linksys lan cards (2of them) with a catagory 5 snagless patch cable and the exact thing is happening. Computers see themselves but not each other. There has got to be an answer somewhere!!!

Its the next day! After reading all that you smart people had to say, I must admit to learning a great deal about networking. I also found out that replacing the patch cable with a cross-over cable solved everything. I am now networked...er how does this help me? Heheehe...thanks to all


[This message has been edited by netjason (edited 08-11-2000).]

RedVR6
August 12th, 2000, 12:42 AM
Well guys...turned out being an IRQ issue. We pulled his antique sound board out and moved a few card sto other slots and then rebooted. Walah...It worked!

Damn those IRQ's. http://discussions.hardwarecentral.com/wink.gif

Thanks for all the help!!!

------------------
DBK

nortsm
August 14th, 2000, 09:43 PM
I have been following this string,and i was hoping for a simple solution ie a specific cause and effect. I have been having the same problem with my Linksys network kit.
Last night i gave up and turned the computers off. Today i was ready to call Linksys support, when i turned the computers on every was working the way it should. I started with a Linksys Switch kit then i updated one of the network cards (4.1 from 2.0 ). On the other end i went with a USB network device, and it still did not work. I don't know what i did or din't do but it works.

[This message has been edited by nortsm (edited 08-14-2000).]

RedVR6
August 14th, 2000, 09:50 PM
One of those things...Just don't ask. As long as it keeps working. http://discussions.hardwarecentral.com/biggrin.gif

------------------
DBK

Dr. MASS
August 16th, 2000, 01:32 AM
Try this, start... find/search... computers..
type in the other computers name.. double click on it, when u find it..
That should do the trick..


------------------
*** The worst investment u can do is a buy a new computer, buy some stocks isntead ***