I feel your pain, but keep this all in perspective. You will
ultimately be able to get some form of high speed data over
cable access. Where I live here in the PRNV( People's Republik
of Northern Virginia), I am within 20 miles of five of the
world's largest ISPs. The best access I can get is a 56k
dialup line. //RANT OVER//
Now, regarding the less than tactful "engineer" who is trying
desperately hard not to help you, it would appear that he is in
over his head. It may be useful to do a little troubleshooting
on your own.
For example, you are given a reasonable indication that this
cable operator favors using the low end addresses for a gateway
on a particular segment. The issue is what segment are you
actually on? Give the scope information you provided, here are
some of the possibilities:
24.65.134.1 to 24.65.135.254 (assume 24.65.134.1 is the
gateway). From your router, you will need to temporarily go
back to hard coded IP addresses. Set your IP address to
24.65.134.40 and a subnet mask of 255.255.254.0 and see if you
can reach your gateway(I can from my house - if it's yours).
If the answer is yes, you can reach it as well, then this can
be communicated to the fine staff at your local cable
operator. If OTOH, you cannot reach that gateway, you are
probably on another IP subnet.
The logical next choice would definitely be to try and reach
24.65.142.1. The problem is that your IP addr is not from that
subnet. As much as I hate to suggest this, go ahead and hard
code on your router an IP addr from the subnet this gateway is
from(choices are 24.65.142.2 through 24.65.143.254) I would
probably go with a high value near the end of the range (say
24.65.143.241). See if you are now able to reach the gateway.
One of these two methods will work (most likely the first
method).
Once you are clear exactly what subnet you are on, I suspect
you could probably hard code the values in your router until
somebody that has a brain can fix the DHCP server.
Additionally, you will also need to track down the other DHCP
options that are handed out. When I tested this a little while
back, I believe that the DHCP client on the router did not
necessarily accept all options that were passed from the DHCP
server. Probably the most important ones you will need are the
DNS servers. Once you have the correct info, you then will
have all the necessary parameters to program your DHCP server
on your private network for the hosts in your home.
There is one other tactic you may want to use as well. If push
comes to shove and they absolutely refuse to deal with you and
your cisco router, then go to one of your PCs and get the MAC
address from the NIC card. Go to the router interface facing
the cable modem and enter the following command on that
interface:
router(config)#int e0
router(config-if)#mac-address (your PC's MAC addr)
router(config-if)#shut
router(config-if)#no shut
router(config-if)#end
When they call back and attempt to troubleshoot, play along
with them. When they tell you to look at "winipcfg", you know
where to go on your router to get the info that you need.
Sometimes, you need to get into the head of the person you are
dealing with and put it in terms they can understand.
Hang in there :-) Let us know if you achieve victory.
v/r,
Paul Werner
> Well, I've found the IOS that runs DHCP client, and I've
found the
> command.
> I've just spent the past 4 hours trying to resolve why I'm
getting
> encapsulation failure messages after the DHCP Offer is made
from the
> service
> provider (Shaw @ Home) and have discovered the following:
>
> My IP Address: 24.65.134.40
> Subnet Mask: 255.255.254.0
> Gateway: 24.65.142.1
>
> Anyone see a problem?
>
> If you do, then you're one up on Shaw Cable's technical
support. They
> won't
> look at the problem because it's a Cisco router at the other
end--an
> unsupported device. But the device isn't the problem--their
scope
> configuration is.
>
> No, I can't get any information on who it is that I'm
speaking with
> other
> than his name is Darren.
>
> No, I can't speak to a supervisor.
>
> And no, I can't continue talking either because I've just
been hung up
> on.
>
> What excellent customer service. Just what exactly is
technical support
> for?
>
> So if anyone out there knows anyone at Shaw, they might want
to mention
> their problem to them. And no, I'm not just talking about
their
> interpersonal skills.
>
> So thanks to everyone who tried to help me get this going...
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16858&t=16746
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
