Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Network\s+reliability\s*$/: 16 ]

Total 16 documents matching your query.

1. [WriteLog] Network reliability (score: 1)
Author: "Bob Henderson" <bob@5b4agn.net>
Date: Mon, 5 Nov 2007 18:10:53 -0000
In recent years I've used WL MS and M2 but have been troubled by periodic network failure and half hearted recovery. Having never been able to nail down the cause, I have assumed the culprit to be RF
/archives//html/WriteLog/2007-11/msg00012.html (7,749 bytes)

2. Re: [WriteLog] Network reliability (score: 1)
Author: mikebfischer@comcast.net
Date: Mon, 05 Nov 2007 18:42:40 +0000
Hi Bob, Thanks for asking that question. I thought we were just network inept. HAS anyone been able to kep this from happening? Thanks! Mike K7XH / K7IR ______________________________________________
/archives//html/WriteLog/2007-11/msg00013.html (8,697 bytes)

3. Re: [WriteLog] Network reliability (score: 1)
Author: "Don Cassel" <ve3xd@rogers.com>
Date: Mon, 5 Nov 2007 13:43:41 -0500
I have had WL fail the network even when there is no contesting going on. Usually during hours of sleep in the middle of a contest. It happened during SS CW this weekend and I suspect it occurred whe
/archives//html/WriteLog/2007-11/msg00014.html (8,964 bytes)

4. Re: [WriteLog] Network reliability (score: 1)
Author: "Richard L. King" <k5na@ecpi.com>
Date: Mon, 05 Nov 2007 20:27:53 +0000
At K5NA multi-op efforts we have suffered with this also. We typically run 4 or 5 computers in the network that is also connected by telnet to a in-house DX Cluster network. This year we stopped usin
/archives//html/WriteLog/2007-11/msg00015.html (9,888 bytes)

5. Re: [WriteLog] Network reliability (score: 1)
Author: "Irwin Darack" <irwindarack@comcast.net>
Date: Mon, 5 Nov 2007 16:49:59 -0500
Rich, We had the same problem at our VE2DXY (zone 2 Canada). This was a Multi-Two station with two computers networked together. When we used the Band Map feature, after a while it would cause Writel
/archives//html/WriteLog/2007-11/msg00016.html (11,646 bytes)

6. Re: [WriteLog] Network reliability (score: 1)
Author: "K7ZO (Scott Tuthill)" <k7zo@cableone.net>
Date: Mon, 5 Nov 2007 18:26:24 -0700
Have used WL for years at NK7U in MS, MM, M2 environments with high levels of RF, up to 5 PC's online at the same time. Never had any problems I would call "networking" problems. Had something that l
/archives//html/WriteLog/2007-11/msg00018.html (9,871 bytes)

7. Re: [WriteLog] Network reliability (score: 1)
Author: "Charles Morrison" <cfmorris@bellsouth.net>
Date: Tue, 6 Nov 2007 08:42:32 -0600
I'll second Scott's observations. I've found it to be fairly reliable, however it could have been for several things that I did inadvertently and didn't think twice about. 1. Never use TCP/IP networ
/archives//html/WriteLog/2007-11/msg00021.html (12,673 bytes)

8. Re: [WriteLog] Network reliability (score: 1)
Author: "Hal Kennedy" <halken@comcast.net>
Date: Tue, 6 Nov 2007 12:03:51 -0500
Charlie, KI5XPs email is right on the money. We used to consistently run 48 hours without problems at K4JA, usually with five or six computers in the network. The link was NET-DDE not TCP/IP. All the
/archives//html/WriteLog/2007-11/msg00024.html (9,309 bytes)

9. Re: [WriteLog] Network reliability (score: 1)
Author: "Irwin Darack" <irwindarack@comcast.net>
Date: Tue, 6 Nov 2007 12:49:02 -0500
I would like to explore this further. We ran two computers in a Multi-Two station. One was a wired (Ethernet) connection into a D'Link router and the other we ran wireless. The only time our computer
/archives//html/WriteLog/2007-11/msg00026.html (10,766 bytes)

10. Re: [WriteLog] Network reliability (score: 1)
Author: "Bob Henderson" <bob@5b4agn.net>
Date: Tue, 6 Nov 2007 17:54:55 -0000
My sincere thanks Hal, Charlie and others for detailed and thoughtful responses. The significant input I've had from other folks with WL network issues suggests the guidance you have provided may be
/archives//html/WriteLog/2007-11/msg00027.html (7,926 bytes)

11. Re: [WriteLog] Network reliability (score: 1)
Author: "Gerald Wilson" <gtwilson@integrity.com>
Date: Wed, 7 Nov 2007 06:22:17 -0000
Hi Scott K7ZO, I am glad to hear about the success you have had networking WriteLog at NK7U. The "network reliability" and "networking" threads have received much play on this reflector over the past
/archives//html/WriteLog/2007-11/msg00033.html (13,112 bytes)

12. [WriteLog] Network reliability (score: 1)
Author: "James M. Galm, W8WTS" <jim@w8wts.com>
Date: Thu, 8 Nov 2007 18:26:02 -0500
I'm afraid that I don't have a magic recipe that guarantees perfect WL networking, but I've always had complete success with WL networks, both large and small. Perhaps being an engineer causes me to
/archives//html/WriteLog/2007-11/msg00058.html (10,933 bytes)

13. Re: [WriteLog] Network reliability (score: 1)
Author: "ve3cwj" <ve3cwj@gmail.com>
Date: Sun, 11 Nov 2007 11:45:38 -0500
I see our favorite topic of networking WL is still running... A few years back, I implored WL to implement TCP/IP instead of just NetDDE. They did, but problems have always cropped up. Yes, WL seems
/archives//html/WriteLog/2007-11/msg00094.html (10,574 bytes)

14. Re: [WriteLog] Network reliability (score: 1)
Author: "Kostas SV1DPI" <sv1dpi@otenet.gr>
Date: Sun, 11 Nov 2007 19:15:41 +0200
I have not a lot of experience in networking but the last time i tried via a wireless network to connect 2 writelog computer i stayed connected only when i wrote in start>run ping -t ip.address That
/archives//html/WriteLog/2007-11/msg00095.html (11,922 bytes)

15. Re: [WriteLog] Network reliability (score: 1)
Author: "Mike Brown" <mike@k9mi.com>
Date: Mon, 12 Nov 2007 15:02:40 -0000
I'm not sure what the differences might be, but we have ran WriteLog at our club's Field Day operation for the past 3 years, and I only remember one time, one of the computers locked up. And upon reb
/archives//html/WriteLog/2007-11/msg00101.html (8,404 bytes)

16. Re: [WriteLog] Network reliability (score: 1)
Author: "Charles Morrison" <cfmorris@bellsouth.net>
Date: Mon, 12 Nov 2007 22:10:13 -0600
My problem has never been with relinking the network after a crash, that's always performed fine. Exit Writelog (a reboot is only necessary if something hangs, which sometimes is a comport), restart
/archives//html/WriteLog/2007-11/msg00104.html (9,941 bytes)


This search system is powered by Namazu