Any other DYNDNS in this Account works fine on 2601, now we know that this SPECIFIC dyndns name is an issue. My guess is there is a bug in RP for URL length of prefix. FYI, my prefix is 11 characters, anyone want to bet there is a cutoff at 10?
R
Just did a test on the bad PC.
Connected iPhone to it and used it as IP gateway. Same error immediately pops up, thus, I believe we can conclude that for some reason this particular URL to the M1, from this Particular PC is the specific issue.
How or why it hates this URL is beyond me.
...
Question for anyone who knows. In the list of usernames/passwords, what UN is used for the connection? Does it try the first then if fail move to the second? Some other logic?
Ross
TurboSam - No VLAN's, no changes of note other than to fully disable the FW on the XEP problem side.
Tonight I moved over from the working PC the following directories:
C:\Users\Ross\Desktop\ElkRP
C:\Users\Ross\Desktop\RP
I than ran the application and set the database paths to the local RP...
I apologize for the confusion I caused with naming the RP's. All are RP'2's running on PC1 and PC2.
I will copy over the entire working application directory shortly and see what comes of it.
Regards,
Ross
No joy...
Please find attached screens RP1 unable to connect to the problem M1 at 2601 plus Systray and FW, of RP1 not running. RP1 connecting to a different M1 on 2601 no problem, RP2 connection to problem M1 via 2601, no problem.
I was unable to upload images to this post. I placed them...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.