Re: redirection on network

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm using two different XP machines for my testing. Both work with both
CE4.2 and 5.0. Perhaps you don't have the NetBEUI protocol installed on
your XP box, but you do on Vista? In any case, if you have a single Vista
machine and a single XP machine and one works and the other does not, I'd
cross-compare the list of clients and protocols installed for their network
adapters. Something is missing...

Paul T.

"Boyd" <Boyd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7BF59A6-4480-44AF-B3B0-D3E0BC1204CC@xxxxxxxxxxxxxxxx
By Golly you are right.

I don't need the "\network" anymore.

At least to my vista machines :(


XP still not so happy.

"Paul G. Tobey [eMVP]" wrote:

Acting as a client, you should be able to type \\<servername>\<sharename>
or
just \\<servername> into the address bar in Windows CE Explorer and see
what's on the server. I've tested that on CE4.2 and CE5 this morning.
It
appears that \network\\<servername> works OK, too, at least for a couple
of
simple test cases in CE4.2, but not in CE5. Seems like \\<servername> is
easier anyway. Maybe you can live with that change?

*Everyone* owes Steve a beer!

Paul T.

"Boyd" <Boyd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AB9B2373-D6E2-477D-89FA-F9D302E7F7AA@xxxxxxxxxxxxxxxx

I have been confused by some of your coments.

So I did some digging, found a Steve Maillet ( I still owe him a beer)
article describing how 4.2 introduces the concpt of Windows CE acting
as
File
Server.

Neat.

My question on this thread though is using the CE device as a file
client
accessing an XP/2003Server file server, not the other way around.

And there, "\network" is definitely required to get to the file server.

/Boyd
"Paul G. Tobey [eMVP]" wrote:

Or, you can try \\<servername>\<sharename> in Explorer. If you have
suitable credentials, that will show the contents of the share.
\\<servername> also works in the same way. As far as I can tell,
though,
\network is not involved in these at all.

Paul T.

"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT
com> wrote in message news:%23WsfO$hKJHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
I think you've just been lucky finding that working that way or
something.
That's not the intended mode of operation, as far as I can tell. What
is
displayed for the Vista box when you do that for it? The list of
shared
folders? Or the contents of a share?

Maybe you have a share mapped from that servername called by that
name
in
the \network folder or something. That's what you'd get if you
mapped
a
share using a command something like this:

net use <servername> \\<servername>\<sharename>

You'd have a subfolder under \network, called <servername>, so
\network\\servername (although the second \ is not necessary), would
work.

Paul T.

"Boyd" <Boyd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3209AE13-953C-44ED-846B-F9E53B407C83@xxxxxxxxxxxxxxxx
Hi Paul,

On the Windows CE GUI display, click "My Computer" Icon, one of
the
option
icons presented is "network." When the Network icon is selected,
"\Network"
appears on the "Address" line. Fill in the reset with
"\Network\\servername"
and it "should" present a logon screen. After the logon screen, it
"should"
list the shared resources on the host machine.
And all that works fine if the "\\servername" is a Vista box. No
joy
if
it
is an XP box!
And this used to work to XP boxes in my 4.1 build but for other
reasons I
now must use 4.2.

Actually this procedure worked years ago also on my CE 3.0, 3.1,
3.2
images.

Another note: all machines ( Vista, XP, CE ) are on a DHCP network.

And the XP, Vista, W2K machines have no troubles connecting to
shared
resources amongst each other.

"Paul G. Tobey [eMVP]" wrote:

I don't recognize the URL \network\\servername, but I think that,
if
that
works, it's just luck. Are you sure you aren't trying to access
the
\network folder *on the Windows CE device* with that? Or is
"network"
just
a stand-in for your network name? You might try the following:

1. Set the name of the device on the Control Panel | System applet
|
Device
Name page to something unique on the network.

2. Reboot.

3. Actually create that share. In a MS-DOS window on the device,

net use * \\<servername>\sharename

This may pop up the username/password dialog. Fill that in, if
so.

Now, what's the state of the \network folder on the device? Has a
subfolder
called something like "<sharename> on <servername>"?

Paul T.

"Boyd" <Boyd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38BDD7CD-2D0D-47DE-AFF6-24410730DF49@xxxxxxxxxxxxxxxx
I have the strangest problem.

I have a Windows CE 4.2 nk.bin image built that I can use
\network\\servername where servername is a VISTA machine works
just
fine!!!

But if servername is an XP box, it doesn't work - can't find the
machine.

If it helps at all, it's a PB4.2 image using a Kontron MOPslcd6
BSP
applied!!

Long story short: I had previous built such an image using PB
4.1
that
worked just fine. But new BSP doesn't support 4.1, just 4.2 and
up.

I thought I had ported everything to the 4.2 build, but
something
seems to
be missing.

redir.dll and netbios.dll are in the image, so I don't know
where
else
to
look.

Regards,

Boyd













.

Relevant Pages

  • Vista to XP large file transfers over wireless fail consistently
    ... I am experiencing a wireless network compatibility issue between ... Windows Vista Ultimate and Windows XP Pro. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Moving Day for That Vista Machine
    ... Moving Day for That Vista Machine ... And as if PC moving day weren’t hard enough, most people now faced with this task have to migrate from an older version of Windows to the new Windows Vista, which typically stores user files in different folders from previous versions. ... The Windows Easy File Transfer program that comes with Vista can help migrate program settings while Laplink’s PCMover can migrate settings and try to move your software. ... One way to get files to the new machine is to connect the two machines by a wired or wireless local area network and use built-in Windows tools to copy files. ...
    (alt.sys.pc-clone.dell)
  • Moving Day for That Vista Machine
    ... Moving Day for That Vista Machine ... task have to migrate from an older version of Windows to the new Windows ... Vista can help migrate program settings while Laplink's PCMover can migrate ... wired or wireless local area network and use built-in Windows tools to copy ...
    (soc.retirement)
  • Re: getting into an apple os 10 workgroup with a vista 32-bit system
    ... but the apple computer will not show up on my network map. ... your friend will need to set up Windows networking on the Mac. ... must create matching user accounts/passwords on both the Mac and Vista. ... do not need to be logged into the same account on all machines and the ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: redirection on network
    ... article describing how 4.2 introduces the concpt of Windows CE acting as ... Maybe you have a share mapped from that servername called by that name ... When the Network icon is selected, ... And all that works fine if the "\\servername" is a Vista box. ...
    (microsoft.public.windowsce.embedded)