Author Topic: Linksys Port Triggering? (Read 1676 times)

lakehavasu · « **on:** October 11, 2007, 04:02:02 am »

I have a Linksys BEFW11S4 (802.11b) router. Is it nessisary to port trigger the TCP and UDP for Winmx to work properly? I have port forwarded my TCP and UDP but it seems that if I don't port trigger I can't get a good connection to Winmx. Any info would be greatly appreciated

bughunter · « **Reply #1 on:** October 11, 2007, 05:40:59 am »

no it shouldnt need to be triggered.........
port triggering is normally for applications that either require multiple ports or usually use different ports when accessing the net each time, so rendering port forwarding useless..........
but haveing said that if port triggering being enabled helps then run with it .............

Me Here · « **Reply #2 on:** October 11, 2007, 04:00:07 pm »

Linksys are pretty straight forward and the port forwarding is definatly the way to go on them usually (i had this model myself at one time)

I would make sure that the linksys has not assigned a new Internal IP to your machine (its very common on them and that breaks portforwarding rules already set to the old ip)

Go to Start > Run > type in cmd
Then click OK
Now in the black box type ipconfig
Then hit the enter key.

Check that the IP Address listed in the above matches what you have for your Port forwarding rules in the router. If they dont match then I might suggest you set up a static IP for the router to always use and thats pretty easy too.. here is a guide for XP.
https://www.winmxworld.com/tutorials/static_ip.html

lakehavasu · « **Reply #3 on:** October 12, 2007, 02:28:59 am »

thanks for all the info, but I tried the Static IP and it didn't work. Didn't change anything. Still connects and then disconnects. Primary =1 then =0 and so on. I had a windows update the other day and that seems to be when the problem started. Winmx does work if I bypass my router. Works great. Winmx used to work with my router configuration but recently quit. Still searching for answers here. Thanks.

Me Here · « **Reply #4 on:** October 12, 2007, 07:49:40 am »

First of all Lakehavasu,

The disconnections are not due to the router settings unless a person is lossing all interent also. Basically the other post you made about finding a patch if you look there at the damage that flooders can do to a person while on primary and pie then you may see why you cant stay connected well.

As for uploads and downloads, searches etc those will be more likely affected by port settings.

Since your actually having issues like this I would highly suggest the patch we offer here that blocks and filters for you. I think you'll find running primary on it much more stable and we can then just deal with any port issues you have.

lakehavasu · « **Reply #5 on:** October 13, 2007, 02:23:20 am »

thanks for the info mehere. I just tried starting up winmx again and it's doing the same there. Connects after about 15 seconds then P=1 then P=2 and maybe sometime P=3 and then goes P=2 then P=1 then disconnects and trys reconnecting again. My bandwidth is also showing maybe 500 and used to just up to 24000 or higher. Any suggestions on what I could try? Thanks

Mike

lakehavasu · « **Reply #6 on:** October 14, 2007, 07:05:07 am »

Quote from: lakehavasu on October 12, 2007, 02:28:59 am

thanks for all the info, but I tried the Static IP and it didn't work. Didn't change anything. Still connects and then disconnects. Primary =1 then =0 and so on. I had a windows update the other day and that seems to be when the problem started. Winmx does work if I bypass my router. Works great. Winmx used to work with my router configuration but recently quit. Still searching for answers here. Thanks.

Ok I'm going to try this again since I didn't set up the static IP in my router the first time. I went to ipconfig/all and my IP address is showing some weird numbers and letters IP Address.......fe80::207:e9ff:fea9
That is what it is showing for my IP Address. Any suggestions?

Me Here · « **Reply #7 on:** October 15, 2007, 06:09:00 pm »

Yes its using IPv6 instead of IPv4 and its rendering it to you as a hash.. go to

Control Panel > Network Connections > Then right click the Local Area Connection > Choose properties

In the new box you see the small menu.. look for IPv6 and untick it.. this may also require a reboot but save changes by saying OK out of this..

and then try the
Start > Run > cmd
THen ok then in the box ipconfig /all
and see if this time its not a correct looking IP
If its not still reboot the machine then try.