cfisher440
Well-known member
- Joined
- Oct 11, 2005
- Messages
- 73
- Programming Experience
- 1-3
Hello everyone,
I have program that I support that somebody else programmed a while back that is no longer with my company. Basically it is a timeclock program. It runs just fine all the time (a bit slow actually) so I never have to worry about going into the code. The database and "vbTimeListener" for it runs within our facility (on the LAN) on one of our servers along with our personal network drives.. Unfortunately, our server group failed over that server to one in another state. Now the program runs extremely slow, yet I can still access people's personal network drives just fine (little bit of lag time, but not very noticeable).
The program is local to the client's PC. When they open the program and clock there is a lot of verification going on, but for the most part it is basically going to the database and updating it.
What could make the program run very very slow, but the network drives not?
I would just say it's because the server failed over and it will be back in a few days.
I looked at the code and it seems to be listening on port 13 of the server. I'm not sure why they selected port 13 when they built this program, but I was thinking that may having something to do with it.
Any questions/comments/ideas are appreciated.... Thanks!
I have program that I support that somebody else programmed a while back that is no longer with my company. Basically it is a timeclock program. It runs just fine all the time (a bit slow actually) so I never have to worry about going into the code. The database and "vbTimeListener" for it runs within our facility (on the LAN) on one of our servers along with our personal network drives.. Unfortunately, our server group failed over that server to one in another state. Now the program runs extremely slow, yet I can still access people's personal network drives just fine (little bit of lag time, but not very noticeable).
The program is local to the client's PC. When they open the program and clock there is a lot of verification going on, but for the most part it is basically going to the database and updating it.
What could make the program run very very slow, but the network drives not?
I would just say it's because the server failed over and it will be back in a few days.
I looked at the code and it seems to be listening on port 13 of the server. I'm not sure why they selected port 13 when they built this program, but I was thinking that may having something to do with it.
Any questions/comments/ideas are appreciated.... Thanks!