rise level and adprep vs mapping shares and printers by IP

last weekend we executed a domain rise level to Windows 2003 native and adprep for the forest, domain and gpprep.  All logs without problems.  But... today all users in the domain are reporting that when they are logged on Windows 7 and Windows server 2008 equipments, if the user tries to map a network share or a printer (both in the same domain) by IP  (\\\share1), they are prompted for credentials, they give the user and password, and they get the error code 0x80070043 - the network name cannot be found.  However, if they execute the same test on the same machine but specifying the name of the server(\\server1\share1), they map the share and /or printer without been requeste for a user and password and without any problem.  On other hand, if a the same user logs to a Windows server 2003, they can map the shares and printers by name and by IP without problems and without prompting for user and password.  Notes: there are the ptr records in the DNS, it is not the problem.  Dcdiag and repadmin and logs look ok.  Logs from rise level and adprep: all ok without errors.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Neadom TuckerCommented:
The objects may have had some minor changes.   Have you tried to recreate the shares and see if that makes any difference?  I have not done a 2000 to 2003 update in so long I cannot remember all the issues that would normally come about.
Will SzymkowskiSenior Solution ArchitectCommented:
Raising the Functional Level should not create an issues on the end user with logins etc. The functional level only affects domain controllers and the features they can use based on the functional level they are at.

If your DC's are replicating correctly and there are no errors in the logs then this might be related to something else.

finally we found the cause of the problems...  Some days ago it was a applied the critical security patch KB3002657, so when the reboot of the domain controller for the rise level, the patch was also applied and it couses all the crazy validations behavior.  Now it is a new version of the patch for servers with operating system Windows server 2003.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
te first answer helped to look for the root cause on other way.  The root cause was the patch that was activated after the reboot of the rise level.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.