-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos F Lange wrote:
> I solved the problem with brute force (see my other e-mail today), but I
> wanted to reply here to see if learn some more.
>
> On Tue June 5 2007 14:11, G T Smith wrote:
>> Carlos F Lange wrote:
>>> On Tue June 5 2007 09:37, G
I solved the problem with brute force (see my other e-mail today), but I wanted
to reply here to see if learn some more.
On Tue June 5 2007 14:11, G T Smith wrote:
> Carlos F Lange wrote:
> > On Tue June 5 2007 09:37, G T Smith wrote:
>
>
>
> >> A very faint possibility is that there
> >> may be
On Tuesday 05 June 2007, Carlos F Lange wrote:
> On Tue June 5 2007 12:06, BandiPat wrote:
> > I'm going to ask a silly question and make a silly suggestion. When
> > you say you booted into Windows then booted into Linux later, did you
> > shutdown the machine first or just reboot it selecting Li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Tuesday 2007-06-05 at 11:49 -0600, Carlos F Lange wrote:
> > A very faint possibility is that there
> > may be an issue with connection negotiation (Duplex, 10/100 mbps
> > etc).
>
> Would there be any log for this negotiation?
No, but there a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos F Lange wrote:
> On Tue June 5 2007 09:37, G T Smith wrote:
>
>> A very faint possibility is that there
>> may be an issue with connection negotiation (Duplex, 10/100 mbps
>> etc).
>
> Would there be any log for this negotiation?
>
What
On Tue June 5 2007 12:06, BandiPat wrote:
> I'm going to ask a silly question and make a silly suggestion. When
> you say you booted into Windows then booted into Linux later, did you
> shutdown the machine first or just reboot it selecting Linux?
>
> Next, if you did the above, try shutting down
On Tuesday 05 June 2007, Carlos F Lange wrote:
[...]
>
> > >> b) Which NIC?
> > >
> > > nVidia Corporation MCP51 Ethernet Controller
> >
> > Is this the same NIC as on your other machines. If you think is so
> > check chipset on card... NIC card manufacturers have a nasty habit
> > of revising the
On Tue June 5 2007 09:37, G T Smith wrote:
> >> a) Does the NIC communicate with a static IP address from SuSE?
> >
> > No. Even an attempt to ping the router (192.168.2.1) gives error:
> > "Connect: Network is unreachable."
> > "rcnetwork status" gives "eth0 dhcpd is still waiting for data."
>
On Tue June 5 2007 07:33, Rainer Brinkmann wrote:
> Perhaps the cable dropped down.
No cable problem. That is exactly what is killing me. The lights on the
router are on (also when I changed ports and cable) and when I reboot
into Windows the DHCP servers hands out the usual IP address
immediat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos F Lange wrote:
> On Tue June 5 2007 01:40, G T Smith wrote:
>> Carlos F Lange wrote:
>>> I reconfigured the card a few times and rebooted the router. I
>>> disabled the MAC address control on the router and the other
>>> machines are fine, all a
On Tue June 5 2007 01:40, G T Smith wrote:
> Carlos F Lange wrote:
> > One of my desktop machines is dual-boot and lived happily attached
> > to my SMC router, which has a built in DHCP server. After a change
> > of network card the DHCP server saw and assigned an address to it,
> > as usual. After
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos F Lange wrote:
> One of my desktop machines is dual-boot and lived happily attached to my
> SMC router, which has a built in DHCP server. After a change of network
> card the DHCP server saw and assigned an address to it, as usual. After
> bo
One of my desktop machines is dual-boot and lived happily attached to my
SMC router, which has a built in DHCP server. After a change of network
card the DHCP server saw and assigned an address to it, as usual. After
booting into Windows (network working again fine) I went back to Suse
10.1 but
13 matches
Mail list logo
