| | |
Network Adapter Disconnections due to terminal services
![]() |
•
•
Join Date: Jun 2007
Posts: 3
Reputation:
Solved Threads: 0
[FONT='Times New Roman','serif']Our main server is running Windows 2000 adv server and basically running as a local file server, terminal server and application server.
[FONT='Times New Roman','serif']We have two other company branches in other parts of the country connecting via VPN (terminal services)to our main server using an accounting package developed for our needs.
[FONT='Times New Roman','serif']
[FONT='Times New Roman','serif']The main server has two network cards on the same network. This makes it appear that there are two servers on the network with the same name. This is NOT correct. It was done to address the speed problem with terminal server sessions. It appears to work most of the time. When the routing gets "confused" the terminal server sessions will come to a grinding halt that will need the servers to be restarted to rectify the problems.
[FONT='Times New Roman','serif']This issue is the main contributor to errors being logged by the servers in their respective event viewers informing us about one network adapter that keeps disconnecting and then reconnecting.
[FONT='Times New Roman','serif']We are running accounting applications and when this happens the program crashes.
[FONT='Times New Roman','serif']
[FONT='Times New Roman','serif']Is there a way to streamline this process and keep the network adapter from disconnections?
[FONT='Times New Roman','serif']We have two other company branches in other parts of the country connecting via VPN (terminal services)to our main server using an accounting package developed for our needs.
[FONT='Times New Roman','serif']
[FONT='Times New Roman','serif']The main server has two network cards on the same network. This makes it appear that there are two servers on the network with the same name. This is NOT correct. It was done to address the speed problem with terminal server sessions. It appears to work most of the time. When the routing gets "confused" the terminal server sessions will come to a grinding halt that will need the servers to be restarted to rectify the problems.
[FONT='Times New Roman','serif']This issue is the main contributor to errors being logged by the servers in their respective event viewers informing us about one network adapter that keeps disconnecting and then reconnecting.
[FONT='Times New Roman','serif']We are running accounting applications and when this happens the program crashes.
[FONT='Times New Roman','serif']
[FONT='Times New Roman','serif']Is there a way to streamline this process and keep the network adapter from disconnections?
![]() |
Similar Threads
- Can't detect Network adapter settings (Windows NT / 2000 / XP)
- Logging on through Terminal Services (Windows NT / 2000 / XP)
- Disonnect remote users via Script on Terminal Services (Windows NT / 2000 / XP)
Other Threads in the Networking Hardware Configuration Forum
- Previous Thread: server setup
- Next Thread: Website with Cisco tutorial videos and white papers
| Thread Tools | Search this Thread |
802.11 802.11n bluetooth british broadband browserproblems bt connectionproblem connectivity cpu data desktop dual gigabyte hardware infrastructure internet memory network networking news program rdimm reliability riched20.dll routers server storage survey technology telecoms troubleshoot uk upgrade videoconferencing view virgin wireless wirelessnetworking





