On Apr 2, 2012, at 7:32 AM, "Dave" wrote:
> On 1 Apr 2012 at 19:05, Jerry wrote:
>
>> On Mon, 02 Apr 2012 08:50:42 +1000
>> Da Rock articulated:
>>
>>> Given that the other tech in question asked me to help him, and he
>>> is a Winblows nut like yourself, I think this premise can be
>>> dismiss
On Mon, 02 Apr 2012 15:18:19 +0100
Dave wrote:
> fbsd8
>
> How do you connect to your TW ISP? Just a Cable modem of some sort,
> or is there a Router involved somewhere? It makes a whole world of
> difference
If you read the rest of the thread you'll see that that the problem
was solve
On 1 Apr 2012 at 19:05, Jerry wrote:
> On Mon, 02 Apr 2012 08:50:42 +1000
> Da Rock articulated:
>
> > Given that the other tech in question asked me to help him, and he
> > is a Winblows nut like yourself, I think this premise can be
> > dismissed out of hand. I won't even bother to qualify the r
On 1 Apr 2012 at 10:21, Erich Dollansky wrote:
> Hi,
>
> On Sunday 01 April 2012 08:57:00 Da Rock wrote:
> > >
> > > Did they come to your location and run a test to their equipment?
> > > My neighbor had a recent cable outage of an existing cable on our
> > > block that was too low and a moving
On Mon, 02 Apr 2012 08:50:42 +1000
Da Rock articulated:
> Given that the other tech in question asked me to help him, and he is
> a Winblows nut like yourself, I think this premise can be dismissed
> out of hand. I won't even bother to qualify the rest, I wouldn't want
> to ruin your delusion.
No
On 04/02/12 08:41, Jerry wrote:
On Mon, 02 Apr 2012 08:20:02 +1000
Da Rock articulated:
Both networking in FreeBSD _and_ Winblows can be difficult at times.
My point is that Winblows is not some magical fairy that can make
everything better. It doesn't. It quite often gets it wrong, and when
it
On Mon, 02 Apr 2012 08:20:02 +1000
Da Rock articulated:
> Both networking in FreeBSD _and_ Winblows can be difficult at times.
> My point is that Winblows is not some magical fairy that can make
> everything better. It doesn't. It quite often gets it wrong, and when
> it does its a b**ch to fix-
On 04/02/12 04:10, Fbsd8 wrote:
Well here is the results of my attempts to connect to Time Warner
cable network.
After 4 calls to their call center which was in the Philippines where
all the people just read a scripted answer FAQ and only had the
ability to remotely reset the modem. I finally
On 04/02/12 02:29, Jerry wrote:
On Mon, 02 Apr 2012 01:27:36 +1000
Da Rock articulated:
Until it loses that configuration and you're expected to delete it
and re-enter the connection details...
Or until elephants fly, or whatever.
No. This is the common mantra for any Windows net technician.
On Sun, 01 Apr 2012 14:10:52 -0400
Fbsd8 articulated:
> Well here is the results of my attempts to connect to Time Warner
> cable network.
>
> After 4 calls to their call center which was in the Philippines where
> all the people just read a scripted answer FAQ and only had the
> ability to remo
Well here is the results of my attempts to connect to Time Warner cable
network.
After 4 calls to their call center which was in the Philippines where
all the people just read a scripted answer FAQ and only had the ability
to remotely reset the modem. I finally requested to talk to the top
su
On Mon, 02 Apr 2012 01:27:36 +1000
Da Rock articulated:
> Until it loses that configuration and you're expected to delete it
> and re-enter the connection details...
Or until elephants fly, or whatever.
> Explain why it would be so hard to configure various functions as
> file sharing and some o
On 01/04/2012 15:59, Jerry wrote:
> Mathew, I don't know if it is as cut and dry as that. The OP claimed
That's Matthew with two t's.
> that his Microsoft PC connected properly but not his FreeBSD machine.
> That, in itself, is certainly not surprising. I have always had better
> luck setting up
On 04/02/12 00:59, Jerry wrote:
On Sun, 01 Apr 2012 15:35:02 +0100
Matthew Seaman articulated:
On 01/04/2012 14:35, RW wrote:
I had a modem that did something similar, it issued a temporary
private ip address and the replaced it with a routable address.
It's fairly sad that they don't use the
On Sun, 01 Apr 2012 15:35:02 +0100
Matthew Seaman articulated:
> On 01/04/2012 14:35, RW wrote:
> > I had a modem that did something similar, it issued a temporary
> > private ip address and the replaced it with a routable address.
>
> It's fairly sad that they don't use the officially mandated[*
On 01/04/2012 14:35, RW wrote:
> I had a modem that did something similar, it issued a temporary private
> ip address and the replaced it with a routable address.
It's fairly sad that they don't use the officially mandated[*]
169.254.0.0/16 netblock which is what DHCP clients/servers are supposed
On Sun, Apr 1, 2012 at 9:35 AM, RW wrote:
> On Sat, 31 Mar 2012 20:52:26 -0400
> Fbsd8 wrote:
>
>> Da Rock wrote:
>> > On 04/01/12 09:52, Fbsd8 wrote:
>> >> Just purchased an account on the northern Ohio Time Warner cable
>> >> system. Having problem connecting to their service. Seems their
>> >>
On Sun, 1 Apr 2012 14:35:41 +0100
RW wrote:
> The difference here is that the DHCP server is in a different address
> block to the DHCP server,
That should be: "the temporary address is in a different address
block to the DHCP server"
___
freebsd-que
On Sat, 31 Mar 2012 20:52:26 -0400
Fbsd8 wrote:
> Da Rock wrote:
> > On 04/01/12 09:52, Fbsd8 wrote:
> >> Just purchased an account on the northern Ohio Time Warner cable
> >> system. Having problem connecting to their service. Seems their
> >> dhcp server has an ip address of 10.2.0.1 which is no
On 04/01/12 14:06, Outback Dingo wrote:
On Sat, Mar 31, 2012 at 11:21 PM, Erich Dollansky
wrote:
Hi,
On Sunday 01 April 2012 08:57:00 Da Rock wrote:
Did they come to your location and run a test to their equipment? My
neighbor had a recent cable outage of an existing cable on our block
that
On Sat, Mar 31, 2012 at 11:21 PM, Erich Dollansky
wrote:
> Hi,
>
> On Sunday 01 April 2012 08:57:00 Da Rock wrote:
>> >
>> > Did they come to your location and run a test to their equipment? My
>> > neighbor had a recent cable outage of an existing cable on our block
>> > that was too low and a m
Hi,
On Sunday 01 April 2012 08:57:00 Da Rock wrote:
> >
> > Did they come to your location and run a test to their equipment? My
> > neighbor had a recent cable outage of an existing cable on our block
> > that was too low and a moving van hit it.
>
> Apparently the Windows system works, so I'
Hi,
On Sunday 01 April 2012 06:52:48 Fbsd8 wrote:
> Just purchased an account on the northern Ohio Time Warner cable system.
> Having problem connecting to their service. Seems their dhcp server has
> an ip address of 10.2.0.1 which is not public routable. I know my
> Freebsd 8.2 box functions b
On 04/01/12 11:22, Al Plant wrote:
Da Rock wrote:
On 04/01/12 10:52, Fbsd8 wrote:
Da Rock wrote:
On 04/01/12 09:52, Fbsd8 wrote:
Just purchased an account on the northern Ohio Time Warner cable
system.
Having problem connecting to their service. Seems their dhcp
server has an ip address of 1
Da Rock wrote:
On 04/01/12 10:52, Fbsd8 wrote:
Da Rock wrote:
On 04/01/12 09:52, Fbsd8 wrote:
Just purchased an account on the northern Ohio Time Warner cable
system.
Having problem connecting to their service. Seems their dhcp server
has an ip address of 10.2.0.1 which is not public routable
On 04/01/12 10:52, Fbsd8 wrote:
Da Rock wrote:
On 04/01/12 09:52, Fbsd8 wrote:
Just purchased an account on the northern Ohio Time Warner cable
system.
Having problem connecting to their service. Seems their dhcp server
has an ip address of 10.2.0.1 which is not public routable. I know
my Fre
Da Rock wrote:
On 04/01/12 09:52, Fbsd8 wrote:
Just purchased an account on the northern Ohio Time Warner cable system.
Having problem connecting to their service. Seems their dhcp server
has an ip address of 10.2.0.1 which is not public routable. I know my
Freebsd 8.2 box functions because it
On 04/01/12 09:52, Fbsd8 wrote:
Just purchased an account on the northern Ohio Time Warner cable system.
Having problem connecting to their service. Seems their dhcp server
has an ip address of 10.2.0.1 which is not public routable. I know my
Freebsd 8.2 box functions because it worked fine und
Just purchased an account on the northern Ohio Time Warner cable system.
Having problem connecting to their service. Seems their dhcp server has
an ip address of 10.2.0.1 which is not public routable. I know my
Freebsd 8.2 box functions because it worked fine under att service which
I just left
29 matches
Mail list logo
