Re: cable modem and ISA 2004
- From: "Brian Cryer" <not.here@localhost>
- Date: Tue, 5 Aug 2008 09:22:57 +0100
"bgreg" <bgreg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E7018298-29F3-404C-A795-86FD707B3E31@xxxxxxxxxxxxxxxx
Recently switched from Verizon DSL to cable modem provided by Cablevision in
NJ. With DSL I had external NIC set to 192.168.1.3 and connected patch cable
to DSL modem/router at 192.168.1.1. Inside nic to 172.25.10.3. Worked well
for years. With cable config using cable modem Motorola SBV5222 a router must
be used. Purchased Linksys BESFR41. From ethernet port of cable modem I
connect to ethernet port of Linksys router. IP address of cable modem is
192.168.100.1 so I configured ethernet port of Linksys to 192.168.100.5 and
external nic to 192.168.100.3, 255.255.255.0 with gateway
192.168.100.5(Linksys)I logged in to linksys and get external address and DNS
listed as 167.206.245.129 & .130. Have rerun CEICW mutiple times using DNS
addresses listed by Linksys. I cannot get out to internet at server or any
workstations on LAN. If I connect LAN card directly to cable modem and allow
DHCP at LAN card, I can connect. Same occurs at at workstation. I 've
observed logging at ISA 2004 and connection is opened and closed at port 53.
It seems that it is being blocked. Anyone had similar problems with Cable
modem /cable ISP blocking specific ports. Ports are listed open (stealth
mode) via GRC's Shields up. Anyone experienced similar issues?
This isn't the problem, but you shouldn't NEED a router. You should be able to plug directly from the cable modem to your NIC as you did before. Most people use routers because its convenient, but you should be able to connect as you did before with the cable modem connected via a patch cable directly to your NIC. Sorry, just read that it does all work if you do this. In which case I expect its either a default gateway or dns issue. A router will normally block incoming ports unless you open them, but not outgoing.
I'd concentrate first on ensuring that you can connect to the internet on your server. If you start a command window then try the following:
nslookup www.cryer.co.uk 192.168.100.5
this is asking 192.168.100.5, i.e your router, to resolve the name www.cryer.co.uk. It should be successful. If it isn't then your router either isn't providing DNS (which it should be) or isn't connected to the internet - so the problem could be with your router, modem or cable company, but probably your router.
ping 69.89.27.225
this is the ip address that should be returned from your ns-lookup. If it works then your server is connecting to the internet - at least at the ip level, so 90% of the way there. If it doesn't work then I suspect that your default gateway isn't pointing to your router.
ping www.cryer.co.uk
assuming that the ping by ip address worked then this is by name. The difference is that it will use the dns servers to resolve the name. I'm assuming that your network is configured to use your server as your DNS server. In which case if this step doesn't work but the previous did then your DNS server isn't configured correctly.
Let us know how you get on.
--
Brian Cryer
www.cryer.co.uk/brian
.
- References:
- cable modem and ISA 2004
- From: bgreg
- cable modem and ISA 2004
- Prev by Date: Re: Windows SBS 2003 backup restoring with XP Pro.
- Next by Date: Re: 75 users limit
- Previous by thread: cable modem and ISA 2004
- Next by thread: Re: cable modem and ISA 2004
- Index(es):
Relevant Pages
|
