$10 in paypal if you can successfully help us get our LAN working. *Hub is being taken back, thanks anyways*

[FordLorider]

$10 in Paypal if you can help enough to get our networking working correctly (if it's money that it takes to get this network working so be it)

We both have NICS, I have a Linksys 10/100 and he has a Netgear 10/100, both bought from Best Buy. The Hub is the Netgear 4 Port Autosensing (I have no idea what that means) Hub. It's the DS104. http://www.netgear.com/products/ds_108/index.shtml

Right clicking on Network we get to the properties and I would think that we have everything set correct. Our settings are as follows:
'The following network components are installed:'

Client for Microsoft Networks - double clicking this gives me
'Client for Microsoft Networks Properties' and the only thing checked is Logon and restore network connections

Dial-Up Adapter - double clicking this gives me
'Dial-Up Adapter Properties'
Driver type Tab - Enhanced mode (32 bit and 16 bit) NDIS driver) is the only thing that I can check and it's checked.
Bindings Tab- TCP/IP Dial-Up Adapter is checked
Advanced Tab- 'Enable Point To Point IP' is set to 'No'
'IP Packet Size' is set to 'Small'
'Record a log file' is set to 'No'
'Use IPX header compression' is set to 'Yes'

Linksys LNE100TX Fast Ethernet Adapter - double clicking this gives me
'Linksys LNE 100TX Fast Ethernet Adapter Properties'
Driver Type Tab - 'Enhanced mode (32 bit and 16 bit) NDIS driver' is checked of the 3 available
Bindings Tab - 'Linksys LNE 100TX Fast Ethernet Adapter' is checked
Advanced Tab - 'Connection Type' is 'AutoDetect'
'Transmit Threshold' is 'Store and Forwared'

TCP/IP Dial-Up Adapter - double clicking this gives me
'TCP/IP Properties
IP Addres Tab - it set to 'Obtain an IP address automatically'
WINS Configuration Tab - is set to 'Disable WINS Resolution and 'Use DHCP to WINS Resolution' is not checked
Gateway Tab - contains nothing
DNS Configuration Tab - is set to 'Disable DNS'
Bindings Tab - 'Client for Microsoft Networks' and 'File and Printer sharing for Microsoft Networks' are both checked
Advanced Tab - 'Allow Binding To ATM' is set to 'No' and 'Set this protocol to be the default protocol' is checked
NetBIOS Tab - nothing is checkable

TCP/IP Linksys LNE 100TX Fast Ethernet Adapter
'TCP/IP Properties
IP Addres Tab - it set to 'Specify and IP Address' my assumption about this is that me and my buddy have to have the same 'Subnet Mask' and our 'IP Address' has the same first 3 numbers the same and the last must be different (correct me if I am wrong, do they have to be consecutive numbers?)
WINS Configuration Tab - is set to 'Disable WINS Resolution and 'Use DHCP to WINS Resolution' is not checkable
Gateway Tab - contains nothing
DNS Configuration Tab - is set to 'Disable DNS'
Bindings Tab - 'Client for Microsoft Networks' and 'File and Printer sharing for Microsoft Networks' are both checked
Advanced Tab - 'Allow Binding To ATM' is set to 'No' and 'Set this protocol to be the default protocol' is not checked
NetBIOS Tab - nothing is checkable

File and printer sharing for Microsoft Networks
'File and printer sharing for Microsoft Networks Properties'
'Browse Master' is set to 'Automatic'
'LM Announce' is set to 'No'

The 'Primary Network Logon' is set to 'Client for Microsoft Networks'

Clicking the 'File and Print Sharing' button gives me:
'I want to be able to give others access to my files' is checked
'I want to be able to allow others to print to my printers' is checked

The 'Identification' Tab contains my computer name and we both have the same workgroup name in the same lower-case fashion.

The 'Access Control' Tab has 'Share-level access control' checked.

His settings were the same for mine except for IP and Computer Name (I think).

These settings were the farthest that we could get meaning that we got what we believed the most success with them. We were able to see our own computer on 'Network Neighborhood' and when each of us got into entire network, we could see our own (same) workgroups but both of our computers only showed ourselves in the workgroup.

