Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[stogs]

I have a HP mediasmart server that attempts to automatically configure port forwarding to enable my home website and remote access.  This all worked well in 1.21 and 1.22b, I seem to be having issues with it in 1.31.

I followed all the instructions for the upgrade and did not reload the old config.  I started from scratch after restoring to defaults.  I see the following items in the log when my homeserver attempts to configure port forwarding, these entries have always been the same between firmware versions:

INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XXX.XXX.XXX:4125 <-> 192.168.1.198:4125 TCP timeout:0 'WHS_4125'
[INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XX.XXX.XXX:443 <-> 192.168.1.198:443 TCP timeout:0 'WHS_443'
[INFO] Sat Jan 31 12:35:14 2004 UPnP added entry 255.255.255.255 <-> XXX.XXX.XXX.XXX:80 <-> 192.168.1.198:80 TCP timeout:0 'WHS_80'

Note:  Actual IP removed and replaced with X, it was correct.   

After it executes, everything works fine for about 10 minutes and then the settings must timeout.  I have manually added the port forwarding entries and everything seems to work ok so far, I am just curious as to why this behavior changed.  Any thoughts?



 

[Lycan]

It would depend on how the server is communicating with the gateway device. Is it using UPnP?

[stogs]

I believe so, yes.

[EddieZ]

It should ber working without a problem. Unless you turned off uPnP on the router or there is an internet gateway device on the WAN side and those ports need to be opened too. That does not happen automatically....

[stogs]

I agree it should be working.  Since it was working fine in previous firmware versions for months.  I have Upnp turned on.  From the logs I can see it forwarding the ports.  It will work for about 10 minutes and then I start to see request blocked in the logs for those same ports.

It has been working fine for a couple days after I manually forwarded the ports.  I was just curious if this was a bug in the new firmware or if I had some setting messed up.  I was also curious if anyone else was seeing this issue.  This automatic router configuration is out of the box functionality for Windows Home Server.

[bananaman]

Hi stogs!

I had exactly the same issue with 1.31 and my Windows Home Server.

I solved it by disabling UPnP and manually forwarding the ports.

UPnP does not work properly in version 1.31.

[EddieZ]

Hi stogs!

I had exactly the same issue with 1.31 and my Windows Home Server.

I solved it by disabling UPnP and manually forwarding the ports.

UPnP does not work properly in version 1.31.

Apparently only with WHs, because 1.31 uPnP does a fine job with torrent clients, all sorts of games, RDP....

[aben2amu]

I am having a port forwarding problem, I am trying to configure several ports for 3 computers on my network. I have tried to configure several rules depending on each computers static LAN address, I save it and reboot the router and the list is empty, no rules whatsoever are saved.
Another question, Is there a way to create rules for the LAN and not machine specific? The 3 computers have the same software. I would like to be able to just open the ports so the 3 can actually interact with the internet. Is this possible?

Thanks,

AJ

[Lycan]

What browser are you using to configure the router?

[aben2amu]

IE 8 or Firefox 3.0.10, neither one saves. I even tried Chrome, still no saving. I will try Safari.
Ok I got it working as Application Rules. So all the necessary ports are open for all computers in my LAN.
I thought I had it configured but no, the Application Rules table won't get deleted, either manually or hard resetting the router. It is driving me crazy.

[TLE]

I am also having this issue with my windows home server.

[Soylent_Geek]

Hey guys,

I have had the same problem and was experiencing the uPnP issue with my slingbox as well.

What I did was uncheck the uPnP option, reboot the router, re-check uPnP, and reboot the router and suddenly everything started working again.

Might be a glitch in the firmware.

Try it and let me know if it worked for you.

D.

[ttmcmurry]

I skipped right to the end of this post, so sorry if its been said already:

You mentioned you went from 1.2x to 1.3x.  What I want to know:

1)  Did you backup your 655 config prior to the upgrade?
2)  In lieu of that, did you write down your settings?
3)  If you haven't yet, can you?
4)  Have you tried resetting to defaults via either the GUI and/or the RESET button?
5)  Would you be willing to do that and put said settings back into the 655?

Most of the issues I see are from when the router makes a generational jump in firmware and somehow, someway the config gets screwy.  The only solutions I've seen in the forum and real life that really worked included factory resets.  You could spend hours instead of fixing the actual problem doing things such as turning an unrelated feature off... suddenly makes port forwarding work.  Solutions like that simly mask the issue.

Just my two cents.

[TLE]

1)  Did you backup your 655 config prior to the upgrade?
No not in this instance as I was going to configure the router from scratch

2)  In lieu of that, did you write down your settings?
I have print out of each page where I have non standard settings

4)  Have you tried resetting to defaults via either the GUI and/or the RESET button?
I have tried two factory re-sets using both the web to re-set the router,
and have also tried the button on the back of the router

Neither scenrio worked, its not really a problem as I forwarded the ports on manually, but if a feature is there I do like to use it..lol

Is there anything else we can do to try and resolve this? Will the logs show why the ports have been closed when they were previously opened by UPnP?

[TLE]

I am wondering if it could be somthing to do with the below logging.

[INFO] Thu May 14 21:59:06 2009 Blocked incoming TCP connection request from xxx.xxx.xx.xxx:3176 to xxx.xxx.xx.xxx:443
[INFO] Thu May 14 21:58:57 2009 Above message repeated 2 times
[INFO] Thu May 14 21:58:41 2009 Blocked incoming TCP connection request from xxx.xxx.xx.xxx:3175 to xxx.xxx.xx.xxx:80
[INFO] Thu May 14 21:58:31 2009 Above message repeated 2 times

443 and 80 are 2 of the ports which windows home servers uses. Both the request from IP address and the to IP address were my static IP address assigned by my ISP.

Any thoughts?