Re: networking problem

• Previous message: Karoly Vaczko (FM): "networking problem"
• In reply to: Karoly Vaczko (FM): "networking problem"
• Next in thread: Karoly Vaczko (FM): "Re: networking problem"
• Reply: Karoly Vaczko (FM): "Re: networking problem"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 28 Dec 2004 22:45:27 +0100

Karoly,

Does this help?
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/msg/552f346383b56dcb

Regards,
Slobodan

"Karoly Vaczko (FM)" <karoly.vaczko@freemail.hu> wrote in message news:%23a9FeOS7EHA.1564@TK2MSFTNGP09.phx.gbl...
> Hello,
>
> I'm facing with a new problem now...
>
> Configuration: my hardware and a shell prototype that I created in
> component designer (it is actually a cmd.exe componentized, nothing
> more). including components: network command shell, network command
> shell interface. Then running auto-resolve created an image that was
> able to boot.
>
> FBAlog.txt shows the following interesting:
>
> 19:47:53 PM - [FBALaunch] D:\WINDOWS\system32\snetcfg.exe -l
> D:\WINDOWS\inf\ndisuio.inf -c p -i MS_NDISUIO (ExitCode: 0x8007000d)
> 19:47:53 PM - [FBALaunch] D:\WINDOWS\system32\snetcfg.exe -l
> D:\WINDOWS\inf\netwzc.inf -c s -i MS_WZCSVC (ExitCode: 0x8007000d)
> 19:48:09 PM - [FBARegQueue: DllRegisterServer]
> D:\WINDOWS\System32\activeds.dll (Error: 0x80040154)
> 19:48:10 PM - [FBARegQueue: DllInstall]
> D:\WINDOWS\System32\userenv.dll (Error: 0x80040154)
>
> After booting into the shell, I managed to start netsh, here is the
> screen capture:
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> D:\WINDOWS\System32>netsh
>
> WARNING: Could not obtain host information from machine:
> [OEM-OGQRQ6TRR00]. Some
> commands may not be available.
> Class not registered
>
> netsh>interface ip
> netsh interface ip>show config
> The request is not supported.
>
>
> netsh interface ip>show ipaddress
>
> The Routing and Remote Access Service is not currently running on the
> local mach
> ine.
> Please use 'net start remoteaccess' on the machine to start the service.
>
> netsh interface ip>show dns
> The request is not supported.
>
> netsh interface ip>add address "Local Area Connection" 192.168.2.155
> 255.255.255
> .0
>
> Invalid interface Local Area Connection specified.
>
> netsh interface ip>dump
>
>
> # ----------------------------------
> # Interface IP Configuration
> # ----------------------------------
> pushd interface ip
>
>
>
> popd
> # End of interface IP configuration
>
>
> netsh interface ip>reset d:\resetlog.txt
>
> netsh interface ip>show ipaddress
>
> The Routing and Remote Access Service is not currently running on the
> local mach
> ine.
> Please use 'net start remoteaccess' on the machine to start the service.
>
> netsh interface ip>exit
>
>
> D:\WINDOWS\System32>net start remoteaccess
> The service name is invalid.
>
> More help is available by typing NET HELPMSG 2185.
>
>
> D:\WINDOWS\System32>
>
>
>
> resetlog.txt:
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\1\RegLocation
> old REG_MULTI_SZ =
>
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpSubnetMaskOpt
> SYSTEM\CurrentControlSet\Services\?\Parameters\Tcpip\DhcpSubnetMaskOpt
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\3\RegLocation
> old REG_MULTI_SZ =
>
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDefaultGateway
> SYSTEM\CurrentControlSet\Services\?\Parameters\Tcpip\DhcpDefaultGateway
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\6\RegLocation
> old REG_MULTI_SZ =
>
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpNameServer
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DhcpNameServer
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation
> old REG_MULTI_SZ =
>
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDomain
> SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\44\RegLocation
> old REG_MULTI_SZ =
>
> SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\Tcpip_?\DhcpNameServerList
> SYSTEM\CurrentControlSet\Services\NetBT\Adapters\?\DhcpNameServer
>
> reset
> SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\46\RegLocation
> old REG_SZ =
> SYSTEM\CurrentControlSet\Services\NetBT\Parameters\DhcpNodeType
>
> added SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\ServiceDll
> added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DatabasePath
> added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ForwardBroadcasts
> added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IpEnableRouter
> added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\NameServer
> added
> SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Winsock\UseDelayedAcceptance
> Failed to load network configuration from the registry. (hr=0x8007000d)
> <completed>
>
>
>
>
> What do I miss from the configuration so that the ethernet interface
> could be initilaized and the computer will be then "pingable"?
>
> Thanks for your help in advance. I apologize for the long post.
>
> Regards,
>
>
> Karoly

• Previous message: Karoly Vaczko (FM): "networking problem"
• In reply to: Karoly Vaczko (FM): "networking problem"
• Next in thread: Karoly Vaczko (FM): "Re: networking problem"
• Reply: Karoly Vaczko (FM): "Re: networking problem"
• Messages sorted by: [ date ] [ thread ]