Universal can't connect to Windows Server 2003 - solved

[Ischovits]

Hello!

I have a Universal in german from T-Mobile Austria and a BlueAngel also from T-Mobile Austria. As we all know the Universal has the new OS Windows Mobile 5.0, the BlueAngel has Windows Mobile 2003.

So and there is a BIG difference between these two OS (OR A BIG BUG, I don't know).

The problem is: With the file-explorer (or Total Commander 2.0, which i prefer) you can connect with WLAN to a share on a computer. Enter the UNC-path under path in the file-explorer, the device asks for a login and it works. So it is unter Windows Mobile 2003 with the BlueAngel. And it doesn't matter to which computer I will connect: to my server with Windows Server 2003 or to my workstation with Windows XP. I enter my domain account and it works.

On the Universal it doesn't work when I will connect to my server with Windows Server 2003. It's absolutely impossible to connect to a share on my server. BUT I CAN connect to a share an my workstation with Windows XP WITH MY DOMAIN ACCOUNT. So what I see in the moment: The NTLM-authentication works because I can connect to any Windows XP with a domain account, but the connection to a share on a server with Windows Server 2003 fails. And this only with the Universal, because in the same time with my BlueAngel it works.

My question is: Has somebody the same ugly problem or maybe I do somethimg wrong, I don't know.

And that's the reason why I can't change my device in this moment and why I love my BlueAngel.

Best regards, Peter

[Carnivor]

i to have this issue, i can map to xp shares no probs but win2003server shares just loops on the password screen.

big issue for me this

[Dubrand]

w2k3 issues
I had the same issues on w2k3-server before installing the latest updates.
After new W2K3 installation and newest updates: no problems.
The problem could be active directory.

Have a look to "NetBIOS over IP" at IP-settings. Resco Explorer can't map UNCs, only NetBIOS-names, it's my monitoring.

Greetings, Gerd Dubrand

[Carnivor]

that dosent fix the problem, just tried it, it worked fine on my BA but not on JJ.

[eagle 1]

I also cannot connect to my Win2003 server via jasjar, but I can connect to my win2000 advanced server. Win2003 server is sbs2003 with all updates applied. Can connect to both via my pda2k. Interesting?

[tintoy]

IS the server a DC? you may need to disable the 'Microsoft network server: Digitally sign communications (always)' setting the default DC GPO - http://support.microsoft.com/kb/823659. This is enabled by default for DC's and acan cuase issues when talking to downlevel clients (I've had this problem with samba clients.

It mayalso be set in the local secuirty policy.

But then again this might not be anything to do with it...

Anything in the logs on the server?

[Ischovits]

Thank you for your samba server and your idea, tintoy. Your hint works!

For all others aigan the solution:

On a Windows Server 2003 domain controller you have to disable 'Microsoft network server: Digitally sign communications (always)'. I haven't this done by Active Directory, i have this done by 'Security settings for domain controller' -> 'Security Options' in 'Management'.

Note: Please excuse when I don't have used the correct names, because I have only a german version of the Windows Server 2003 and I don't know the exact names of the program groups of the english version. But I hope you know, what I mean.

Thank you aigan tintoy, this problem is solved!

See you all again here,
Peter

[Carnivor]

I confirm this,

network server: Digitally sign communications (always)

change to disabled in the Default Domain Controller Security Settings.

This has just made my day. odd how wm5 is apparently newer but dosent quite work out the box like wm2003 did

[tintoy]

np ;-)

[gio-ita]

Someone can write a detailed description ? I have the same problem.

Thanks