Hub troubles:
Our Hub seemed weird. There is a button on the hub that when pressed it means 'Input' and when depressed it means 'Normal'. We tried several settings with both the button presses an depressed.

If the light above our each individual port where we were connected to the Hub were blinking then that means 'Receiving' and it if was solidly lit (if that's a word) then it's 'Sending'

At this time the Hub was set to Normal (depressed). My buddy was in port one and for some reason he was always solidly lit. I was in port two and I was always blinking. At this time the collison light was almost solitly lit (flashing barely). I changed to port 4 and the collison light was still almost solidly lit. We then switched ports so I was in 1 and he was in 2 and I was still blinking and he was solidly lit, there was no change so we put him back in 1 and me in 2. So then I changed my cord (thought that that was the problem because I thought that the collison should not be lit that much). I changed from a newer 25ft cable to an older 10 foot cable and the collison light didnt flash so hard. We then pushed the botton on the Hub (now set to Input), almost all lights turned off including the collison light, 100 light, and the light above my port on the Hub. It was getting late and we quit for the night (again).

If anyone can get our network working then I will personally give them $10 paypal.

My hand hurts....time for a nap.







Never got it to work I am believe I have tried everything. Can ping or anything. The hub is going back today. Thanks for your help though guys. Hopefully someone else got their problem solved cause I sure couldn't.

 

[SufferinSuccotash]

The IP addresses don't have to be consecutive, but they do have to be on the same network. Try using 192.168.0.1 and 192.168.0.2 for the machine's IP addresses and use 255.255.255.0 as a subnet mask. The Input/Normal button is so you can hook another hub into that hub. Leave it on normal, or simply don't use the fourth port. Once you've done this, see if you can ping each machine. Open a DOS box and type 'ping 192.168.0.1' and 'ping 192.168.0.2' on each machine. If it comes back with a time, you're all set. If not, we'll have to keep working at it.

 

[fergiboy]

Try putting the cables into the two farthest holes. Don't use the uplink port, the one next to the button.

 

[Scarpozzi]

OK...the button on your hub is an uplink/crossover button. What this does is allow you to use a straight-thru cable rather than a crossover cable to connect another hub to your existing up or to run an internet feed... Don't use port 1 if you are getting weird light displays...

As for the lights on NICs and Hubs. There are usually send/recieve lights or activity lights. They sometimes mean something and othertimes not. The reason is because they may be searching for a signal and not finding one past the hub. They will have a link light if they have connectivity to the hub.


To network the computers, make sure that you have Client for Microsoft Netowrks installed, a NIC, Netbeui, and of course File and Print Sharing for Microsoft Networks. Then you need to make sure that you specify a shared directory somewhere by right clicking on the folder you want to share in "My computer". You can then select it as a shared folder from there.

If you do that, it should work as long as your cables are good and your NICs are installed properly. If you still cannot find the computer through your network, there may be an Operating System conflict that cannot be solved easily. That is when you might want to try doing a search for the other computer. For instance... You have two computers. One named COMPUTER1 and one named COMPUTER2. On COMPUTER1, go to start, find, computer...do a search for COMPUTER2. You should then be able to locate it and click on it. If you cannot view the computer, try searching for it from the other one.

Try that and let me know if it helps. Good luck!

 

[SufferinSuccotash]

Subscribing

 

[Jugernot]

SufferinSuccotash, I have the same basic setup as FordLorider except I've gotten everything working other than ICS. I can successfully ping both machines, but the client doesn't get on the internet properly. Any suggestions?

 

[SufferinSuccotash]

The first thing I would check is can the machine that is hooked directly to the internet reach websites, and double-check the gateway is set correctly on the client.

 

[andrey]

couple things to check:

1. if your cables are not crossover, try to not to use uplink port at all, let's say 2 & 4

2. Install NetBEUI protocol on both computers for file and printer sharing. Since this protocol is autoconfiguring, if everything connected properly, everything should work fine.

Let us know how this works out for you.

 

[Jugernot]

SufferinSuccotash, I got it working finally by specifying the settings manually. I guess it had some kind of problem with the DHCP.

Thanks

 

[FordLorider]

fyi, I am going to try what you guys say in order from first posted to last. The one that makes our LAN work first I will reward them. This will probably happen today or thursday. Thanks.

 

[hymy]

Ford,

I fixed this problem with the same card by installing the IPX/SPX protocol. I've seen this twice. If you look real close at the documention it does say somehere that you have to install IPX/SPX.

 

[JumpJoe]

I think I know, for some strange reason, nics irq conflicts are never reported by windows.


Try yanking all other card except for your video. Worked for me, once I got my network running, I reinstall all the other components one by one. I don't know why this is, and I haven't seen this for any other PC component except modem, but windows does not report all resource conflicts, it once drove me nuts as well. At least for modem there is the diagnostic option, but nics we're in the dark. Just have to yank everythin.

 

[FordLorider]

the question is what would happen to your NIC when you had the IRQ conflict. Our light up and I used mine in that slot for school ethernet. I guess it could be his but he has lights and lights on the hub, your saying that even with both set's of lights the card could still have those conflicts. Thanks

 

[JumpJoe]

For my PC to PC network, and I guess it couldn't get simpler than that, a simple impossible to detect irq conflict took me days to solve. Device manager looked fine, all pci devices, and led lights up when you plug the cross over cable in.

In both my computer, I end up sacrificing a pci TV-tuner card to get it working right.

My advice would be to go buy a cross over cable and first test the connection between two PCs at a time, this way, you'll know if it's the hub or the nic cards giving you problems.

 

[FordLorider]

Can anyone verify that our settings are right, you don't have to go through all of the settings just the important ones. I think that they are pretty much right but just in case.

 

[SufferinSuccotash]

Try pinging the local loopback address (127.0.0.1) on each machine, and then have each machine ping its own address. See if that turns up anything.

 

[hymy]

Ford,

your initial post indicates that you only have the TCP/IP protocol installed. Your netgear NIC will not work unless you add either netbeui or IPX/SPX to you network properties. I don't know why, I just know that I have one too, and if I just have TCP/IP installed, it won't work.

left click net neiborhood and select properties. click add and select protocol. Select microsoft and then netbeui. Do this for both computers and add IPX/SPX too. You can add it the same way.

Now I'm not saying this will fix it, cuz there maybe something else wrong. But I know those netgear 10/100 cards won't browse the network unless you do this.

 

[dirtboy]

hmmm...I have Netgear nic's installed in a couple machines with TCP/IP only and they work just fine.

 

[FordLorider]

I guess IPX might be the answer, sorry but I haven't had the time to get check out all of these possibilities but I am working on it.

 

[hymy]

I'd count myself lucky then dirtboy,

I'm on a netgear machine now. I deleted all the protocols except tcp/ip last night. And it wouldn't browse the network. Then I added netbeui and it was fine. It did however surf the web fine. I got friend that has the exact same problem on a our lab network. So I don't know. My motto is if it works then no matter how weird it is don't break it trying to figure out why it works.

 

[Kalidor]

Two things:
1) Since you both are using Twisted Pair cabling you might as well change the adapter to use TP only instead of auto-detect

2) Once you install IPX in the advanced area you should have a field that lists frametype. Set that from auto to 802.3. I am not sure why you need that but I have seen several networking setups go from nothing to fully operating with just that change.

 

[SufferinSuccotash]

That's because on an IPX network, all computers must be set to use the same frame type. What that means is that the IPX packets are sent out in different formats, and they are not compatible with each other. You just have to choose one and go with it throughout the entire network. OTOH, AutoDetect will set the Frame Type to be whichever frame type it encounters first on the network. I suppose it is possible that in negotiating, both computers would send out both types, and one computer could receive an 802.2 packet first while the other would receive an 802.3 first, thus rendering the IPX protocol on the network useless.

 

[FordLorider]

!@#$%^*($!!!!!!!

Never got it to work I am believe I have tried everything. Can ping or anything. The hub is going back today. Thanks for your help though guys. Hopefully someone else got their problem solved cause I sure couldn't.

 

[Suki]

I had a problem before installing a network on my friend's office. I followed the instructions to the t's but didn't work. Finally my brother said to enabled PnP OS in the bios and everything works. Hope this help.