Boot Up Error with Dhcp.exe

[James Tabor]

Hi all!

WARNING:  WSHGetSockaddrType at drivers/net/wshtcpip/wshtcpip.c:103 is UNIMPLEME
NTED!
Unhandled exception
ExceptionCode:    c0000005
Faulting Address:        0
Address:          7c92659d   C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c92659d
DS 23 ES 23 FS 3b GS 0
EAX: 00000000   EBX: 00000022   ECX: ffffffff
EDX: 7ffe0304   EBP: 0066fe18   ESI: 00841c98   ESP: 0066fdc8
EDI: 00000000   EFLAGS: 00010246
Frames:
      400000+1bbf       C:\ReactOS\system32\dhcp.exe
      400000+2282       C:\ReactOS\system32\dhcp.exe
      400000+2a95       C:\ReactOS\system32\dhcp.exe
      400000+11e7       C:\ReactOS\system32\dhcp.exe
      400000+1258       C:\ReactOS\system32\dhcp.exe
    7c800000+31285      C:\ReactOS\system32\KERNEL32.dll

Thanks,
James

[James Tabor]

James Tabor wrote:
> Hi all!
>
> WARNING:  WSHGetSockaddrType at drivers/net/wshtcpip/wshtcpip.c:103 is 
> UNIMPLEME
> NTED!
> Unhandled exception
> ExceptionCode:    c0000005
> Faulting Address:        0
> Address:          7c92659d   C:\ReactOS\system32\ntdll.dll
> CS:EIP 1b:7c92659d
> DS 23 ES 23 FS 3b GS 0
> EAX: 00000000   EBX: 00000022   ECX: ffffffff
> EDX: 7ffe0304   EBP: 0066fe18   ESI: 00841c98   ESP: 0066fdc8
> EDI: 00000000   EFLAGS: 00010246
> Frames:
>      400000+1bbf       C:\ReactOS\system32\dhcp.exe
>      400000+2282       C:\ReactOS\system32\dhcp.exe
>      400000+2a95       C:\ReactOS\system32\dhcp.exe
>      400000+11e7       C:\ReactOS\system32\dhcp.exe
>      400000+1258       C:\ReactOS\system32\dhcp.exe
>    7c800000+31285      C:\ReactOS\system32\KERNEL32.dll
>
> Thanks,
> James

Oh he!
Revision: 18617

[James Tabor]

Hi,
Funning thing, I was just testing and typed dhcp at the cmd console.
Wow! It worked! It doesn't work when booting up. I guess due to the boot
sequence. One more note, from the cmd line, it does not find the dns address.
Is there a cmd line entry I need to init the name server address?

So, Does dhcp run before the net driver is installed?

Thanks,
James

From ipconfig /all

ReactOS IP Configuration

HostName. . . . . . . . . . . : COMPUTERNAME
    DomainName. . . . . . . . . . :
    DNS Servers . . . . . . . . . : 0.0.0.0
    NodeType. . . . . . . . . . . : 8 (Hybrid)
    ScopeId . . . . . . . . . . . :
    EnableRouting . . . . . . . . : no
    EnableProxy . . . . . . . . . : no
    EnableDns . . . . . . . . . . : no

GetNumberOfInterfaces() returned 2
GetInterfaceInfo() returned with 1 adaptor entries
[1] NE2000 Compatible

Adaptor Information

Ethernet Adapter NE2000 Compatible:

Description. . . . . . :
    Physical Address . . . : 00-40-05-E1-35-76
    DHCP Enabled . . . . . : No
    IP Address . . . . . . : 10.65.145.101
    Subnet Mask. . . . . . : 255.255.255.0
    Default Gateway. . . . :

[art yerkes]

On Sat, 22 Oct 2005 23:17:43 +0000
James Tabor [e-mail] wrote:
> Hi,
> Funning thing, I was just testing and typed dhcp at the cmd console.
> Wow! It worked! It doesn't work when booting up. I guess due to the boot
> sequence. One more note, from the cmd line, it does not find the dns address.
> Is there a cmd line entry I need to init the name server address?
>
> So, Does dhcp run before the net driver is installed?
>
> Thanks,
> James
>
> From ipconfig /all
>
> ReactOS IP Configuration
>
> HostName. . . . . . . . . . . : COMPUTERNAME
>    DomainName. . . . . . . . . . :
>    DNS Servers . . . . . . . . . : 0.0.0.0
>    NodeType. . . . . . . . . . . : 8 (Hybrid)
>    ScopeId . . . . . . . . . . . :
>    EnableRouting . . . . . . . . : no
>    EnableProxy . . . . . . . . . : no
>    EnableDns . . . . . . . . . . : no
>
> GetNumberOfInterfaces() returned 2
> GetInterfaceInfo() returned with 1 adaptor entries
> [1] NE2000 Compatible
>
> Adaptor Information
>
> Ethernet Adapter NE2000 Compatible:
>
> Description. . . . . . :
>    Physical Address . . . : 00-40-05-E1-35-76
>    DHCP Enabled . . . . . : No
>    IP Address . . . . . . : 10.65.145.101
>    Subnet Mask. . . . . . : 255.255.255.0
>    Default Gateway. . . . :
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

dhcp should wait for new adapters to arrive and set their addresses.
I didn't know how to do it (and we couldn't have new adapters at the
time anyhow), so it just checks once at startup.  It isn't acutally
that hard to add adapters if we know how to receive the right
message.

There shouldn't be any difference between dhcp after startup and at
startup with respect to dns server address.  It's likely a bug.

dhcp is supposed to be a real service, but I don't think we had 
support for that at the time.  It's not difficult to transition it
if reactos is ready.
-- 
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman