Steven, although it may sound highly unlikely would it be possible to test this case on your device running the lastet OS build? Just want to cover all the bases before digging in.
This is still a problem with the latest OS and 126.96.36.199.
Thank you for the update Steven... helpdesk ticket 2689276 was created. Teir 2 support will try to replicate the issue and get to us.
Steven, would it be possible to test this issue against updated Fusion drivers, release 25.
The handheld with MC9190-G30SWEQA6WR model and Wireless Fusion 3.00.2.0.025R failed.
The handheld with MC9190-GA0SWEQA6WR model and Wireless Fusion 3.00.2.0.019R failed.
This time I looked into IIS log file and particularly focus on these fields: cs-method, cs-uri-stem, cs-uri-query, s-port, cs-username, sc-status, sc-substatus and sc-win32-status.
For details, please go to this link,
Here is a sample log,
Line # cs-method cs-uri-stem cs-uri-query s-port cs-username sc-status sc-substatus sc-win32-status 1 GET auth.htm - 80 - 401 2 2148074254 2 GET auth.htm - 80 QA\johndoe 200 0 0 3 GET auth1.htm - 80 QA\johndoe 200 0 0 4 GET auth.htm - 80 QA\johndoe 200 0 0 5 GET auth1.htm - 80 QA\johndoe 200 0 0 6 GET auth.htm - 80 QA\johndoe 200 0 0 7 GET auth1.htm a=1 80 - 401 1 2148074248 8 GET auth1.htm a=1 80 - 401 1 2148074248 9 GET auth1.htm a=1 80 - 401 1 2148074248
How to read the above lines:
- Line 1, access the auth.htm file
- Line 2, enter user name and password credentials
- Line 3, clicks Go button without query string on auth.htm page
- Line 4, clicks Back button on auth1.htm page
- Line 5, clicks Go button without query string on auth.htm page
- Line 6, clicks Back button on auth1.htm page
- Line 7, clicks Go button with query string as 'a=1'
- Line 8, enter user name (johndoe) and password credentials
- Line 9, enter user name (johndoe) and password credentials
Now focus on lines 7, 8 and 9. The cs-username became '-' which means it uses anonymous mode even I entered credentials at line 8 and 9. And the status codes are different from the line 1.
1 of 1 people found this helpful
New information on the LDAP issue. We only see it when working with Windows 2003 server. Once we configured the outside server access for you, we could not get our hand held to work, so we used the ActiveDirectory from Windows 2008 Server. This does not have the problem encountered. We do not have an external facing Windows 2003 ActiveDirectory server. I think if you try the older Windows 2003 Server, you will likely duplicate the problem.