I saw the following posted in the news section of the CWOP web page today…
July 17, 2008 - In the next few days, the APRS Core servers will stop accepting unverified packets. Any CWxxxx, DWxxxx or unverified ham packets will be rejected and not reach findU or CWOP or MADIS. To prevent this from happening to their packets, CWOP members need to check the recommended servers and make changes if needed.
I changed mine a while ago and I’m still getting the warnings saying I’m on the old server.
Glad to see I’m not the only one getting these messages :roll:.
If using WD this is what I set mine too which works for me (see Attached.
But this thread suggests something different
http://www.wxforum.net/index.php?topic=1862.0;topicseen
IIRC you don’t need to change anything in WD for this to work. Try un-ticking “Use other Server” and you should be fine. I believe Brian already made the necessary changes in WD to connect to the correct server and at the right frequency.
I see in the latest build he has cwop 1 etc, tried as you suggested but the WDFTP hung using the cwops.aprs.net server
I am getting quite a few hung WDFTP operations but I think some of that is due to School Semester break holidays and wet Sunday weather, happened last weekend too… the 350kB animated webcam “videos” stall - or get to 100% and stall and the rest of the list dont get posted 
Sometimes they sit there with the first comms proc and don’t proceed at all… The vagaries of a weak NZ network.
TokKiwi
so what is the official server to use now?
I agree with Dan. Windy has already upgraded WD to use cwop.aprs.net and that automatically rotates to CWOP - 1, CWOP - 2, and CWOP - 3, which are the correct ones to use for non-Ham CWOP users. There is no need to enter the server names in manually. If you check my raw data at: http://www.findu.com/cgi-bin/raw.cgi?call=CW0053 you will see that my packets all read that they were received by either CWOP - 1, CWOP - 2, or CWOP - 3.
EXAMPLE:
CW0053>APRS,TCPXX*,qAX,CWOP-3:@190503z4513.10N/12123.85W_303/005g008t056r000p000P000b10156h44.WD 1
CW0053>APRS,TCPXX*,qAX,CWOP-1:@190513z4513.10N/12123.85W_320/005g009t057r000p000P000b10156h43.WD 1
CW0053>APRS,TCPXX*,qAX,CWOP-1:@190523z4513.10N/12123.85W_305/002g008t056r000p000P000b10156h44.WD 1
CW0053>APRS,TCPXX*,qAX,CWOP-2:@190533z4513.10N/12123.85W_307/000g008t056r000p000P000b10156h45.WD 1
that clears that up… I did not think you were supposed to be using those rotate servers specificly
I think the news statement was to remind those that have not changed to the new regimen have to do shortly or start all over again as they will not be loaded against their data and left high and dry - the old servers will be shut down or used for just the Hams data. Just reading tbetween the lines and best guess…
I think you have done all you need to Brian.
For non-amateurs, (regular CWxxxx, DWxxxx ids) Gerry Creager said this on the CWOP mailing list
If you’re going to explicitly name servers instead of using the round-robin cwop.aprs.net, please use
cwop1.aprs.net 165.91.140.46 (cwop1.tamu.edu)
cwop2.aprs.net 70.57.237.99 (cwop.fuller.net)
cwop3.aprs.net 193.1.193.154 (sip.tssg.org)Ports 23, 14580 are accepted. I recommend 14580, because a lot of firewalls at companies and ISPs are blocking 23 even outbound these days.
Either Russ or I can help with valid passcodes for Amateur Radio Operators using their callsigns on rotate.aprs.net (or Tier2) to submit.
Non-Hams will continue to use the default passcode (-1) resulting in an unverified connection, on CWOP servers via cwop.aprs.net
Gerry
So my reading of the above suggests that my current CWOP configuration should be OK into the future?
If this looks wrong, please can someone let me know?
no, as you need the full server name for the rotate to servers,…you dont have the full server name entered there…
Does the attached snap look better? If not, perhaps someone could post a snap of the correct settings.
I think this is correct.
Thanks, I’ll give your settings a go. Interestingly, 2 minutes after I took the above snap, I looked at my CWOP settings and found that the entries for “servers to rotate to” and “2nd servers to rotate to” had been autofilled i.e. I didn’t populate either field (see attached snap). I assume this is normal behaviour if you don’t populate these fields?
Kevin, I’m not sure if you just created that snap to show me the config, but if it’s a snap of your actual config, then I think you have a typo in your setting for 2nd server to rotate to (arps instead of aprs).
never noticed that before… Just corrected it.
Checking my connection logs…
CW2582>APRS,TCPXX*,qAX,CWOP-2:@190652z3324.15N/11152.98W_291/004g009t093r000p000P000b10066h34L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190702z3324.15N/11152.98W_306/002g008t092r000p000P000b10066h35L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190712z3324.15N/11152.98W_307/002g009t092r000p000P000b10068h35L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190722z3324.15N/11152.98W_307/002g007t092r000p000P000b10069h37L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190732z3324.15N/11152.98W_286/001g007t092r000p000P000b10070h36L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190742z3324.15N/11152.98W_325/000g003t091r000p000P000b10073h38L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190752z3324.15N/11152.98W_325/001g002t090r000p000P000b10076h38L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190802z3324.15N/11152.98W_325/000g002t090r000p000P000b10076h41L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190812z3324.15N/11152.98W_325/002g003t089r000p000P000b10076h40L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190822z3324.15N/11152.98W_327/000g002t090r000p000P000b10078h38L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190832z3324.15N/11152.98W_327/000g001t089r000p000P000b10079h42L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190842z3324.15N/11152.98W_142/003g008t090r000p000P000b10081h38L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190852z3324.15N/11152.98W_130/000g006t090r000p000P000b10081h38L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190902z3324.15N/11152.98W_130/000g003t090r000p000P000b10081h40L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190912z3324.15N/11152.98W_130/000g002t089r000p000P000b10080h41L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190922z3324.15N/11152.98W_123/005g014t089r000p000P000b10081h43L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190932z3324.15N/11152.98W_132/004g008t089r000p000P000b10081h45L0000.WD 31 CW2582>APRS,TCPXX*,qAX,CWOP-2:@190942z3324.15N/11152.98W_142/004g008t089r000p000P000b10080h46L0000.WD 31