Problems DHCP server

Thanks for submitting this report.

Could you please provide some information about your ethernet card? The command "sudo lshw -C net" provides all the information needed. Please upload or paste the result here.

Thanks

Hello,

Here's the result:

laacque@laacque-desktop:~$ sudo lshw -C net
[sudo] password for laacque:
  *-network
       description: Ethernet interface
       product: VT6102 [Rhine-II]
       vendor: VIA Technologies, Inc.
       physical id: 12
       bus info: pci@0000:00:12.0
       logical name: eth0
       version: 74
       serial: 00:11:2f:41:a8:d1
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full latency=32 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s

Thanks,

Akke

> From: <email address hidden>
> To: <email address hidden>
> Date: Sat, 17 Nov 2007 15:27:28 +0000
> Subject: [Bug 163290] Re: Problems DHCP server
>
> Thanks for submitting this report.
>
> Could you please provide some information about your ethernet card? The
> command "sudo lshw -C net" provides all the information needed. Please
> upload or paste the result here.
>
> Thanks
>
>
> ** Changed in: ubuntu
> Assignee: (unassigned) => Ralph Janke (txwikinger)
> Status: New => Incomplete
>
> --
> Problems DHCP server
> https://bugs.launchpad.net/bugs/163290
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Nooit meer offline met Windows Live Messenger op je mobiele telefoon
http://www.getlivemobile.nl/

Thanks for the information.

Do you have any error messages that are shown about this in "/var/log/messages" ?

Could this be the same as Bug #159980 ?

Thanks

Hi there,

Well, I checked on the bug you mentioned and I m not really sure whether it's the same. The only thing that is sure is that I ve been using Ubuntu for quite some time and it used to connect nicely to the internet.
Here's my /var/log/messages.
It looks like Chinese to someone like me..... Hope your Chinese is fine..

Nov 18 14:36:37 laacque-desktop syslogd 1.4.1#21ubuntu3: restart.
Nov 18 14:43:00 laacque-desktop exiting on signal 15
Nov 18 19:07:39 laacque-desktop syslogd 1.4.1#21ubuntu3: restart.
Nov 18 19:07:39 laacque-desktop kernel: Inspecting /boot/System.map-2.6.22-14-generic
Nov 18 19:07:39 laacque-desktop kernel: Loaded 25445 symbols from /boot/System.map-2.6.22-14-generic.
Nov 18 19:07:39 laacque-desktop kernel: Symbols match kernel version 2.6.22.
Nov 18 19:07:39 laacque-desktop kernel: No module symbols loaded - kernel modules not enabled.
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] Linux version 2.6.22-14-generic (buildd@palmer) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 (Ubuntu 2.6.22-14.46-generic)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-provided physical RAM map:
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000001fffc000 (usable)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 000000001fffc000 - 000000001ffff000 (ACPI data)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] 0MB HIGHMEM available.
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] 511MB LOWMEM available.
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] Zone PFN ranges:
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] DMA 0 -> 4096
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] Normal 4096 -> 131068
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] HighMem 131068 -> 131068
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] early_node_map[1] active PFN ranges
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] 0: 0 -> 131068
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] DMI 2.3 present.
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] ACPI: RSDP signature @ 0xC00F5E20 checksum 0
Nov 18 19:07:39 laacque-desktop kernel: [ 0.000000] ACPI: RSDP 000F5E20, 0014 (r0 ASUS )
Nov 18 19:07:39 laacque-desktop kernel: [ ...

It shows no DHCP packets that it has received.

This is quite difficult to troubleshoot and I have been told similar stories before. Previously it sometimes worked when the network cable has been exchanged or just turned around (the plug on the network card into the network device and vice-versa.

Maybe this helps in this case too.

Well, someone in the Dutch Ubuntuforum wrote a script for me.
Unfortunately my English is too lousy to translate it. But there should be some guys on the forum who's English is better than mine.

It seems it's not an Ubuntu problem but a Windowsproblem. Windows simply refuses to release the network.
Here's the Dutch solution.
I ll send a translation as soon as I have it.

U kunt dit handmatig oplossen door het IP-adres onder Windows vrij te
geven, alvorens u de PC herstart.

      * Handmatige methode

Open hiervoor in Windows XP een DOS-venstertje:

Start - Programma's - Bureau-accessoires - Opdrachtprompt

tik in:

ipconfig /release

En druk op Enter.

Om deze handmatige oplossing te automatiseren heeft u twee opties:

      * Via een snelkoppeling (halfautomatische oplossing). Open
        Kladblok (notepad): Start - Programma's - Bureau-accessoires -
        Kladblok.

Tik in kladblok het volgende in:

ipconfig /release

Sla dit op als vrijgave.bat

Maak een snelkoppeling op uw bureaublad, die naar vrijgave.bat verwijst.
U kunt voortaan telkens even hierop dubbelklikken, voordat u Windows
afsluit.
----------------------------------------
> From: <email address hidden>
> To: <email address hidden>
> Date: Wed, 12 Dec 2007 13:43:11 +0000
> Subject: [Bug 163290] Re: Problems DHCP server
>
> It shows no DHCP packets that it has received.
>
> This is quite difficult to troubleshoot and I have been told similar
> stories before. Previously it sometimes worked when the network cable
> has been exchanged or just turned around (the plug on the network card
> into the network device and vice-versa.
>
> Maybe this helps in this case too.
>
> --
> Problems DHCP server
> https://bugs.launchpad.net/bugs/163290
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Bekijk Yes-R's real life soap op MSN Video!
http://video.msn.com/video.aspx?mkt=nl-nl&tab=m1192527562294&vid=8aff5b76-b78d-4b55-8b64-ef7e1d73aab2&playlist=videoByUuids:uuids:50b732c2-c105-41e9-adf0-36bd627d4eaa,0813da8c-031b-423f-a79d-35d925aee805,5cce447e-948d-43af-9862-45bb6bb9d6d8,6a39138c-f562-4254-be70-9d93343650f8,f9b8d78f-05a4-4c74-8e4b-28d20a4037ab&from=NLNL_Yes-R

Summarizing the dutch instructions:

the problem can be solved by manually releasing the DHCP lease in windows with ipconfig /release. The rest explains how to write a batch file and create a shortcut on the desktop that can be doubleclicked to do the release instead of using the command prompt.

I will close this report since it does not seem to be an ubuntu problem. Please reopen it if you can give us the information that shows a problem on ubuntu, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!