Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 296 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Time-out
Stefan.Norbart
Member Posts: 3
Hi there,
We recently had a technical upgrade to NAV2009 SP1 of our old 2.5 database. We did this because we switched to Windows 7 and the old Navision client (3.70B) does not run under W7. At first we had some small issues with our firewall (Fortigate). If traffic over TCP/IP-port 2407 isn't active for 300 seconds then the port is closed by the firewall. This was a known problem and is fixed by setting the time-out to 43200 seconds (12 hours).
I hoped the issues were solved but we still have issues with a time-out. It seems that after a few hours (2 or 3) an inactive Navision session is closed. We get error message "The TCP/IP-network send error code 10051". Our Navision partner says it's a DNS problem and our ICT-vendor thinks it's a wrong setting in Navision. Did anybody had a similar problem or does someone know a solution for this issues?
Thanks,
Stefan Norbart
We recently had a technical upgrade to NAV2009 SP1 of our old 2.5 database. We did this because we switched to Windows 7 and the old Navision client (3.70B) does not run under W7. At first we had some small issues with our firewall (Fortigate). If traffic over TCP/IP-port 2407 isn't active for 300 seconds then the port is closed by the firewall. This was a known problem and is fixed by setting the time-out to 43200 seconds (12 hours).
I hoped the issues were solved but we still have issues with a time-out. It seems that after a few hours (2 or 3) an inactive Navision session is closed. We get error message "The TCP/IP-network send error code 10051". Our Navision partner says it's a DNS problem and our ICT-vendor thinks it's a wrong setting in Navision. Did anybody had a similar problem or does someone know a solution for this issues?
Thanks,
Stefan Norbart
0
Comments
Is it really a problem that someone who hasn't used the application in three hours is logged off? I mean it's better for security, for opening up sessions (if you have too many users), etc.
My Blog - nav.education
Thanks for your reaction. It's not a major issue but some reports are being processed by night. When the report is processed and after that the time-out kicks in the user cannot see the results. A work-around for this is to process the report during day-time.
Our Navision partner had a new idea which is being tested at this moment. The problem can be caused by a setting in the Terminal Server config. There's a time-out configured which is also used by Navision. Let's wait and see.