For all you ppl that think you need to run DHCP, disable it, and just run either auto detect or assign IP in the client machine network setttings. THERE IS NO NEED TO RUN THIS WHACK NETWORK WIZ. No reason at all, I have owned the linksys 41 for 2 and 1/2 years, and been running XP for a yr and 1/2. I also have my CNA and my MSCE. I shouldnt have to tell you my credentials I think I know what I am talking about. But since some of you DHCP users think I dont, talk to linksys tech support, if you ever get a knowledgable person on the line, or anyone on the line at all. Or if you want, check out some knowledgable LINKSYS forums.
DHCP is not needed, the router is its own DHCP. You only need DHCP if you own the linksys hub.
As long as you have a tcp/ip protocol assigned to a nic on that client machine, whether it is setup auto or not, you will see the balloon popup in the bottom right corner telling you that a network cable is plugged in.
Tundra, I can tell you what your problem is, you have seen ppl tell you the IPX protocol is the way to go, maybe if you were running ICS as many do, since they dont either have the money, or dont believe in 3rd party hardware. Internet is not going to travel on IPX. You will only see the other clients files and be able to transfer, THATS IT!! IPX is a faster protocol, meant to deter confusing loads of traffic on a LARGE network long used for P2P networks, big firms or networks started using. NOT DHCP
For a solution, Just setup TCP/IP auto or not, then go to the advanced button, then the WINS tab and for your Netbios Settings, set to default or enable. Then there is no need for the IPX protocol to be able to see other client computers or share files between them. Using netbios behind the firewall will be protected as long as the other computers are not on the DMZ. For the client settings enter the IP: 192.168.1.2 the default gateway as 192.168.1.1 and your ISP's DNS servers. This will resolve conflict later on down the road as I will explain further.
After you have chosen to do this, make sure that all client computers are on the same name for the Domain name. Then go to the "Entire Network" and search for the other computers on your network, THIS will solve your internet/P2P network problem.
You dont need PPOE as cable does not run on PPOE, so yet here is another answer that, YES, is TOTALLY wrong, quit ppl, jesus!!
LPDad, you are on DSL, therefore dont give him the way you setup your DSL connection with your router, as it is totally different than setting up a cable modem, much easier setting up a cable modem than it is a DSL connection, especially a dialup.
There is no need to mess with any other SETTINGS on your router's configuration page, other than the Wan IP address (your modem's IP), the gateway IP, DNS servers, to get internet connection and P2P. No need to fumble with DHCP, PPOE, autoconnect settings, none of that crap. This will only confuse the hell out of you as I can see it already has. Once you get that working, THEN you can mess with port forwarding for gaming, ftp, webserver, ect.
For your "domain" name, just choose WORKGROUP for the time being. That is the defualt domain name XP will give to you, just use this and you can change the domain later after you get everything up and running.
Posted by TerraHertz:
Uhmm keylo what are you so talking about. I run DHCP on my linksys and it automatically assigns prv IP's to my PC's. Do you own that particular router are you just trying to say something.
This guy does not want to go through the trouble of using static IP. Ive done it and my damn cable company kept changing DNS on me. Now I just set it for DHCP and thats that. I can play Quake and everything else. I WOULD NOT give some one info that Im not sure about buddy.
Your the one giving him more work than it is. Whats your problem with the router auto assigning an IP to his machines. When I have LAN parties all I have to is plug my friends machines in and everything is auto. Ive connected the router to Win 98, ME, 2000 and Xp using DHCP.
Ok, Terra, you are correct, of course a person could run DHCP, but that is like using two parachutes while jumping out of a plane. Yes, you need a parachute, and if your lucky, you may not splat on the ground like a bug, but there is a GOOD chance that when Using the two chutes (aka the router's its own DHCP server, and the DHCP option itself) there is a bigger chance of them getting intertwined (confused) and you falling to the ground.
What I am trying to say is, you dont need to run DHCP. It is an advanced feature for running a Large network, just like dynamic routing is (using more than one router/hub). If you still believe so, then answer me this, why on that page can you have up to 255 computers on DHCP, but you only have 4 ports ( on the 4 port router). If you can explain this to me, then I will halfway believe that you acutally know what DHCP is and what it does. Instead of using DHCP, just enter an assigned IP that will be given to that client pc from the router, aka 192.168.1.2 in the network settings on the client pc. What this is for is if you are on a big network and trying to find a specific computer if you dont know the domain name and the firm identifies the computer by IP addy and not the computer name, aka Lan messaging, or setting up a Lan webserver. You have to know the IP of the host computer that is hosting the Webserver when setting that up, you cant just set the IP as the host compters name description. This is the MAIN reason why.
Yes, DHCP will work, but its more extra work to confuse a FIRST TIME USER setting up his router. You dont need to put in extra steps to confuse a person unless they know what they are doing.
Terra, if you have multiple pc's on a router, lets say 5, 2 run 24/7, you never shut them down. The other 3 shutdown here and there, some at the same time, some not. Say computer #1, 2 and 3 shutdown, computer #1 had IP 192.168.1.2 #2 had 192.168.1.3 and #3 had 192.168.1.4. Now, shutdown all three of them, then boot the computers in reverse order. I guarantee you that when booted back up, they will have a different assigned IP address. #3 would have 192.168.1.2 #2 would have the same ironically cuz its the middle pc 192.168.1.3 and pc #1 would have 192.168.1.4 . Complete reversal. Now lets say you had a FTP server installed on pc #1, and the original settings were for it to echo a request from a client on port 21 from 192.168.1.2 (when forwarded on the port forward page). Well, those settings would now correspond with pc #3 since it now wears the assigned IP of 192.168.1.2 and the ftp server host pc now wears 192.168.1.4 since you are using auto-detect IP. This is the same when hosting a Lan Webserver for your network to view. This is the second main reason why you would assign IP's on the network by putting them in the client pc's network settings, to stop confusion, and having to always enter "ipconfig" to figure out what IP the FTP server is host pc is now wearing, and having to change the settings in your Linksys browser.
Now after all that typing to hopefully explain in detail what is the easiest and much less confusing with the least amount of steps to setup this router, Tundra could have had this up in running in no time.
Tundra, basically, if you read the manual, its alot better than having to call the tech support, you will actually probly hear them turning the page of the same book you have. And dont try email ever, its not any better.
Posted by LPDad:
How you set your linksys up to connect depends on the type of protocol your isp uses. (mine uses ppoe, so I must make sure the ppoe box is checked.
Check again LPDad and see if you are running your connection over TCP/IP. PPOE is settings the company runs, used for data travel, or MTU, or Maximum Transfer Unit.
Tundra, you will also see MTU at the bottom of the linksys browser home page. Most cable ISP's should be 1500, some are not, I wouldnt worry about this either, XP will determine the MTU string. If you really want to figure it out, ping your isp with a packet of 1500, and see if it needs to be defraged to be sent, aka % loss
Your ISP internet specialist should tell you what the MTU is, if he even knows himself.