networking in XPe

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

Is the .NET component required to browse to an XPe computer. I've got
one which doesn't have the .NET component. From that PC, I can browse
to other XP machines. I've enabled sharing and the guest account. Are
there other changes required?

Rob
 
Rob,

The .Net Framework component itself does not have anything to do wit hthe computer browsing.

You are probably looking for "Netserv Inf" component.

KM
 
Is the netserv.inf something that I need to include when I build the
image? Under the Network properties the File sharing service is listed
and active.

Rob
 
Rob,
Is the netserv.inf something that I need to include when I build the
image?

Desirable. But still can be added (with all dependencies) at run time.
Under the Network properties the File sharing service is listed
and active.

Could you give us more info about the problem you are trying to fix within your image?
 
How can I add the netserv.inf at run time?

I'm trying to pull data files from the XPe machine across the network
however for some reason I can't get access to the XPe files. I've
enabled the guest account, enabled file sharing of the drive as read
only and all the other things that is usually required however it still
doesn't work. Whenever I try to browse to the XPe machine I get error
message

Logon failure: the user has not been granted the requested logon type
at this computer

Any info would help.
 
Hi Rob,

You have "File Sharing" component in your image right?
This component should include component "netserv inf". Check in windows\inf folder if you have netserv.inf file.

When you share your volume in XPe how do you do that from command line or from shell?

Give us exact steps.

Regards,
Slobodan
PS: Can you access volumes on XPP from XPe?
 
Rob,

Please follow Slobodan's post and give us more info about what's included in your image.
Also, please try "net use \\<your xpe device\sharename> .. /USER: password" command from another machine (not just browsing).
 
I've got the netserv.inf in the windows\inf folder

I shared the C drive using windows explorer at first. From a command
prompt net view \\xpe device shows the C drive as shared. If I add a
sharename using the net share command it completes successfully and
appears in the net view command however the results are the same. From
an XPP computer I cannot get any access to the XPe device. It does
appear when I do a NET VIEW command. However when I do a NET VIEW \\XPe
device I get an "System error 5 has occured" message.

I'm not positive about the details of the image right now. It was
actually created by advantech. I've working with them to try to resolve
this but its taken forever. Is there something specific I need to tell
them to include in the image to resolve this?

ROb
 
Hi Rob,

Error that you mention is Access Denied:
5 Access is denied. ERROR_ACCESS_DENIED


My question are:
Is this winlogon/minlogon based image?

Do you have named user account with valid password that you can reference from network (XPP)?

Regards,
Slobodan
 
Slobodan,

There is a named user account however I can't access it from the XPP
machines on the network. From the XPe machine I can browse to other
machines on the network. This in a winlogon image I think but how can I
check?

Thanks

Rob
 
Rob,
There is a named user account however I can't access it from the XPP

machines on the network. From the XPe machine I can browse to other
machines on the network. This in a winlogon image I think but how can I
check?

Check winlogon.exe file under \windows\system32 directory. The file size will be >~ 500kb for Winlogon and much less for MinLogon.
 
KM

The winlogon is 490KB. I've tried the net use command without any
difference.

I think I'm getting closer to my problem. I noticed that the "Named
Service Provider" field is empty under the "Client for MS Networks"
entry in the netwrok configuration properties dialog box. I found an
entry on MSDN that imples the image was built with out the RPC named
service component present

http://support.microsoft.com/default.aspx?scid=kb;en-us;883104

When I change the entry to "Windows Locator" I have to reboot and upon
rebooting the selection is blank again.

I'm working with Advantech to fix this but is there a way that you know
of that I can check to see if the RPC service is present. In the FBAlog
file there is an entry that shows rpcrt4.dll is registered.

Rob
 
Rob,
The winlogon is 490KB.

Yup. That is WinLogon. And that is a good sign as you will definitely be able to fix the problem then.
I've tried the net use command without any difference.
I think I'm getting closer to my problem. I noticed that the "Named
Service Provider" field is empty under the "Client for MS Networks"
entry in the netwrok configuration properties dialog box. I found an
entry on MSDN that imples the image was built with out the RPC named
service component present

http://support.microsoft.com/default.aspx?scid=kb;en-us;883104

When I change the entry to "Windows Locator" I have to reboot and upon
rebooting the selection is blank again.

Great finding and interesting article. I don't want to speculate on it until you give it a try but I am thinking the Locator is not
the cause for the issue.
But who knows for sure untill it's tested :-)

Before you reboot (btw, make sure you are not running enabled EWF!) make sure the [HKLM\SOFTWARE\Microsoft\Rpc\NameService] exists
and "Endpoint" value there set to "\pipe\locator".
I'm working with Advantech to fix this but is there a way that you know

In case it is getting to long to get this fixed through manufacturer, you can always build your own image and replace the current
image on the device.
At least you can do that for testing purposes.
All you need to do is:
- Get XPE ToolKit (Eval would work)
- Run TAP on the device under current image and import and process PMQ
- Create a Winlogon image based on the platform macro component you get on the previous step
- Include whatever components you would like to add (RPC Name Service, etc.)
- Change the Windows directory in the Configuration Trget Device Setting to something like \Windows2, also change all other
directories there to something unique (e.g., Document annd Setting2, etc.)
- Build the image
- Copy the image (everything except files under root) over network (for example) to the device storage media (I am assuming
you've got there enough space to fit both images)
- Change boot.ini to switch to boot from \Windows2 ARC path
- Reboot and watch the FBA process. Test, analyze and debug the image as you'd want to

Since you know that XPe runs on the device already, it may take just a couple of hours for you to build a new image.
of that I can check to see if the RPC service is present. In the FBAlog
file there is an entry that shows rpcrt4.dll is registered.

For the RPC just check the registry under [HKLM\Software\Microsoft\Rpc] to see what's registred.
And certainly check if the RPC services are started.
The rpcrt4.dll belongs to "RPC Local Support" which is likely is in your image.
 
Back
Top