Reestablish Server Connection
in [Visual Basic]
|
Prev: The NNTP exodus continues.
Next: VB6 to Web
From: Helmut Meukel on 12 May 2010 03:33 David, this may be a long shot, but... Are you certain the server reboots? The scenario you describe reminds me of the terms most ISPs here in Germany offer for private Internet access. You pay a flat rate but they disconnect you every 24 hours for a few seconds. And after reconnection you have another IP address out of their pool. Helmut. "David" <NoWhere(a)earthlink.net> schrieb im Newsbeitrag news:uTiBUtV8KHA.1760(a)TK2MSFTNGP04.phx.gbl... > Mr Simpson: > > I tried puttiing KeepAliveTime in registry-- did Not work. > Went down today at the usual time. > > FWIW I have no access to the server. > All I'm doing is linking to a vendors server (as a client) and receiving data > via UDP. > > Re: My App (Client side). > Not sure what more I can do to redesign. > > Have the vendors ActiveX dll which contains only three events: > 1) data receive; > 2) timestamp; and > 3) error. > I've coded against all three. > > As previously stated error event does Not trigger when server stops sending > data (rebooted). > Only way to tell server went down is look at my Caption (where I display the > timestamp). > Every day at exactly 4:45:33 seconds my App stops receiving data -- timestamp > has stopped. > > Closing my App, and then restarting it (my App) > relinks to server and everything is OK for another 24 hours. >
From: David on 12 May 2010 10:52 Mr. Meukel: What you suggest was my initial take. Contacted my ISP prior to posting. They say they're not logging anyone off. However, could not get an answer as to whether their routers (or some router inbetween me and the server) see this 3 second drop and says "link dropped" so make bandwidth available for someone else. Also talked to the server vendor prior to posting. They confirm "3" second shutdown at the time indicated. Indicated I and few others are dropping but not others. Said it was the ISP. Don't put much "fact" in this statement as no checking on their end by the tech -- just a quick response = to "not me, the other guy". "Helmut Meukel" <NoSpam(a)NoProvider.de> wrote in message news:O98sqVa8KHA.5476(a)TK2MSFTNGP06.phx.gbl... > David, > > this may be a long shot, but... > Are you certain the server reboots? > The scenario you describe reminds me of the terms > most ISPs here in Germany offer for private Internet > access. You pay a flat rate but they disconnect you > every 24 hours for a few seconds. And after reconnection > you have another IP address out of their pool. > > Helmut. > > > > "David" <NoWhere(a)earthlink.net> schrieb im Newsbeitrag > news:uTiBUtV8KHA.1760(a)TK2MSFTNGP04.phx.gbl... >> Mr Simpson: >> >> I tried puttiing KeepAliveTime in registry-- did Not work. >> Went down today at the usual time. >> >> FWIW I have no access to the server. >> All I'm doing is linking to a vendors server (as a client) and receiving >> data via UDP. >> >> Re: My App (Client side). >> Not sure what more I can do to redesign. >> >> Have the vendors ActiveX dll which contains only three events: >> 1) data receive; >> 2) timestamp; and >> 3) error. >> I've coded against all three. >> >> As previously stated error event does Not trigger when server stops >> sending data (rebooted). >> Only way to tell server went down is look at my Caption (where I display >> the timestamp). >> Every day at exactly 4:45:33 seconds my App stops receiving data -- >> timestamp has stopped. >> >> Closing my App, and then restarting it (my App) >> relinks to server and everything is OK for another 24 hours. >> > >
From: David on 12 May 2010 10:53 Nobody: Thanks for input. David "Nobody" <nobody(a)nobody.com> wrote in message news:%23N1KLLY8KHA.1888(a)TK2MSFTNGP05.phx.gbl... > "David" <NoWhere(a)earthlink.net> wrote in message > news:uTiBUtV8KHA.1760(a)TK2MSFTNGP04.phx.gbl... >> Mr Simpson: >> >> I tried puttiing KeepAliveTime in registry-- did Not work. >> Went down today at the usual time. >> >> FWIW I have no access to the server. >> All I'm doing is linking to a vendors server (as a client) and receiving >> data via UDP. >> >> Re: My App (Client side). >> Not sure what more I can do to redesign. >> >> Have the vendors ActiveX dll which contains only three events: >> 1) data receive; >> 2) timestamp; and >> 3) error. >> I've coded against all three. >> >> As previously stated error event does Not trigger when server stops >> sending data (rebooted). >> Only way to tell server went down is look at my Caption (where I display >> the timestamp). >> Every day at exactly 4:45:33 seconds my App stops receiving data -- >> timestamp has stopped. >> >> Closing my App, and then restarting it (my App) >> relinks to server and everything is OK for another 24 hours. > > You can "reconnect" by releasing all references to any ActiveX DLL > object(Set obj = Nothing), which unloads the DLL, then use "Set" again(Set > obj = New Project1.Class1). Avoid declaring your variables "As New", like > "Dim o As New Class1", use "Set" to create an instance instead. > >
From: Nobody on 12 May 2010 12:11 "David" <NoWhere(a)earthlink.net> wrote in message news:OhlfPLe8KHA.2248(a)TK2MSFTNGP05.phx.gbl... > Mr. Meukel: > > What you suggest was my initial take. > Contacted my ISP prior to posting. > They say they're not logging anyone off. > However, could not get an answer as to whether their routers > (or some router inbetween me and the server) see this 3 second > drop and says "link dropped" so make bandwidth available for > someone else. > > Also talked to the server vendor prior to posting. > They confirm "3" second shutdown at the time indicated. > Indicated I and few others are dropping but not others. > Said it was the ISP. > Don't put much "fact" in this statement as no checking on their > end by the tech -- just a quick response = to "not me, the other guy". UDP is a connection-less protocol. It means that there is no connection to drop, but at the API level it's possible to call "connect" to listen and talk to a single IP. If there is a router at your end that is using NAT(to make several computers share the same IP) that has rebooted, then you need to send something to the server so your own router knows where the outgoing connection was originated from, so it knows how to forward packets back from the server. However, I can't explain how a router at your end would reboot at the same time you are seeing the outage when the server "reboots". In any event, you need to get a better picture about what's going on. One software that helps is Wireshark, which is free and open source. See what your software/DLL sends on start up, and what happens when there is an outage. http://en.wikipedia.org/wiki/Wireshark Tip on using Wireshark: If you applied some sort of filter, like using "Follow TCP Stream" or made your own and you want to go back to the full packet list, click "Clear" button next to the filter text, which is underneath the toolbar. Also, you may want to use TCPView, and right click your UDP connection and choose "Close Connection" to see how your application behaves if there was an Internet outage. Good luck!
From: David on 12 May 2010 12:20
Thanks for input. Have Wireshark, but never installed it. Looked like a steep learning curve. Maybe this will get me going with it. David "Nobody" <nobody(a)nobody.com> wrote in message news:uJ5mj3e8KHA.3840(a)TK2MSFTNGP02.phx.gbl... > "David" <NoWhere(a)earthlink.net> wrote in message > news:OhlfPLe8KHA.2248(a)TK2MSFTNGP05.phx.gbl... >> Mr. Meukel: >> >> What you suggest was my initial take. >> Contacted my ISP prior to posting. >> They say they're not logging anyone off. >> However, could not get an answer as to whether their routers >> (or some router inbetween me and the server) see this 3 second >> drop and says "link dropped" so make bandwidth available for >> someone else. >> >> Also talked to the server vendor prior to posting. >> They confirm "3" second shutdown at the time indicated. >> Indicated I and few others are dropping but not others. >> Said it was the ISP. >> Don't put much "fact" in this statement as no checking on their >> end by the tech -- just a quick response = to "not me, the other guy". > > UDP is a connection-less protocol. It means that there is no connection to > drop, but at the API level it's possible to call "connect" to listen and > talk to a single IP. > > If there is a router at your end that is using NAT(to make several > computers share the same IP) that has rebooted, then you need to send > something to the server so your own router knows where the outgoing > connection was originated from, so it knows how to forward packets back > from the server. However, I can't explain how a router at your end would > reboot at the same time you are seeing the outage when the server > "reboots". > > In any event, you need to get a better picture about what's going on. One > software that helps is Wireshark, which is free and open source. See what > your software/DLL sends on start up, and what happens when there is an > outage. > > http://en.wikipedia.org/wiki/Wireshark > > Tip on using Wireshark: If you applied some sort of filter, like using > "Follow TCP Stream" or made your own and you want to go back to the full > packet list, click "Clear" button next to the filter text, which is > underneath the toolbar. > > Also, you may want to use TCPView, and right click your UDP connection and > choose "Close Connection" to see how your application behaves if there was > an Internet outage. > > Good luck! > > |