Anyone know why you can not use NLC (New London, CT) as a "stop" on a multi segment trip?

I many times travel on a multi from KIN to OSB. However, if I attempt to put in KIN-WLY-MYS-NLC-OSB for a 4 segment multi, it gives me one train from KIN to NLC - but the next train from NLC to OSB! But if I input a 3 segment multi for KIN-WLY-MYS-OSB (through NLC!), I can do it on the same train!

Normally, this would not be a problem, but I am losing a segment each way! And with the multiple promotions going on, that's 400 to 1200 points per trip!

I understand dwell time in places like NHV (2-5 minutes), NYP (15-30 minutes), PHL (3-10 minutes), and others. But there is none listed for NLC on any schedule! So why am I losing these AGR points?

No idea why it might be doing that. Possibly just a quirk in the computer system or perhaps it's related to the fact that NLC has a Thruway connection. Thruway connections sometimes affect how the computer handles certain types of trips.

However, try making two reservations instead of one. Break up the trip and you should still be able to get 4 tickets and the max points. I don't think that the trip will cost anymore, although I admit I haven't tested the theory.

Using that reason (Thruway connection) would eliminate many California multi segment trips, as many of them also have Thruway connections. And we've heard of many such CA multis!

Perhaps, it is just a quirk! But it's to bad I have to lose a segment every time!

I experience this same quirk NYP-NWK quite often.
All trains stop in NWK. I can book NYP-EWR, or NWK-EWR, but not NYP-NWK-EWR on the same train. In fact the previously available train does not even show up as an option NYP-NWK when booking multi segments.

i had a problem booking was-phl. When i selected four segments it would push a segment here or there to a later train automaticly. I couldn't figure out why it did it. I made two round trips with in a week and lost 4 segments or $1,800 points.

I think this has something to do with the fact that, on the timetable, Newark is generally marked with an "R" to indicate that it is to receive passengers only. Leaving from Washington, I often run into the same problem that you describe if I try to book Washington-New Carrollton, and I've always assumed it had somehing to do with the fact that NCR is marked "R" on nearly every train. I'm not 100% why the system does what it does -- if it really meant the stop to be to receive passengers only, it seems that it shouldn't let you book NYP-NWK at all, but it will -- but I'm pretty sure the R is the reason.

Newark is a "receive passengers only" (R) stop only on some trains; on others, it is a stop for both boarding and disembarking passengers. Amtrak will not let you book a multi-segment ticket with NWK as your destination on any one segment on a train that stops at NWK only to receive passengers. In other words, you cannot make NWK your destination (either final or intermediate) on any train that does not discharge passengers at that station.

The problem with PHL has been discussed previously in this forum. It appears that there is unpublished "dwell" time in the PHL schedules, so that the departure and arrival times are not identical. The Amtrak booking engine will let you book a "connection" (to the same train) with zero minutes between legs; it will not let you book a connection with three or five minutes between legs. (I'm not sure what the minimum connecting time is once you get beyond zero minutes, but clearly it's something more than just a few minutes.)

The dwell time in PHL is unpublished on the NEC1 schedule (NYP-WAS only), but it was published in the NEC2 (BOS-NPN) last timetable (fall/winter), but is not published in the current spring/summer timetable. I don't know if it's in the current (big) national timetable book. (It was in the last book.)

Yes, you're right. But whether the dwell time is published or unpublished will not affect one's ability to book a multi-segment ticket with PHL as connecting point. If there is dwell time in the schedule (published or unpublished), you will not be able to use PHL as a connecting point if you wish to "connect" to the same train on a multi-segment itinerary.

Why NLC continues to be a problem for multi-segment ticketing remains a mystery.