Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Here are some common networking issues that come up every now and then in XPe runtime. Most networking problems come up due to missing components in the runtime, so here are some quick tips and solutions that should help.
How to specify a static ip address in an embedded runtime
If you want to set up your runtime to have a static IP address, keep in mind that there is no facility for this in Target Designer. So the solution is to include a batch file or script to run during RunOnce, which occurs just prior to arriving at the desktop for the first time. You will need to add the following components to your configuration:
Network Command Shell
Network Command Shell Interface Context
IP Router Monitor Library
The batch file contents are as follows:
netsh interface ip set address name="Local Area Connection" source=static addr=[computerIP] [netmask] [defaultgateway] 1
netsh interface ip set dns name="Local Area Connection" static [DNSserver1] primary
netsh interface ip add dns name="Local Area Connection" [DNSserver2] index=2
netsh interface ip add dns name="Local Area Connection" [DNSserver3] index=3
How to enable the route argument in Netstat (netstat -r)
In order to get the route command to work in netstat, you must either add the component 'TCP/IP Utilities' to your configuration, or you can manually add route.exe to your runtime image from your file repository. Route.exe is required by netstat in order to display the route table.
How to get NetBIOS working in the runtime
If you require NetBIOS functionality in your runtime, include both of the following components:
NetBIOS Driver
PNP (User-Mode)
How to use all of net shell's functions
Net Shell (netsh) has some undeclared dependencies. To gain all the functionality of netsh, include the following components in your runtime:
Network Command Shell
Network Command Shell Interface Context
IP Router Monitor Library
How to connect to a network share using 'net use'
If you attempt to connect to a network share using 'net use' in a runtime, you may get the error message 'System error 126 has occurred.' For example:
net use f: \\server\share
To resolve this issue, add the 'Network Command Shell Interface Context' component to your runtime.
[edit 4/26 - fixed component names]
- Matt
Comments
- Anonymous
April 26, 2005
The comment has been removed - Anonymous
April 26, 2005
The comment has been removed