On 05/27/11 16:59, Tim wrote:
> Their all-in-one service is, most likely, aimed at the average computer
> illiterate person who has one or two computers, doesn't really do
> anything special with them, is used to general Windows crappiness, and
> will also put up with the same crappiness in other g
On Fri, 2011-05-27 at 08:19 -0700, JD wrote:
> Obviously you have not used at&t uverse service :)
No... Wrong country
> Without THEIR modem nothing works. Uverse is a
> package: TV, Internet, Phone services. Decryption
> of the TV signal occurs in the modem, and is then
> sent out the same cable
On 05/27/11 05:03, Tim wrote:
> If, and I mean if, being zapped was the cause, then that could well be
> the nature of the fault. Damage to components that allow a charge to
> build up that causes stuff ups.
>
> Faulty equipment can behave in weird ways. I've been servicing
> electronics equipmen
Tim:
>> Doesn't meant it hasn't been zapped from another route (static inside
>> the house, hotplugging equipment, poor anti-static precautions when the
>> unit was built), or has simply failed.
JD:
> But how can you explain that a power reset (without letting
> it cool down), makes all three mach
On 05/26/11 12:23, Rich wrote:
> On 5/26/2011 10:38 AM, JD wrote:
>> On 05/26/11 06:46, Rich wrote:
>>> Just a shot in the dark, but do you have multiple dhcp daemons running
>>> on the network. Your router probably has one running. I could buy that
>>> multiple dhcp daemons might cause something
On 5/26/2011 10:38 AM, JD wrote:
> On 05/26/11 06:46, Rich wrote:
>> Just a shot in the dark, but do you have multiple dhcp daemons running
>> on the network. Your router probably has one running. I could buy that
>> multiple dhcp daemons might cause something like what you describe.
>
> $ ps -e
On 05/26/11 07:18, Tim wrote:
> Tim:
>>> I've had two modem routers go bad, I suspect they've been zapped up
>>> the phone line during thunderstorms.
> JD:
>> This thing connects to the coax cable in the wall. The at&t
>> uverse system is on fiber-optic cable until it gets to the curb
>> by the dev
On 05/26/11 06:46, Rich wrote:
> Just a shot in the dark, but do you have multiple dhcp daemons running
> on the network. Your router probably has one running. I could buy that
> multiple dhcp daemons might cause something like what you describe.
$ ps -ef | grep dhcp
jd 12817 5530 0 07:3
Tim:
>> I've had two modem routers go bad, I suspect they've been zapped up
>> the phone line during thunderstorms.
JD:
> This thing connects to the coax cable in the wall. The at&t
> uverse system is on fiber-optic cable until it gets to the curb
> by the development. From there it is on buried c
Just a shot in the dark, but do you have multiple dhcp daemons running
on the network. Your router probably has one running. I could buy that
multiple dhcp daemons might cause something like what you describe.
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 9.0.901
On 05/25/11 21:09, Joe Zeff wrote:
> On 05/25/2011 08:37 PM, JD wrote:
>> I wish I could do that - but the owner is not I :)
> Understood. Please note that I didn't suggest drilling any holes or
> anything like that. My sister and I share a house; I'd like to do some
> drilling to shorten cable-r
On 05/25/2011 08:37 PM, JD wrote:
> I wish I could do that - but the owner is not I :)
Understood. Please note that I didn't suggest drilling any holes or
anything like that. My sister and I share a house; I'd like to do some
drilling to shorten cable-runs but the house is in her name and she
On 05/25/11 20:22, Joe Zeff wrote:
> On 05/25/2011 08:11 PM, JD wrote:
>> If our house were wired for cat5 or cat6 in every room,
>> I would agree. Since that is not the case, 2 machines have
>> to be wireless, except for win7, which is a desktop and on
>> that desk is the router.
> It's not exact
On 05/25/2011 08:11 PM, JD wrote:
> If our house were wired for cat5 or cat6 in every room,
> I would agree. Since that is not the case, 2 machines have
> to be wireless, except for win7, which is a desktop and on
> that desk is the router.
It's not exactly hard to run the cable along the walls,
On 05/25/11 18:46, Tim wrote:
> On Wed, 2011-05-25 at 13:50 -0700, JD wrote:
>> My only conclusion is that someone at at&t or
>> a nearby is/are hacking our router, or the router's
>> firmware is buggy.
>> But I have never seen a bug like this that waits
>> 20 to 30 minutes before striking :)
> Or
On Wed, 2011-05-25 at 13:50 -0700, JD wrote:
> My only conclusion is that someone at at&t or
> a nearby is/are hacking our router, or the router's
> firmware is buggy.
> But I have never seen a bug like this that waits
> 20 to 30 minutes before striking :)
Or it's failing... Does it, or its powe
On 05/24/11 22:07, Kevin J. Cummings wrote:
> Have you tried the ping tests after turning off your fedora firewall
> (iptables)? Are they any better or do they still fail?
> What about turning off your XP firewall, just to test the pinging?
>
I finally zeroed in on the culprit.
It is neither fedor
On 05/24/11 22:07, Kevin J. Cummings wrote:
>
> You didn't explicitly list them. Can I assume that they are:
>
> win7 192.168.1.1
> fedora192.168.1.2
> xp1 192.168.1.3
> router192.168.1.254
fedora 192.168.1.108
> ?
>
> Are these all DCHP assigned from the router? or static?
> I
On 05/24/2011 10:19 PM, JD wrote:
> On 05/24/11 18:45, Kevin J. Cummings wrote:
>> Does "xp1" have an IP address?
>>
>> If yes, does Fedora know about it?
> xp1 and win7 are both listed in /etc/hosts.
> So yes, they have IP addresses :) :)
You didn't explicitly list them. Can I assume that they
On 05/24/11 18:45, Kevin J. Cummings wrote:
> On 05/24/2011 06:57 PM, JD wrote:
>> I have been trying to mount on fedora a shared C drive
>> from a windows machine running winxp.
>>
>> Well, I used the mount command:
>>
>> # mount -t cifs //xp1/c -o
>> user=jd,password=mypassword,uid=myuid,gid=mygi
On 05/24/2011 06:57 PM, JD wrote:
> I have been trying to mount on fedora a shared C drive
> from a windows machine running winxp.
>
> Well, I used the mount command:
>
> # mount -t cifs //xp1/c -o
> user=jd,password=mypassword,uid=myuid,gid=mygid,rw /mnt/xp1/c
>
> Unable to find suitable addre
I have been trying to mount on fedora a shared C drive
from a windows machine running winxp.
Well, I used the mount command:
# mount -t cifs //xp1/c -o
user=jd,password=mypassword,uid=myuid,gid=mygid,rw /mnt/xp1/c
Unable to find suitable address.
I checked the firewall setting on the xp machi
22 matches
Mail list logo
