Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Classic Database server (2009SP1) on Windows 2012 server
Newminds_Systems
Member Posts: 2
Hi all,
First of all, i like to say i like this forum alot. As a sys-admin for several Nav customers this forum helped me out alot of times.
Actually it helped me today, toward a solution at a customer and a colleague told me to add to this community, my efforts / solutions for today, so it might help others in the future.
Today we moved a Nav 2009 SP1 Classic Database server from a Windows 2008R2 server to a new Windows 2012R2 server.
All users are using database authentication, except for 2 NAS services, who use Windows Authentication.
After the migration to the new server, we moved all users without any trouble, however i couldn't get the NAS services up and running.
Giving the following error in Windows Application event log.
" Network path cannot be found. This message refers to the file .
The network server may be down or the path may be invalid "
I tried to authenticate using Windows authentication from a Classic Client (Gui) which failed as well, until i ran the client from the database server itself. There i was able to successfully connect. Eventually it make me disable the Windows firewall, and afterward i was able connect from other machines as well, using Windows Authentication, so technically... problem solved..
However as a sys-admin i prefer the firewall enabled. I found out that with Windows Authentication the client also creates a TCP port 445 connection.
445 TCP Microsoft-DS Active Directory, Windows shares
445 TCP Microsoft-DS SMB file sharing
If i would have enabled the role file services on the database server, the firewall rules would have been prolly altered.
I our case, i enabled the (default configured) firewall rule: File and Printer Sharing (SMB-In)
Now we are able to connect with Windows Authentication and have firewall enabled.
I hope this might help others as well in the future.
Regards,
Han
First of all, i like to say i like this forum alot. As a sys-admin for several Nav customers this forum helped me out alot of times.
Actually it helped me today, toward a solution at a customer and a colleague told me to add to this community, my efforts / solutions for today, so it might help others in the future.
Today we moved a Nav 2009 SP1 Classic Database server from a Windows 2008R2 server to a new Windows 2012R2 server.
All users are using database authentication, except for 2 NAS services, who use Windows Authentication.
After the migration to the new server, we moved all users without any trouble, however i couldn't get the NAS services up and running.
Giving the following error in Windows Application event log.
" Network path cannot be found. This message refers to the file .
The network server may be down or the path may be invalid "
I tried to authenticate using Windows authentication from a Classic Client (Gui) which failed as well, until i ran the client from the database server itself. There i was able to successfully connect. Eventually it make me disable the Windows firewall, and afterward i was able connect from other machines as well, using Windows Authentication, so technically... problem solved..
However as a sys-admin i prefer the firewall enabled. I found out that with Windows Authentication the client also creates a TCP port 445 connection.
445 TCP Microsoft-DS Active Directory, Windows shares
445 TCP Microsoft-DS SMB file sharing
If i would have enabled the role file services on the database server, the firewall rules would have been prolly altered.
I our case, i enabled the (default configured) firewall rule: File and Printer Sharing (SMB-In)
Now we are able to connect with Windows Authentication and have firewall enabled.
I hope this might help others as well in the future.
Regards,
Han
0