QUOTE(abdqds @ 12-10-06, 8:03pm)

While using packet capturing software i am also able to see that besides know requests to DNS now it is requesting a new entry that is time.vonage.net with with NTP, probably Network Time Protocol.
Configure your hosts file (with the domain name 'time.vonage.net') as detailed in
Post #407. Then enable Windows NTP server as explained in
Post #137. This should cause your PAP2 to proceed a bit faster as it won't timeout during the NTP check (although it shouldn't have any practical impact on the unlock process overall).
QUOTE(abdqds @ 12-10-06, 8:03pm)

I haven't seen any recommended changes to HOSTS file with time.vonage.net

Then you haven't read through every post in this thread.

QUOTE(abdqds @ 12-11-06, 3:16pm)

while going through step by step with post 326, I am sure to say that i am stuck at step 7. Adapter doesn't show RED light even after 5 minutes.
Before the LED turns red, while the adapter is loading the new firmware, one of the blue LED's should flash rapidly for at least 5-10 seconds (perhaps longer). If you don't see this happening, the adapter isn't loading the replacement firmware (which is also why the LED doesn't turn RED).
QUOTE(abdqds @ 12-11-06, 3:16pm)

Now at this point i have started analyzing packets captured in those 5 minutes. I can see that adapter is trying to get xml file from TFTP root and a directory (grabbed xml from two locations, TFTP Server Log file Confirms).
Why is the adapter grabbing an XML file from TWO locations? You should only have your PRIMARY XML file staged in the TFTP ROOT at this point in time. You should NOT have your PLAIN TEXT XML FILE staged in the "randomly named" directory at this stage.
QUOTE(abdqds @ 12-11-06, 3:16pm)

After grabbing xml file, adapter starts requesting ls.tftp.vonage.net first on port 21 and then if not successful then goes to port 2400 with the same ls.tftp.vonage.net.
So long as it gets the PRIMARY XML FILE from your TFTP root, all subsequent TFTP requests can and should be allowed to FAIL.
QUOTE(abdqds @ 12-11-06, 3:16pm)

If i will remove the port forwarding that was 21 and 2400 to 69
Like I said before, remove the port forwarding. You've already confirmed that your adapter grabs its XML file from the TFTP server @ port 69.
QUOTE(abdqds @ 12-11-06, 3:16pm)

Here i am confused that tftp log file shows that (only when port is forwarded) timeout occur communicating with httpconfig.vonage.net. But packets captured clearly proves that basically request is for ls.tftp.vonage.net.
If you remove port forwarding, then this doesn't happen. As for why it's showing 'httpconfig.vonage.net,' perhaps that's the "most current" domain name belonging to that IP address in your hosts file. To test this theory out, open up a command prompt and type:
ping -a 192.168.0.1If the ping response shows a domain name, and if that domain name is 'httpconfig.vonage.net,' that's what your PC is considering the primary domain name for 192.168.0.1. How can you change this? Re-arrange the order in which you've defined domain names in your hosts file.
QUOTE(abdqds @ 12-11-06, 3:16pm)

Is it possible that it is requesting the files from http via tftp right after grabbing xml file.
If the unlock process works as it's intended to, the adapter should be making an HTTP REQUEST (i.e. TCP/IP port 80) to
httpconfig.vonage.net, not a TFTP request (i.e. UDP to port 69, 21, or 2400).
QUOTE(abdqds @ 12-11-06, 3:16pm)

Any ideas, whats is this situation actually ?
Hopefully some of the above helps determine what's going on.
Diggler