Non-exit Relay problems ORPort(?)


3 years ago
I have Tor Bundle on 2 Windows machines and one Linux machine. All 3 are set up the same in Vidalia (except different Nicknames). No apparent problems on Linux machine, but on both Windows machines:

Non-Exit Relay
No valid UPnP-enabled Internet gateway devices found
(with automatic port forwarding test)

Message log says (and here is the problem, I would assume):
Sep 20 11:45:42.640 [Warning] Your server (BLANKED:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.


Network map shows dozens of connections.... all OPEN. I don't really know what this means.

What I have tried:
Configuring Windows Firewall to open appropriate ports .. but did not really understand it .... sooo ...
Disabling Windows Firewall (temporarily).
Checking router ..UpNP is enabled. (all 3 machines on same router ... wired)

Entire Message Log (don't know which IP addresses are safe to post .. blanked all of them):

Sep 20 11:25:29.198 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Windows 7.
Sep 20 11:25:29.198 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Sep 20 11:25:29.198 [Notice] Read configuration file "E:\Tor Browser\Data\Tor\torrc".
Sep 20 11:25:29.304 [Notice] Initialized libevent version 2.0.21-stable using method win32. Good.
Sep 20 11:25:29.304 [Notice] Opening Socks listener on BLANKED
Sep 20 11:25:29.304 [Notice] Opening Control listener on BLANKED
Sep 20 11:25:29.304 [Notice] Opening OR listener on BLANKED
Sep 20 11:25:29.304 [Notice] Opening Directory listener on BLANKED
Sep 20 11:25:44.616 [Notice] Parsing GEOIP file .\Data\Tor\geoip.
Sep 20 11:25:44.616 [Notice] No AES engine found; using AES_* functions.
Sep 20 11:25:44.616 [Notice] This OpenSSL has a good implementation of counter mode; using it.
Sep 20 11:25:44.616 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Sep 20 11:25:44.616 [Notice] Your Tor server's identity key fingerprint is 'BLANKED'
Sep 20 11:25:44.616 [Notice] Reloaded microdescriptor cache. Found 5481 descriptors.
Sep 20 11:25:44.616 [Notice] We now have enough directory information to build circuits.
Sep 20 11:25:44.616 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Sep 20 11:25:44.616 [Notice] New control connection opened.
Sep 20 11:25:44.616 [Notice] Guessed our IP address as BLANKED (source: BLANKED).
Sep 20 11:25:44.616 [Notice] Heartbeat: It seems like we are not in the cached consensus.
Sep 20 11:25:44.616 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 3 circuits open. I've sent 31 kB and received 210 kB.
Sep 20 11:25:44.616 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Sep 20 11:25:44.617 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Sep 20 11:25:45.718 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Sep 20 11:25:45.718 [Notice] Bootstrapped 100%: Done.
Sep 20 11:25:45.718 [Notice] Now checking whether ORPort BLANKED:443 and DirPort BLANKED:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 20 11:39:05.346 [Notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Sep 20 11:45:42.640 [Warning] Your server (BLANKED:443) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.


and I am at a loss. Assistance appreciated in advance.

Reply

You are not logged in. Login or register to reply on this thread.