Just seen this question today.

I have in th SBS as the user opening the file the same user I used in the
Login Screen opened by Resco Explorer.

Helio

------
Helio Diamant
MS-MVP/Mobile Devices
Editor - PocketPCFreak.com



"Dan H" <someone@nospam.com> wrote in message
news:u1zEIUg0IHA.524@TK2MSFTNGP05.phx.gbl...
> Let me ask you this...on the SBS how is it showing you accessing the
> shares? ie. In open files what username is it saying is accessing the
> files?
> Ours shows guest.
>
> "Helio Diamant - MS-MVP/Mobile Devices" <helio@nospam.pocketpcfreak.com>
> wrote in message news:urWOeQe0IHA.2292@TK2MSFTNGP03.phx.gbl...
>> Strange, it is working for me flawlessly. I can search the network,
>> choose the SBS server, and go into any share that I want.
>>
>> --
>> ----
>> Helio Diamant
>> MS-MVP/Mobile Devices
>> Editor - PocketPCFreak.com
>>
>>
>>
>> "Dan H" <someone@nospam.com> wrote in message
>> news:OP%23JCEU0IHA.3920@TK2MSFTNGP02.phx.gbl...
>>> Hi Helio,
>>> Thanks for your response.
>>> We initially tried Rescoe explorer (was suggested on an HP site) and it
>>> did not work.
>>> My only concern with our "fix" is that is actually merely an exploit of
>>> a security hole. This is no good for many reasons. Reason #1 it could
>>> be "fixed" in a Windows update.
>>> Thanks again for your input.
>>>
>>> "Helio Diamant - MS-MVP/Mobile Devices" <helio@nospam.pocketpcfreak.com>
>>> wrote in message news:uH$4u4T0IHA.4492@TK2MSFTNGP02.phx.gbl...
>>>> Dan,
>>>>
>>>> I have been doing some tests here since your first post, and I have
>>>> found an easy way to avoid all problems on this issue. The name of the
>>>> solution is Resco Explorer and it can be found at www.resco.net .
>>>> Believe me, the LAN functionality connects easily also to SBS, and
>>>> together with the registry editor and the FTP client it is well worth
>>>> the 29.95 they are asking for it.
>>>>
>>>> --
>>>> ----
>>>> Helio Diamant
>>>> MS-MVP/Mobile Devices
>>>> Editor - PocketPCFreak.com
>>>>
>>>>
>>>>
>>>> "Dan H" <nospam@email.com> wrote in message
>>>> news:eldkYPpwIHA.2068@TK2MSFTNGP05.phx.gbl...
>>>>> Hi I posted this in SBS NG and it was suggested I post here:
>>>>>
>>>>> We are using an IPAQ running Windows Mobile 6. We want to access
>>>>> shares on
>>>>> the network.
>>>>> We can access shares on a Windows XP Pro machine no problem but when
>>>>> on the
>>>>> same network trying to access a share on a Windows 2003 SBS the login
>>>>> fails
>>>>> and a messge box prompting for a username and password continues to
>>>>> pop up
>>>>> (because of the failed access).
>>>>> The event viewer on the server though shows a successful login.
>>>>> The user is administrator and has full control on the shares. We
>>>>> verified
>>>>> it is not a firewall issue. We verified it is not a WAP issue.
>>>>> We actually took the ipaq to another network to see if it could access
>>>>> folders and the same issue occurs and it seems to be only with the
>>>>> Windows
>>>>> 2003 SBS (it works on Windows 2000 server).
>>>>>
>>>>> We took a Dell handheld running Mobile PC 2003 and were able to access
>>>>> the shares using a username and password to the share on the SBS
>>>>> server. We had no problems accessing the folder with the Mobile
>>>>> running the PC 2003.
>>>>>
>>>>> =============
>>>>> The above was our initial post after the above post we tried other
>>>>> things while waiting for a response and this is what happened:
>>>>>
>>>>> since the post we have been trying various
>>>>> different things and can access the folder but we are really not
>>>>> comfortable
>>>>> with how it is accessing the folder (I will explain) so I don't really
>>>>> consider it a resolution. As suggested I will post to the other group
>>>>> as
>>>>> well. Thanks for
>>>>>
>>>>> the link.
>>>>>
>>>>> While waiting for a post response I continued trying to access the
>>>>> server
>>>>> and did get into
>>>>>
>>>>> the share we need to.
>>>>>
>>>>> What I did was provided the netbios servername\username in the message
>>>>> box
>>>>> that prompted for
>>>>>
>>>>> the usernaame and password. It appeared the sername was case
>>>>> sensitive as
>>>>> we tried multiple
>>>>>
>>>>> times.
>>>>> On the 2003 server there is an account called testaccount. servername
>>>>> is
>>>>> Testserver.local.
>>>>> so in the IPAQ i open \\testserver\testfolder. it prompts for a
>>>>> unsername
>>>>> password and
>>>>>
>>>>> domain.
>>>>> If i put in testserver\testaccount as username it denies access,
>>>>> HOWEVEr if
>>>>> I put in
>>>>>
>>>>> Testserver\testaccount (notice the capital T in testserver) it lets me
>>>>> in.
>>>>> When i initially got in though i didn't see any files in the folder.
>>>>> Server
>>>>> Manager on the
>>>>>
>>>>> SBS showed a user Guest as being connected.
>>>>> So i enabled guest and gave the Guest account full control to the
>>>>> folder and
>>>>> now I can see
>>>>>
>>>>> all of the files and folders in the share.
>>>>> So it looks like the server thinks it is the account GUEST.
>>>>> Now we tried this over and over, and could only get in when the T in
>>>>> testserver was capital.
>>>>> To take it further we provide credentials Testserver (no username just
>>>>> the
>>>>> netbios name of
>>>>>
>>>>> the sbs server we are trying to get into, there is no user account
>>>>> called
>>>>> testserver) and no
>>>>>
>>>>> password and it lets us in the share (still showing it as connecting
>>>>> as
>>>>> GUEST).
>>>>>
>>>>> So we can get it to work consistently but obviously this is not right.
>>>>>
>>>>> Here is where it gets even more tricky.
>>>>>
>>>>> WE needed to get this thing live in the actual work environment so we
>>>>> planned on enabling
>>>>>
>>>>> guest account on the server and doing the same thing by providing
>>>>> netbios
>>>>> name of the new
>>>>>
>>>>> server we were connecting to.
>>>>>
>>>>> So I went over the new location, enabled the guest account entered the
>>>>> UNC
>>>>> for the new
>>>>>
>>>>> server (\\newserver\newfolder) and it let me right. It did not prompt
>>>>> me
>>>>> for any username
>>>>>
>>>>> or password. It sees the user as Guest but the last credentials I
>>>>> supplied
>>>>> from the IPAQ
>>>>>
>>>>> were from the test environment (Testserver).
>>>>>
>>>>> Any ideas on what is going on because we are stumped?
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>