Kevin McGregor wrote:
Well, no. By default, Shaw gives out one IP address per cable modem, so if you change the connected device from the original router you tried, to something else, it ignores the new device. Sometimes powering down the cable modem (and waiting... hours? Days?) helps, but the better solution is to call Shaw Internet tech support and tell them you want your free second IP address activated.
I only need one address. I just need the NIC to get it. I was trying to bypass the firewall to see if that's where the problem was.
I am guessing the firewall is NOT the problem: 1) I can connect on another machine on the LAN that should be handled the same way by the firewall. 2) The second app used to work with the same firewall on the first machine.
Could a NIC 'partly' fail so that it can't accept an address by DHCP and will fail with some connections but not others?
You may still have to power down and up the cable modem after they do this. Shaw provides all Internet users with two IP addresses, but the second one has to be activated on request.
After that, you can try plugging in your computer or other device to the cable modem to do tests - although I'd be loathe to do that with a Windows 2000 machine.
Kevin
Dan Martin wrote:
I have a home LAN that uses a iptables firewall running on FC 4 on my gateway machine. I run Win2K on an internal LAN machine that I use to run (among other things) 2 applications that contact remote servers. Using SNAT in iptables, everything seemed to run fine, since all communications with the servers were initiated on my end and return packets were appropriately translated back. ...
I plugged my Win2K machine directly to the cable modem and configured it to connect by DHCP. I could not get an address for it. Shaw believes the modem is working and trying to assign an address.
...
It is suspicious that the NIC would not configure when plugged to the cable modem - but everything else works. I can browse the web and get my mail.
Is this consistent with a NIC failure? could it be something else?
Yes, you only technically need one address, but my point was you may need the second one because the cable modem won't reassign the first one to the second device. I was suggesting a free workaround for the way the cable modem works, not because you 'need' a second address.
Anyway, at this point I doubt it's the NIC. DHCP and port connections are all handled by the host OS's TCP/IP stack, not the card.
Dan Martin wrote:
Kevin McGregor wrote:
Well, no. By default, Shaw gives out one IP address per cable modem, so if you change the connected device from the original router you tried, to something else, it ignores the new device. Sometimes powering down the cable modem (and waiting... hours? Days?) helps, but the better solution is to call Shaw Internet tech support and tell them you want your free second IP address activated.
I only need one address. I just need the NIC to get it. I was trying to bypass the firewall to see if that's where the problem was. I am guessing the firewall is NOT the problem:
- I can connect on another machine on the LAN that should be handled
the same way by the firewall. 2) The second app used to work with the same firewall on the first machine.
Could a NIC 'partly' fail so that it can't accept an address by DHCP and will fail with some connections but not others?
You may still have to power down and up the cable modem after they do this. Shaw provides all Internet users with two IP addresses, but the second one has to be activated on request.
After that, you can try plugging in your computer or other device to the cable modem to do tests - although I'd be loathe to do that with a Windows 2000 machine.
Kevin
Dan Martin wrote:
I have a home LAN that uses a iptables firewall running on FC 4 on my gateway machine. I run Win2K on an internal LAN machine that I use to run (among other things) 2 applications that contact remote servers. Using SNAT in iptables, everything seemed to run fine, since all communications with the servers were initiated on my end and return packets were appropriately translated back. ...
I plugged my Win2K machine directly to the cable modem and configured it to connect by DHCP. I could not get an address for it. Shaw believes the modem is working and trying to assign an address.
...
It is suspicious that the NIC would not configure when plugged to the cable modem - but everything else works. I can browse the web and get my mail.
Is this consistent with a NIC failure? could it be something else?
On 02/14/2008 05:49 PM, Dan Martin wrote:
Could a NIC 'partly' fail so that it can't accept an address by DHCP and will fail with some connections but not others?
Our experience has been that NICs can fail almost as frequently as hard drives (particularly older ones seem to burn themselves out or something). They can also fail in unexpected ways. We had one that did the opposite of what you describe: it got its settings by DHCP (though not without a lot of haggling back and forth), but then wouldn't work consistently enough to allow a TCP connection to anything. Probably an extremely high error/retry rate.
Anyway, if you suspect the NIC, it's usually a fairly quick and easy fix to install a new one and see if that clears up the problem.
I have a LAN which uses static private IP addresses. The machines are connected to one another by a hub. The gateway machine is a Linux box running iptables . This has worked well with one recent exception which is likely a failed NIC, and it provides a means of examining traffic.
I just purchased a Mac and want to add it to the network. It is in a place where there are no cables at present.
I should have purchased a wireless adapter for the gateway machine, but instead I purchased the Airport Extreme Base Station. In hindsight, I don't really need a router - but is there a way to use it to simply get my Mac onto the network?
In setup, the airport base station insisted on having something plugged into the WAN port, so I eliminated the hub, plugged the gateway machine's LAN side ethernet into the WAN port of the airport, and plugged the other wired LAN machines into LAN ports. All the wired machines are able to browse the internet (though I'm guessing everything is NATd twice - once in the router and again in the gateway machine).
I have not been able to get internet access through the wireless on my Mac.
Is there a simple way to use this device as a simple wired and wireless 'switch' on my LAN? or should I simply throw in the towel and let the base station be a router and firewall, and do away with a gateway computer?
Dan Martin wrote:
Is there a simple way to use this device as a simple wired and wireless 'switch' on my LAN? or should I simply throw in the towel and let the base station be a router and firewall, and do away with a gateway computer?
There is no problem doing double Nat but you should be able to set it up just a switch.
- turn off DHCP on your airport. - make sure the LAN network is the same subnet as your current LAN. - assign an unique address to the airport router within your current LAN subnet - make sure the wireless Mac's gateway address is pointing to your current gateway.
-- Bill
Thanks Bill!
It seems to work. Took me quite a while to find where I could manually enter the IP address of the Mac's own wireless adapter, harder than actually configuring the router.
After giving them both local LAN IP addresses, I have internet access.
I'll leave transferring files between PC and Mac for another day.
Bill Reid wrote:
Dan Martin wrote:
Is there a simple way to use this device as a simple wired and wireless 'switch' on my LAN? or should I simply throw in the towel and let the base station be a router and firewall, and do away with a gateway computer?
There is no problem doing double Nat but you should be able to set it up just a switch.
- turn off DHCP on your airport.
- make sure the LAN network is the same subnet as your current LAN.
- assign an unique address to the airport router within your current
LAN subnet
- make sure the wireless Mac's gateway address is pointing to your
current gateway.
-- Bill
-
Bill Reid -
Dan Martin -
Gilles Detillieux -
Kevin McGregor