[EMAIL PROTECTED] wrote:
>>Any other users who run into this problem on similar
>>hardware might want
>>to try using a non-nForce NIC.
>>
>
> Did you have the firewall software turned on??
Nope.
> I have nForce NICs on several Opteron and Athlon64s
> with no problems after disabling the nVidia f
Kern Sibbald wrote:
On Saturday 23 July 2005 22:22, Phil Stracchino wrote:
Kern Sibbald wrote:
You might make sure you have the latest drivers/firmware for the ethernet
card in your Windows system that is giving you problems. At least one
user recently found that this was the cause of his di
> Any other users who run into this problem on similar
> hardware might want
> to try using a non-nForce NIC.
>
Did you have the firewall software turned on??
I have nForce NICs on several Opteron and Athlon64s
with no problems after disabling the nVidia firewall
which was preventing me from con
Yes, the network adapter is part of the nforce2 chipset, not an external
realtek chip or something, though I seem to remember it being autodetected
as a realtek at one time. I'm certain though, that when I ran linux on this
machine a while back it used the nforce kernel driver.
Thanks,
Chris
>
Chris Lee wrote:
> I have a win32 machine whose motherboard (nforce2) has onboard 10/100
> ethernet. I'll try to test this in the near future, but currently I'm using
> a 3com card in that machine.
The key factor is, is it an *nVidia* onboard 10/100?
--
Phil Stracchino [EMAIL PROTECTED]
I have a win32 machine whose motherboard (nforce2) has onboard 10/100
ethernet. I'll try to test this in the near future, but currently I'm using
a 3com card in that machine.
Thanks,
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Kern
On Saturday 23 July 2005 22:22, Phil Stracchino wrote:
> Kern Sibbald wrote:
> > You might make sure you have the latest drivers/firmware for the ethernet
> > card in your Windows system that is giving you problems. At least one
> > user recently found that this was the cause of his disconnects wi
Kern Sibbald wrote:
> You might make sure you have the latest drivers/firmware for the ethernet
> card
> in your Windows system that is giving you problems. At least one user
> recently found that this was the cause of his disconnects with a Windows
> machine -- he had a NVidia ethernet card.
On Saturday 23 July 2005 20:50, Phil Stracchino wrote:
> OK, I have the beginnings of a clue here. First of all, when I
> restarted bacula with debugging enabled (at -d200) on the sd, the sd
> reported 3 jobs on the volume and 1 on the catalog, and errored out the
> tape. I loaded a fresh tape, r
On Saturday 23 July 2005 20:17, Phil Stracchino wrote:
> Kern Sibbald wrote:
> > There is something going wrong in the network connection between the FD
> > and the SD. The first thing is to always (at first) believe the error
> > message, which says that the SD has closed the connection. Perhaps
I've found and solved the problem. That machine has two NICs, both
gigabit; one is an nVidia gigabit NIC built into its nForce4 chipset,
the other a Marvell Yukon 88E8053 PCI-E gigabit NIC built onto the
motherboard. I switched ther machine's network connection to the
Marvell Yukon, and the backu
Kern Sibbald wrote:
> There is something going wrong in the network connection between the FD and
> the SD. The first thing is to always (at first) believe the error message,
> which says that the SD has closed the connection. Perhaps turning on debug
> in the SD would give you a better idea w
On Saturday 23 July 2005 18:33, Phil Stracchino wrote:
> I've just updated all the existing clients I currently have running from
> v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
> current win32 clients, both of which are new client installs, one
> because it's a new client,
On Saturday 23 July 2005 17:51, Misty Stanley-Jones wrote:
> I have a volume that is no longer listed in the database because I changed
> the volume naming scheme. I bsanned it in, but when I try to use
> 'bextract' I get the following error:
>
> 23-Jul 10:47 bextract: bextract Error: Win32 GZIP d
Phil Stracchino wrote:
> I've just updated all the existing clients I currently have running from
> v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
> current win32 clients, both of which are new client installs, one
> because it's a new client, one because it was recently rei
I've just updated all the existing clients I currently have running from
v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
current win32 clients, both of which are new client installs, one
because it's a new client, one because it was recently reinstalled after
Windows shot its
I have a volume that is no longer listed in the database because I changed the
volume naming scheme. I bsanned it in, but when I try to use 'bextract' I
get the following error:
23-Jul 10:47 bextract: bextract Error: Win32 GZIP data stream not supported on
this Client.
23-Jul 10:48 bextract: E
17 matches
Mail list logo
