D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: bem2x on April 19, 2008, 09:02:26 AM
-
i cant establish a video chat connection while using this router. it works when i used my old router or if i connect directly to the modem. but when i use dir-655, it always give "unable to establish a connection" error. could anyone help? because i really want to use ichat video chat. btw, i;m running osX10.5 dir-655 firmware 1.11 HW A3
logs:[INFO] Sat Apr 19 11:27:56 2008 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.109 to 24.64.106.252
[INFO] Sat Apr 19 11:27:56 2008 Above message repeated 2 times
[INFO] Sat Apr 19 11:27:30 2008 Blocked incoming TCP packet from 69.156.111.236:2461 to 24.36.23.158:16512 as RST:ACK received but there is no active connection
[INFO] Sat Apr 19 11:24:00 2008 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.109 to 24.64.200.199
[INFO] Sat Apr 19 11:24:00 2008 Above message repeated 2 times
[INFO] Sat Apr 19 11:22:29 2008 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.109 to 24.64.89.132
[INFO] Sat Apr 19 11:22:29 2008 Above message repeated 2 times
[INFO] Sat Apr 19 11:22:28 2008 Blocked incoming TCP connection request from 69.156.111.236:2461 to 24.36.23.158:16512
[INFO] Sat Apr 19 11:22:19 2008 Above message repeated 2 times
[INFO] Sat Apr 19 11:22:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52747 as RST received but there is no active connection
[INFO] Sat Apr 19 11:22:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52709 as RST received but there is no active connection
[INFO] Sat Apr 19 11:22:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52710 as RST received but there is no active connection
[INFO] Sat Apr 19 11:22:09 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as RST:ACK received but there is no active connection
[INFO] Sat Apr 19 11:21:50 2008 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.109 to 221.208.208.98
[INFO] Sat Apr 19 11:21:30 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as ACK received but there is no active connection
[INFO] Sat Apr 19 11:21:17 2008 Blocked incoming TCP packet from 172.21.135.37:6293 to 24.36.23.158:52830 as RST received but there is no active connection
[INFO] Sat Apr 19 11:21:05 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:20:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52717 as RST received but there is no active connection
[INFO] Sat Apr 19 11:20:01 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:18:57 2008 Above message repeated 1 times
[INFO] Sat Apr 19 11:18:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52691 as RST received but there is no active connection
[INFO] Sat Apr 19 11:18:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52648 as RST received but there is no active connection
[INFO] Sat Apr 19 11:18:16 2008 Blocked incoming TCP packet from 74.125.47.111:993 to 24.36.23.158:52642 as RST received but there is no active connection
[INFO] Sat Apr 19 11:17:53 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:17:19 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52651 as RST:ACK received but there is no active connection
[INFO] Sat Apr 19 11:16:49 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:16:31 2008 Blocked incoming TCP packet from 205.188.13.4:5190 to 24.36.23.158:52718 as RST:ACK received but there is no active connection
[INFO] Sat Apr 19 11:16:22 2008 Blocked incoming TCP packet from 205.188.13.4:5190 to 24.36.23.158:52718 as ACK received but there is no active connection
[INFO] Sat Apr 19 11:16:16 2008 Blocked incoming TCP packet from 172.21.2.6:6293 to 24.36.23.158:52807 as RST received but there is no active connection
[INFO] Sat Apr 19 11:16:15 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52651 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:16:06 2008 Blocked incoming TCP packet from 205.188.13.4:5190 to 24.36.23.158:52718 as PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:15:45 2008 Blocked incoming TCP packet from 216.155.193.170:5050 to 24.36.23.158:52728 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:15:40 2008 Blocked incoming TCP packet from 205.188.13.4:5190 to 24.36.23.158:52718 as PSH:ACK received but there is no active connection
[INFO] Sat Apr 19 11:15:14 2008 Above message repeated 1 times
-
Try disabling the SPI under advanced/firewall. That should help.
-
Try disabling the SPI under advanced/firewall. That should help.
did that, still doesnt work..
-
I'm having the same problem. I've turned off SPI, and it still won't let iChat video or screen sharing through. This is what I see in the log on the router:
UPnP renew entry 255.255.255.255 <-> 68.99.181.196:55312 <-> 192.168.0.189:16402 UDP timeout:-1 'iC55312'
UPnP added entry 255.255.255.255 <-> 68.99.181.196:55312 <-> 192.168.0.189:16402 UDP timeout:-1 'iC55312'
I've upgraded the firmware to 1.21, but that'd didn't help either.
Has anyone solved this issue?
-
Have you tried changing the router firewall (UDP / TCP) settings? Default they're quit strict, so you might want to lossen them up a bit.
-
What are your firewall settings built into the OS X? You should try leaving it completely open, and remove port stealthing, and that should be okay.
If it still doesn't work, set the NAT filtering for both TCP and UDP to Endpoint Independent and see what happens.
-
Both macs on my internal network have the mac firewall set to allow all incoming connections.
I set both UDP and TCP Endpoint filtering to Endpoint independent and rebooted the router.
I still can't get the video or screen sharing working, and the router has errors in the log like:
Blocked incoming TCP packet from 192.73.8.28:443 to 68.99.181.196:56307 as ACK received but there is no active connection
UPnP added entry 255.255.255.255 <-> 68.99.181.196:54757 <-> 192.168.0.189:16402 UDP timeout:-1 'iC54757'
I've also turned off the ALG/SIP setting, and that didn't help. For some reason this DLink is still blocking the ichat video sharing.
-
I don't see any blocking messages for the iChat application/ports....
Blocked incoming TCP packet from 192.73.8.28:443 to 68.99.181.196:56307 as ACK received but there is no active connection
Has nothing to do with iChat
UPnP added entry 255.255.255.255 <-> 68.99.181.196:54757 <-> 192.168.0.189:16402 UDP timeout:-1 'iC54757'
This is OK, registering with the router to get the ports open.
Are you sure your internet gateway has also opened the necessary ports?
-
Are you sure your internet gateway has also opened the necessary ports?
Not sure about that. The DIR-655 is connected to a Motorola SB5101 cable modem. Is that what you mean by internet gateway? If so, I've never used a web interface to the cable modem at all, and I couldn't find anything about that in the manual for the Motorola. These are the settings I've changed on the DLink so far with no success:
Disable SPI
Change UDP Endpoint Filterting to: Endpoint Independent
Change TCP Endpoint Filterting to: Endpoint Independent
Disable ALG/SIP
Enable WAN Ping Respond
I can check anything else that you think I should. Thanks.
-
You might want to inquire with your ISP if the Motorola needs to have ports configured in your setup.
-
You might want to inquire with your ISP if the Motorola needs to have ports configured in your setup.
EddieZ, i'm not sure where you live, but the Motorola modems are just what they are - modems. There is nothing to be opened on them, as they pretty much allow all connections. There is nowhere on there to set such a thing.
@ OP: Try disabling UPnP, and manually add a port forwarding rule. You can even try setting your machine in the DMZ, and seeing what happens. UPnP is broken, and has been for a while.
http://support.apple.com/kb/HT2282
Check that out. I noticed that it ONLY uses some random port, instead of the ones that it's supposed to if it cannot establish a proper connection. Try those ports listed in there, and/or putting your machine in the DMZ, and see what happens.
-
I don't have one for sure ;). Only some cable providers and they tend to close all kinds of ports for security reasons. I contest the fact that UPnP is broken. It works flawless here (BT, MSN etc)
-
I don't have one for sure ;). Only some cable providers and they tend to close all kinds of ports for security reasons. I contest the fact that UPnP is broken. It works flawless here (BT, MSN etc)
Go look again at what Firmware version he was using, before you post again please.
And again, I don't know where you live, but it's obviously not in the US. The Motorola modems, do NOT have anything in which they can turn off ports, or open them at will - again, it is JUST a modem, that allows ALL connections regardless. Blocking of ports, or opening them is done on the ISP side. Almost ALL of the cable providers HAVE all open ports, except port 80, and 25.
-
Go look again at what Firmware version he was using, before you post again please
Excuse me? UPnP also worked fine in 1.11, so don't get ****y on me please.
And again, I don't know where you live, but it's obviously not in the US. The Motorola modems, do NOT have anything in which they can turn off ports, or open them at will - again, it is JUST a modem, that allows ALL connections regardless. Blocking of ports, or opening them is done on the ISP side. Almost ALL of the cable providers HAVE all open ports, except port 80, and 25.
I don't know where you are from, but apparently you're not very well informed about my local situation (non-US). So perhaps bem2x is not even American...who knows...
-
Well it works fine now after I swapped out the DIR-655 with my friends spare Linksys WRT54G2 router. I tried iChat Video/Screen sharing with another mac inside my network, and several outside, and all worked great with the Linksys.
So that at least confirms the DLink is culprit. I do like the securespot feature for my kids. Does anyone think upgrading to 1.31 or even 1.32 would be worth a shot? I'll probably try it anyway just to see if I can get it to work without having to buy a new router.
-
If you were running SecureSpot that would stop the iChat.
LOL.