Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 266 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Navision Slows down on Server
Christian_Buehl
Member Posts: 145
This weekend we did a big restructuration of our Network. We replaced the former NT Domain by OpenLDAP.
Everything seems to work fine, except Navision. Swiching from one company to another takes now up to 30 seconds, other actions slow down too.
It's weird, as this happens only on a W2K-Server which was quite fast before. A secondary workstation -with a testsystem on it- works as fast as usual.
Additionally I can't connect to the server by using the management console, while the client still works without problems.
I think there is something wrong with the netbios name resolution (which shouldn't be, as we use TCP/IP as protocol). :?
Does anyone know a reason for this or a solution ?
Thanks in advance.
Everything seems to work fine, except Navision. Swiching from one company to another takes now up to 30 seconds, other actions slow down too.
It's weird, as this happens only on a W2K-Server which was quite fast before. A secondary workstation -with a testsystem on it- works as fast as usual.
Additionally I can't connect to the server by using the management console, while the client still works without problems.
I think there is something wrong with the netbios name resolution (which shouldn't be, as we use TCP/IP as protocol). :?
Does anyone know a reason for this or a solution ?
Thanks in advance.
0
Comments