rejetto forum
Software => HFS ~ HTTP File Server => router & port problems => Topic started by: photonman on May 07, 2009, 08:57:29 PM
-
Hi,
I have a problem that baffles me. My HFS runs great, self-test OK, some files downloaded. But, a couple of times my server has been inaccessible, and when I open HFS the designated port has changed from 80 to 7000.
I have just transfered from a crashed XP system to a brand new Vista system. I followed the instructions at Portforward.com for my Linksys BEFW11S4 V4 when I set up the new system, but of course I may have botched the set up. One other fact: I was having problems with Dyndns updater, which I installed as a service. The service kept stopping, so I uninstalled and reinstalled it as a regular process, not a service.
Can anyone tell me what might be causing the port to change from 80 to 7000, seemingly at random?
Many thanks for any help
Photonman
-
A very strange problem. The port where HFS listens to the world is set by HFS, and can not be changed by router.
Does port change when HFS is running or does port change when you restart HFS ?
Do you use some recorded macros in another program? Do you type in some program something that contains 7000 ?
-
Search if other program use port 80.
hfs change the default port if it is open.
Applications like "SKIPE", or "Intenet Information Server", "APACHE", use port 80, only one programa at once.
Run this command line y "star menu", "RUN":
cmd /c netstat -anovbp tcp > %temp%\netstat.txt & start notepad %temp%\netstat.txt
This, open a "dos box", dump result of the netstat command to a file netstat.txt in Windows
temp folder and open it in notepad.
Search something like this: (it's an example)
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
[System]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4534
[skype.exe]
well, the second line show a program that use port 80 with PID 4534 and his name.
Try to change the port 80 in the program and tell us if the hfs works in port 80.
Bye.
-
I do use some macros, but I don't think anything would have generated a "7000" string. I've restarted several times, and the port has been steady on 80 all day.
So, maybe my brain is being controlled by aliens who like the number 7000, huh? I guess I'll check it frequently and if it changes again maybe I can pin down some event that might have produced the change. Switching to Vista has been a massive hassle, and I would not be surprised if some helpful microsoft feature is at the root of my problem.
Thanks,
Photonman
-
Thanks. If I can figure out how to give the operation "elevation" I'll report back.
-Photonman
Search if other program use port 80.
hfs change the default port if it is open.
Applications like "SKIPE", or "Intenet Information Server", "APACHE", use port 80, only one programa at once.
Run this command line y "star menu", "RUN":
cmd /c netstat -anovbp tcp > %temp%\netstat.txt & start notepad %temp%\netstat.txt
This, open a "dos box", dump result of the netstat command to a file netstat.txt in Windows
temp folder and open it in notepad.
Search something like this: (it's an example)
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
[System]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4534
[skype.exe]
well, the second line show a program that use port 80 with PID 4534 and his name.
Try to change the port 80 in the program and tell us if the hfs works in port 80.
Bye.
-
Uhm...should there be 50 lines? Should I be feeling paranoid? No other port 80 lines listed for Local Address, but some listed for foreign address:
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 3868
[hfs.exe]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 956
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 616
[wininit.exe]
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 1088
Eventlog
[svchost.exe]
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1180
Schedule
[svchost.exe]
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 660
[services.exe]
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 676
[lsass.exe]
TCP 127.0.0.1:12025 0.0.0.0:0 LISTENING 2392
[ashMaiSv.exe]
TCP 127.0.0.1:12080 0.0.0.0:0 LISTENING 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49227 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49240 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49242 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49243 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49252 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49253 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49256 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49258 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49262 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49264 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49266 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49267 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49272 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49276 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49278 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49280 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49281 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49284 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49286 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49288 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49290 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49292 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49294 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49296 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49297 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49298 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49299 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49304 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49306 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49307 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49308 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49312 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49313 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49315 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49321 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49324 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49325 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49328 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49330 TIME_WAIT 0
TCP 127.0.0.1:12080 127.0.0.1:49332 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49333 ESTABLISHED 2412
[ashWebSv.exe]
TCP 127.0.0.1:12080 127.0.0.1:49336 TIME_WAIT 0
TCP 127.0.0.1:12110 0.0.0.0:0 LISTENING 2392
[ashMaiSv.exe]
TCP 127.0.0.1:12119 0.0.0.0:0 LISTENING 2392
[ashMaiSv.exe]
TCP 127.0.0.1:12143 0.0.0.0:0 LISTENING 2392
[ashMaiSv.exe]
TCP 192.168.1.137:139 0.0.0.0:0 LISTENING 4
Can not obtain ownership information
TCP 192.168.1.137:49228 74.125.45.101:80 CLOSE_WAIT 2412
[ashWebSv.exe]
TCP 192.168.1.137:49237 209.85.225.113:80 TIME_WAIT 0
TCP 192.168.1.137:49239 65.117.152.81:80 TIME_WAIT 0
TCP 192.168.1.137:49247 65.117.152.81:80 TIME_WAIT 0
TCP 192.168.1.137:49259 206.57.28.57:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49277 65.55.11.254:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49279 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49282 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49283 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49285 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49287 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49289 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49291 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49293 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49295 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49300 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49301 204.2.215.66:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49302 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49303 204.2.215.34:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49309 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49310 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49311 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49314 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49317 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49319 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49320 204.2.208.47:80 TIME_WAIT 0
TCP 192.168.1.137:49322 204.2.208.47:80 TIME_WAIT 0
TCP 192.168.1.137:49323 204.2.208.47:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49326 207.46.198.247:80 TIME_WAIT 0
TCP 192.168.1.137:49327 207.46.198.247:80 TIME_WAIT 0
TCP 192.168.1.137:49329 204.2.208.73:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49334 65.55.11.254:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49335 65.55.11.254:80 ESTABLISHED 2412
[ashWebSv.exe]
TCP 192.168.1.137:49340 65.212.118.29:80 TIME_WAIT 0
TCP 192.168.1.137:49341 65.212.118.29:80 TIME_WAIT 0
TCP 192.168.1.137:49344 65.212.121.26:80 TIME_WAIT 0
TCP 192.168.1.137:49345 65.212.121.26:80 TIME_WAIT 0
-
It's correct!
Your hfs works fine, use port 80 for any ip ( mask 0.0.0.0 ) , local ( lan ) and internet ( wan )
Can you stop the server, exit, and rename the hfs folder.
Download the last beta version and copy to a folder C:\hfstest ( for example )
Create some users 01 02 03 with pass 01 02 03 ( an other example ;) )
Try load and download with users, delete, etc.
Tell us thah happen with the test.
bye.
-
I see that use "Avast Internet Security Suite".
You need access to port 80 in hfs.exe in "SERVER" mode.
Review config oh this an set access for hfs.exe to internet unrestricted.
Your firewall can block an specific port of your hfs or any activity of the program.
Tell us if you resolve it.
bye.
-
7000 is the last port attempted by the self-test.
i can't tell what's the problem there, but the 7000 is coming from this for sure.
maybe HFS can't write the new configuration because Vista is blocking it.
try running "as administrator".
-
I see that use "Avast Internet Security Suite".
You need access to port 80 in hfs.exe in "SERVER" mode.
Review config oh this an set access for hfs.exe to internet unrestricted.
Your firewall can block an specific port of your hfs or any activity of the program.
Tell us if you resolve it.
bye.
Turrenell, I think you are right or at least close. I checked the firewall settings and found no "unblock" entry for port 80. I thought I had already done that, and the system was working fine sometimes, maybe most of the time. Anyway I have corrected the firewall port 80 setting. I am waiting now to see how things go.
I'm not sure what you mean about "server" mode, though. Can you elucidate a bit, please?
-Photonman
-
7000 is the last port attempted by the self-test.
i can't tell what's the problem there, but the 7000 is coming from this for sure.
maybe HFS can't write the new configuration because Vista is blocking it.
try running "as administrator".
Hi Rejetto
Your program is GREAT. It is Vista that stinks. :(
Yes, I see that when I do a self test it goes thru various ports looking for an open one, and ends on 7000. And you are probably right about Vista blocking the configuration. Everything I do on Vista requires me to click some permission button or run as admin. Arrrgh!
I recall now that I had an unspecific system problem that required me to run system restore. Thats probably how my port 80 got blocked again.
I think my main problem is solved (fingers crossed). I believe there is a way to make programs startup as administrative processes. If I have any further trouble I'll try that and report back.
Many thanks for all the help,
Photonman
-
yes, in the properties you should find an option to always run the program as administrator.