Mark Foster <blakjak@blakjak.net> wrote:

> Lets not let this get blown out of proportion.
>
> Chrissy - Problems with your connection should ALWAYS go to your ISP
> helpdesk first. I dont know why youd even consider using the adsl
> discussion list for this - whilst you use DSL, your problem is not
> specifically related to DSL and as much as we are able to render
> assistance, we are NOT a helpdesk. If this list (which is informal, and
> was created by enthusiasts, not people professionally involved per se)
> didnt exist, would you have considered emailing someone for help? I think
> not - thats what helpdesk is for.
>
> FWIW all the suggestions ive seen on the list so far are exactly what I -
> as a helpdesk employee - would go through with you. Call your helpdesk.
>
> Next time, try your helpdesk first... its all about context.

  It's worth noting that Chrissy did later say that she'd called the
helpdesk several times - but yes, that should have been noted in the first
post. (Chrissy: No, we can't assume that you've done that already, for
exactly the same reasons that helpdesk staff cannot assume that callers
have already checked the power cable. Troubleshooting *always* starts
with the basic steps if we (the troubleshooters) aren't explicitly told
that they've already been checked, and sometimes even if we are.)

  So. From what I understand:

- Ring the helpdesk: done, they say it's Telecom's problem.

- Contact Telecom: done, they admit it's a problem at their end and say
they'll fix it.

- Telecom haven't fixed it yet. This is where we are now.

  There is almost certainly nothing anyone on this list can do about the
problem - even Wayne, as I don't think this is his area. I don't know
whether Telecom's complaints department covers stuff like this, but
they're one place to try. If the problem persists, then do the usual
stuff - record the name of the person you talked to, what exactly they
told you would be done, and the time that they told it to you. This is
neither ADSL- nor Telecom-specific, just the way you deal with large
companies when things aren't working.

  Now, as to the problem. Getting a .255 address is quite likely the
problem, but it might not be. To know whether it is or not, we'll need to
know what netmask you're being given along with the IP address. On an
M1122, you can find this under Statistics -> Interfaces, immediately
following the IP address.

  Usually this will be something like 255.255.255.0. My work connection
has a netmask of 255.255.255.128, but that may be because of the way
Telecom routes for static addresses. If the netmask is wider than
255.255.255.0 (that is, the third octet is less than 255), then a .255 IP
address isn't a problem in and of itself. If the third octet is 255,
though, then a .255 IP address is a broadcast address, so getting one
yourself is a Bad Thing.

  Assuming that the address is the problem (very likely, but not yet
certain), then it doesn't actually solve anything - it's still probably
something Telecom have to fix. But at least then you'd know for sure what
they need to fix, which might help in your dealings with them.

> Thanks guys and remember - for connection problems RING YOUR ISP FIRST! :P

  What he said.

   Jonathan

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message