Re: networking problem

From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 12/30/04 

Date: Thu, 30 Dec 2004 12:24:25 +0100

Karoly,

Thanks for info, I'm sure that it will help someone in the future :-)

Regards,
Slobodan

"Karoly Vaczko (FM)" <karoly.vaczko@freemail.hu> wrote in message news:ux6%234Bm7EHA.2700@TK2MSFTNGP14.phx.gbl...
> Slobodan,
>
> It did help. Thanks a lot. The problem was that I installed netsh and
> netsh extensions hoping that it will depend on the core networking
> components. Well, it didn't. I put together a howto about that, it was
> tested under XPe SP1. Here it goes:
>
>
>
> Static IP address configuration in Windows XPe environment HOWTO
>
>
> To be able to be pingable with one ethernet card in your target machine,
> you have to add the followings in TD:
>
> -driver of your ethernet card
> -Software : System : Networking & Communications; Basic TCP/IP
> Networking macro
> -Software : System : Networking & Communications : Applications;
> Network Command Shell
> -Software : System : Networking & Communications : Applications; Network
> Command Shell Interface Context
> -Software : System : Networking & Communications : Applications; IP
> Router Monitor Library
> -Software : System : Networking & Communications : Applications; TCP/IP
> Utilities
> -Software : System : System Services : Base; CMD - Windows Command Processor
>
>
> Let's make a dependency check, FBA your image and boot. Run CMD.exe.
>
> Enter ipconfig and press enter
>
> For the two possible scenarios here are the screen outputs of ipconfig:
>
> 1) your network card is NOT installed properly
>
> D:\WINDOWS\system32>ipconfig
>
> Windows IP Configuration
>
>
> D:\WINDOWS\system32>
>
> 2) your network adapter IS installed properly (it will be smilar, but
> not exactly the same ID {C675....blabla} - it is OK like that)
>
> D:\WINDOWS\system32>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter {C6757181-2472-44F4-BB41-926220B75EDA}:
>
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 0.0.0.0
> Subnet Mask . . . . . . . . . . . : 0.0.0.0
> Default Gateway . . . . . . . . . :
>
> D:\WINDOWS\system32>
>
>
> The above section tells you that you have a loaded network driver. If
> there is no section like Ethernet adapter or so in the ipconfig output,
> it is most probably a wrongly installed network driver that you should
> resolve first.
>
> Now, you should be patient here. If you do the following steps quickly
> (as I did for the first three-four times) you might receive errors. Wait
> about one minute before continue. The reason is most probably that XPe
> comes with DHCP client and it is trying to get an IP address from a DHCP
> server - the timeout should be about one minute.
>
> In the meantime, if you do ipconfig for a couple of times, the output
> should be altered once and becomes similar to this:
>
> D:\WINDOWS\system32>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter {C6757181-2472-44F4-BB41-926220B75EDA}:
>
> Connection-specific DNS Suffix . :
> Autoconfiguration IP Address. . . : 169.254.73.29
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
>
> D:\WINDOWS\system32>
>
> You should notice here that the IP address and the subnet mask has been
> changed by XPe, and also the _name_ of IP address line has changed from
> 'IP Address' to 'Autoconfiguration IP Address'. Once you notice that
> there is an Autoconfiguration IP Address line in your configuration, you
> must continue with this command:
>
> rundll32 netshell.dll HrRenameConnection
>
> The output of this command should be the prompt. I was not able to get
> any other command line outputs (except when I made a typo in the
> rundll32 or netshell.dll). If you make a typo in HrRenameConnection, you
> are going to receive a messagebox on the GUI (!!!) that something is
> going wrong.
>
> The result of the above command should be seen immediately with ipconfig
> again, it produces something like this:
>
> D:\WINDOWS\system32>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Autoconfiguration IP Address. . . : 169.254.73.29
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
>
> D:\WINDOWS\system32>
>
>
> Notice that you finally have a name of your connection, so that you are
> now able to manage your ethernet card in netsh. If you are using other
> language than English, "Local Area Connection" will appear in your local
> language (for instance, my connection is named as "Helyi kapcsolat").
>
> To set up a static IP address and mask, do this:
>
> netsh interface ip set address name="Local Area Connection"
> source=static addr=192.168.2.102 mask=255.255.255.0
>
> To set up a gateway:
>
> netsh interface ip set address name="Local Area Connection"
> gateway=192.168.2.1 gwmetric=0
>
> To set up a primary DNS:
>
> netsh interface ip set dns name="Local Area Connection" source=static
> addr=145.236.227.108 register=PRIMARY
>
> To set up a secondary DNS:
>
> netsh interface ip add dns name="Local Area Connection"
> addr=145.236.88.66 index=2
>
>
> TRICK: if you don't want to take your time with the syntax of netsh, set
> up all ip address and related parameters of the target machine on your
> _development_ machine through the friendly XP user interface. Then go to
> cmd and enter the following line:
>
> netsh interface ip dump >c:\ipparams.txt
>
> This creates a file at c:\ named ipparams.txt that will contain the
> network configuration that you would like to deploy on the target machine.
>
> To implement this file on your target machine, simply copy the file
> there, and do this command at the command line:
>
> netsh <c:\ipparams.txt
>
> The ipparams.txt file can be edited with a simple text editor, so
> replacing a DNS or changing the IP address would not be a big deal then.
>
> After all, do an ipconfig /all command and it will result this:
>
> D:\WINDOWS\system32>ipconfig /all
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : OEM-SREVWEVPFUT
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet
> Physical Address. . . . . . . . . : 00-11-85-DB-ED-8E
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.102
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 145.236.227.108
> 145.236.88.66
>
> D:\WINDOWS\system32>
>
>
>
> IMPORTANT! If you change from DHCP to static IP addressing or vica
> versa, the 'netsh interface ip set address' command may take a while (I
> measured 20 seconds once!). DON'T PANIC!
>
>
>
> I hope that the above could help to easily set up your static IP in XPe
> (also I hope it works for others as well not just me only! :-) ).
> Comments/corrections/updates are welcome.
>
> Thank you guys again for the support.
>
> Regards,
>
>
> Karoly
>
> Slobodan Brcin (eMVP) írta:
> > 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
> >
> >
> >
>
>
>

Relevant Pages

  • Re: Alternet Configuration broken after sleep
    ... location so we have configured the "Atlernate configuration" with the network ... This configuration works well for switching ... The problem happens when there is no ethernet cable attached. ... I am unable to remote the bad routes with the route ...
    (microsoft.public.windowsxp.network_web)
  • Re: "eth0: unknown interface" with newly-compiled kernel
    ... to do anything ethernet. ... The new kernel comes up ok otherwise. ... started with the default configuration and didn't remove anything ... /var/log/messages doesn't say anything about a network interface. ...
    (comp.os.linux.networking)
  • Re: xircom_cb missing (Fedora Core 2.4.22-1.2115nptl)
    ... >>I can use help connecting to the network after installation. ... >>ethernet after booting. ... > This normal for the default configuration which attempts to start the ... > network service before the pcmcia service. ...
    (comp.os.linux.setup)
  • Re: Remote Access and Outlook Web Access on SBS 2003
    ... that's how the *Wizard* configured your network. ... NETWORKING CONFIGURATION SUMMARY ... Restrict default Web site of IIS to only respond to ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Access and Outlook Web Access on SBS 2003
    ... SUMMARY OF SETTINGS FOR CONFIGURE E-MAIL AND INTERNET ... Internet Connection Wizard. ... network, firewall, secure Web site, and e-mail. ... NETWORKING CONFIGURATION SUMMARY ...
    (microsoft.public.windows.server.sbs)