Can't find Router, but can find other computers.

[the_master_josh]

I'm trying to fix a network that shares a cable internet connection using a Linksys router(BEFSR41). I need to connect a Windows 2000 and an NT 4.0 workstation. Currently I can get the two computers to see each other but only the NT one will access the internet.

The 2000 computer can access the NT computer via the network but cannot find the router even when I enter the ip address of the router manually. I can still access the NT computer via My Network Places. I also have the TCP/IP protocol installed on the local area network connection.

Any ideas on what I'm missing? I'm very new to networking but I do understand a few basics.

[iamien]

sorry but you have both plugged into router correct? not one into router other in other computer <ya stupid question just soudned that way>

[the_master_josh]

Both computers talk to each other through the router. The 2000 machine can ping the router using the command prompt but not with internet explorer. That's the weird thing. The connection through the router is okay, but the 2000 machine still can't access the internet through the router. I am set up with AT&T (now comcast) for two computers so I also know that isn't the problem.

I've done everything the router installation software said to do but it hasn't helped. The software still can't find the router.

[Kodo]

make sure your gateway is set to the IP of the router and that your DNS servers are that of your ISP's DNS servers. I find that I cannot access the net with win2k or XP on a linksys unless I do this.

[the_master_josh]

I just spent over two hours with technical support for the ISP. Did all the standard manual setup procedures and technical guy couldn't figure out why it wouldn't work. He even asked some of his "techie buddies" if they had any suggestions they didn't. I did all this though without the router, just the 2000 machine and the cable modem.

It was wierd because everything was plugged in correctly and working (technical support had to double check for me). Since the computers could still share files over the network I know all the devices were working probably.

Since everything else works fine I'll just have to diagnose it as a windows problem. Guess I'll just have to bite the bullet and reformat and install windows again. Good thing the computer has a second 120 gig hard drive.

Thanks for the suggestion about the default gateway and DNS servers. It didn't work this time, but it will come in handy to have that little piece of knowledge next time.

[gigs_42]

You could also try completely resetting the router: I have the same model and this fixed all of my problems, even though I had to run through all of the setup procedures again. Just stick a pen in the hole, and be sure to hold it in for 10 seconds, otherwise you'll just restart the router.

[Iceburg]

I have the same router, and it has a firewall built into it. Make sure that you have the internal DHCP turned on, and on both of the machines make sure that they are running DHCP. If the router supplies the IP address then I can be up and running, if I try to statically assign one to my 2K server, then it won't route (without some tweaking)

[Kodo]

routers don't have firewalls built into them.. by nature, a router IS a firewall..
Sorry, just a pet peeve.

[the_master_josh]

I did all those things twice. Once by myself the other time with technical support. I'm thinking it is just a problem with the installation of Windows 2000 since technical support did all these things. I did do all the automation stuff necessary with DHCP and even tried just emulating the addresses from the working computer (DNS servers and what not). I'm thinking it is just a problem with the installation of Windows 2000 since technical support did all these things.

Thanks again for all the help.

[Kodo]

have you tried uninstalling TCP/IP -reboot- and reinstall it?

[Iceburg]

Kodo, I hate to argue with the master but wouldn't you say that firewalls are routers, but routers aren't always firewalls? The only thing that routers filter are IP addresses, and they "route" information across the internet, and LAN, while on the other hand, firewalls are screening packets, analyzing headers, ports, data, etc. I disagree.

Master Josh, reinstalling Windows 2000 isn't going to change anything that unistalling TCP/IP is doing. Do you have a software firewall running, or that Norton system works, or anything that would be blocking traffic? There has to be an easy explanation for this.

-Nick

[the_master_josh]

Originally posted by Iceburg
...reinstalling Windows 2000 isn't going to change anything that unistalling TCP/IP is doing...

I can't uninstall The TCP/IP software. It says that some unix print sharing service or something is using that and uninstallation cannot continue. I've tried searching for it via services and what not to no avail.

Just remember that everything else works. The two computers can share files through the router (router and NIC work). Since one computer works fine with the setup I also know it's not the modem or the internet service itself.

[Kodo]

Originally posted by Iceburg
Kodo, I hate to argue with the master but wouldn't you say that firewalls are routers, but routers aren't always firewalls? The only thing that routers filter are IP addresses, and they "route" information across the internet, and LAN, while on the other hand, firewalls are screening packets, analyzing headers, ports, data, etc. I disagree.

Master Josh, reinstalling Windows 2000 isn't going to change anything that unistalling TCP/IP is doing. Do you have a software firewall running, or that Norton system works, or anything that would be blocking traffic? There has to be an easy explanation for this.

-Nick

a router can blocks ports. packets travel over ports.. there are advanced firewalls and there are basic firewalls. as long as there is a port blocking going, it is a firewall. Routers are firewalls.

[Iceburg]

Anyway, back to the issue, any new news on getting the box running?

[the_master_josh]

My dad sent the computer to a network guru friend without telling me (he has so little faith in me). I wasn't able to reinstall Windows but I bet that's what will happen with the computer since windows because Windows itself was acting up (couldn't uninstall programs, crashing a lot, etc). Luckily all the important stuff is stored on a second 120GB hard drive so reformating the master drive won't be a problem.

[the_master_josh]

The guy my dad had taken the computer to gave us some good news. He finally nailed it down to the onboard NIC after reinstalling the chipset drivers. He said that onboard NICs are unreliable. We went down to local computer store and bought a cheap NIC.

I Haven't tried it out since we also upgraded the master hard drive and am currently waiting till tomorrow morning to pick it up. He agreed to reinstall all the drivers and stuff if we gave him the old hard drive.

Thanks for all the help again. Surprisising it was hardware issue that wasn't human error.

[Iceburg]

Probablly a good assumption, well good luck on it.
-Iceburg

[Iceburg]

Should get Linux put on it next time. =)

[the_master_josh]

Tried the new computer Saturday, and it works great. Tried it with the built in NIC, no go. But with the new NIC it works great. thanks for all the help. Wierd problem since the NIC half worked.

Maybe dumb question, but did you have IE set to auto detect proxy settings on the onboard? Also, make sure that you have an internet connection set up via LAN for IE.... just my $.02

187