|issues with home networking|
| 4:36 pm on Nov 7, 2006 (gmt 0)|
I have a static IP from my ISP and 2 nics in my main machine. I have the incoming cat5 going into the machine, and from the other nic, have a cat5 going to my hub (I have a router also but I'm just using a hub for now)..
I can ping outside from the main machine, I can get on AIM... I cannot browse the web, IRC, get email, etc... It resolves because I can ping duke.edu also.
I cannot ping the other machine on my network. They're both on the same workgroup (OFFICE), I'm lost...
Anyone have any ideas on what could be going wrong?
| 4:51 pm on Nov 7, 2006 (gmt 0)|
Make sure that the ISP-connected NIC and your internal LAN have correct IP address ranges. The ISP NIC should be set to whatever static IP address is assigned by your ISP (set it up with the ISP-specified DNS aerver IPs as well).
The internal LAN should be set to any of the common non-routable IP address ranges, such as 192.168.x.y. The ISP-connected machine's LAN NIC IP address should be specified as the Gateway IP address for the other machines on the LAN.
In order to use the internet from the LAN machines, you will need to enable internet connection sharing in the ISP-connected machine.
It will be easier to get this working if you first disable your local network-attached NIC, and get the ISP-connected machine completely working first. Then deploy your LAN.
Multi-homed setups with ICS like this are problematic, though, and I'd recommend that you simply use the router as the single point of contact to the the ISP, with all the PCs as peers on the LAN side of the router.
| 5:01 pm on Nov 7, 2006 (gmt 0)|
I had the network working half way with my router...
I couldn't FTP, or use several programs, but the browsing would work from all sides...
The problem was my router wasnt port forwarding so I could run my webserver, so that's why I went the route I'm on now with the 2 NICS...
Do you have any idea why I could ping out, but not browse, irc, ftp, email, etc? What could be stopping that?
Also, on my LAN NIC, what should I specify as my gateway, ip, dns, etc... 192.* as the IP i'm sure, as well as default subnet, but what about gateway and dns servers? ... on the network machines, should I set them as a static IP, 192.*, and if so, what should I use for their gateway, subnet, dns, etc?
| 5:29 pm on Nov 7, 2006 (gmt 0)|
The easiest approach would be to set up the ISP-connected NIC using the IP address, DNS server addresses, netmask, and default gateway as specified by your ISP. Since you'll need ICS to connect the LAN-side machine to the internet through this machine, you could just set them up as "Get IP address automatically" and "Get DNS automatically." In this case, ICS will act as a DHCP server, and assign the IP addresses for the LAN side.
However, if you have a mixed WinXP/Win2k/WinME/Win98 OS environment, then don't do that -- DHCP often causes problems with file and printer sharing in mixed-OS environments.
If you don't want to use DHCP, then assign the ISP-connected machine's LAN IP as 192.168.0.1, and set the other machines to use that address as the gateway. Assign 192.168.0.1 as their gateway addresses. Use the same DNS server IP addresses as you have set in the ISP-connected machine.
Assign each LAN-side machine a unique address in the 192.168.0.2-254 range. I guess I should mention that I'm assuming the default netmask of 255.255.255.0 here.
The ability to ping but not use other protocols sounds like a DNS problem, assuming that you're pinging IP addresses. However, if you are pinging by domain name, then those domains may have been cached in your local DNS cache, and therefore are working even though network DNS is not working. One way to test this is to go to Start->Run enter "Cmd", and then type "ipconfig /flushdns" in the DOS command window. This will flush your local DNS cache, and if the main problem is DNS, then your pings by domain name will all fail, while pings by IP address will still work. However, this would still leave you with the question of why ICMP (ping) works, but other protocols don't...
Again, the process will be much easier if you disable your ISP-connected machine's LAN-side NIC, and get just that machine working on the internet first. You can go to View Network Connections and right-click-disable the LAN-side NIC to isolate the 'two sides' of the ISP-connected machine.
As to your router, I'll have to refer you to the router manufacturer's Web site for information on how to do port-forwarding with it -- There are simply too many variations in router setup to guess about it here.
| 8:57 pm on Nov 7, 2006 (gmt 0)|
Ok... Now that the network is squared away...
Any ideas on why I wouldn't be able to hit outside?
I've input all of the IPs as my ISP has given me, but still no luck. Their DNS servers aren't down because my inlaws aren't having issues and they live right behind me, and hit the same tower (we're on wireless)
| 10:48 pm on Nov 7, 2006 (gmt 0)|
Make sure that the gateway IP for the ISP-connected machine points to the ISP-specified gateway. Otherwise, that machine, like the others, won't have a way to route outside of your LAN.
And again, disabling the LAN-side NIC on the ISP-connected machine will help to break this problem up into smaller chunks if the above doesn't help.
To be clear, the ISP-connected machine is the (internet) gateway for your LAN. The wireless modem (probably on your roof) is the gateway for the ISP-connected machine.