| 1 |
On Monday, September 05, 2011 06:50:35 AM Johannes Geiss wrote: |
| 2 |
> On Fri, 02 Sep 2011 08:50:46 +0200 |
| 3 |
> |
| 4 |
> Joost Roeleveld <joost@××××××××.org> wrote: |
| 5 |
> > What do you mean with, "outside"? |
| 6 |
> |
| 7 |
> I meant from another place via the Internet through my router to my |
| 8 |
> computer. |
| 9 |
|
| 10 |
I suspected this to be the case. |
| 11 |
|
| 12 |
> |
| 13 |
> > [...] |
| 14 |
> > |
| 15 |
> > Hope this helps. |
| 16 |
> |
| 17 |
> Yes, your suggestions helped. Thank you very much. Though it doesn't |
| 18 |
> solve the problem. Now I know I did everything right at my |
| 19 |
> LDAP-server, but the problem is my router (Speedport W 503V Typ C). |
| 20 |
> It's blocking some (not all) of the communication. I forwarded all |
| 21 |
> ports to my computer (ie. it's in the DMZ), but LDAP is not working |
| 22 |
> correctly. |
| 23 |
|
| 24 |
How did you forward all ports? |
| 25 |
I never specify a port-range for port-forwarding, but only specific ports. |
| 26 |
|
| 27 |
I am not familiar with the router you are using, but is there an option to |
| 28 |
specify a specific port? |
| 29 |
|
| 30 |
Alternatively, you could try using port-forwarding/tunneling using SSH- |
| 31 |
connections. Your LDAP-client should be able to hitch a ride over that |
| 32 |
connection if you set up the tunnel. |
| 33 |
|
| 34 |
If you google for "ssh portforwarding" you should find some examples and |
| 35 |
explanations for this. |
| 36 |
|
| 37 |
-- |
| 38 |
Joost |
Archives