Windows 7 - Windows Live Sync--Online (Behind NAT)

Asked By Mordido

06-Nov-09 04:58 PM

There is four ports to Windows Live Sync.  Open "more," ", Settings," and
then "Port Status, there is TCP ports  80, 443, 6561, and 8000.  For the past
month TCP Port 443 is the reason (Behind NAT) always appears when I open
Windows Live Sync.  I have tried everything, i.e. went to my Linksys router's
xxx.xxx.x.xxx.basic.htm, and port forwarded all Windows Live Sync's TCP
ports.  I have gone into Win XP's Firewall settings, opened Exceptions and,
first,  I Added [a] Program, Windows Live Sync, which includes all the ports.
Then I Added [a] Port, all four TCP ports.  I have tried everything I know and
every try ends with TCP Port 443 Initiate Connection (OK), but Accept
Connection (Blocked).  Therefore, Windows Live Sync--Online (Behind NAT).

TCP Port 443 is the only port that will not Accept Connection.  Prior to the
past month, all four TCP Ports Initiated and Accepted Connections (OK).  I
cannot get TCP Port 443 to Accept a Connection.  I have done what I have always
done to clear a port, but this time, whether I Use UPnP to Automatically
Forward Port, Test Ports Through Firewall (Port Forwarding), or both, i.e.
put a check in both Use UPnP to Automatically Forward Port, and, put a check
in Test Ports Through Firewall (Port Forwarding) also.  Still, TCP Port 443
is Blocked.

Can anyone help?

06-Nov-09 06:06 PM

Why do you care when you already have more than enough ports to allow p2p
connections with your other library sharers?

As to why it is happening, maybe another application is configuring your
router via uPnP to seize that port or maybe your ISP is blocking that port
or maybe your router uses that https port number for remote management.

Tony

06-Nov-09 07:23 PM

Online (behind NAT) is what it should be saying. The NAT (Network Address
Translation) is being done in your router. If it says Online, then it is OK.

It is simply letting you know that Sync is connected to the internet thru a
router, not directly.

Michael

23-Nov-09 06:50 PM

i have the identical problem and the computers set up for sync do not sync.
i am behind a cisco firewall on a company network and all of the sync
computers are also. the ports say they are open and receiving is blocked.
this stopped working when i downloaded the update to window live sync. it
worked fine before.

bill

11-Jan-10 01:19 PM

The reason I checked no (help) is that for a couple month use of Windows Live
Sync, port 443 was not behind NAT.  All four ports werre open.  I finally got
the "creative idea" that 443 might be in use.  I opened my Local Area
Connection/Status/Properties/Advanced (Tab), and under "Advanced" there is
Windows Firewall, beneath Firewall there is "Protect my computer and network
by limiting or preventing access to this computer from the Internet."

I then click "Settings" (to the right of the sentece I just quoted.)/Windows
Firewall Advanced (tab).  Inside Advanced (tab) there are two Local Area
Connection (one of them disabled) and a 1394 Adapter Connection.  I clicked
the "Setting" for the Local Area Connection I currently use.  Inside
Advanced/Settings there is two (2) tabs, i.e. Services and ICMP.  I am
concerned with Services, the ten (10) services provider--if you so desire and
put a check-mark in the square to the left of their title.

For example, there is FTP Server, Internet Mail Access Protocol Version 3
(IMAP3) serves...down to Remote Desktop, and to #7, Secure Web Server
(HTTPS).  You can hi-lite the service/server and click Edit below.  I have
brought you to Description of Service--again Secure Web Server (HTTPS) is the
services with which I am conerned--that particular point is the Description of
Servicee, and to end this long winded dissertation, and the bottom of the
pop-up, i.e. Service Settings, there is External Port number for this service
(443); next, Internal Port number for this service (443), and to the right in
two (2) TCP already had a bullet in the circle.circles:  TCP--UDP.

OK, my point is that port 443 is already being used for TCP purposes, and
this usages might, and I strongly believe it is, the reason for the NAT
Block.  I mean I was using port 443 for a couple months before it went behind
NAT.  I believe all four ports, i.e. 80, 443, 6571, and 8000 (all in TCP
usage) are meant to be used, not blocked.

So now we know that, at least on my computer--I know little about Internal
and External port but I do know that a port in use holds the line usually
until it is hung-up.  I am currently trying to contact someone in Windows Live
who can either verify or refute  what I have just told you.  Therefore, I
selected and checked "no" your suggestion did not help, but I do appreciate
your willingness to help me.  Thank you.

11-Jan-10 01:23 PM

Hey, Bill:  I forgot all about the update.  Now, after reading your post, I am
thinking that is about the same time that I started having NAT problems with
port 443.  Have you gotten any help or solution?

11-Jan-10 01:52 PM

There is all kinds of "maybes."  Maybe all four (4) ports are supposed to be
in use.  As I said, at one time, all four ports ran on my computer and my
computer downloaded the Windows Live Place Holders much faster than the Place
Holders work now.  I think that was because--MAYBE!--when you are downloading
many files and LARGE FILES too, then four ports would do a much faster job of
downloading than just three ports.

Anyway, I asked if anyone/somebody could help me with my problem.  I did not
ask to be critiqued or critized with a veiled tongue spankiing because you
did not like my question or request for help.  In your mind set, I should have
just accepted blocked port 443 as part of the application.

To end, I concluded my post  with a request for help, a question:  Can
anyone help? and you answered my question with a question, i.e. "Why do you
care when you already have more than enough ports to allow p2p connections
with your other library sharers?"  Why I care is my business and I was not
looking for a psychologist or counselor to help me get my life together.  I
wanted help with port 443's NAT problem.  If you had or have facts and
figures, I will gladly listen and if you can prove that it does not matter that
port 443 is behind a NAT wall, I will accept proof, and in this NAT problem, if
it does not matter, and you can prove it, what a relief.  I do not have to
struggle looking for what is causing a NAT problem.  BUT, in my experience, a
NAT problem is not good; it one is installing or port-forwarding or UPnPing
correctly therre would not be a NAT problems.  Yet, I am always open to reason.
Have a good day, Anthony.