...doesn't seem to work tonight. Can test the passsword and get the green OK sign but cannot get a log from the server. Anyone else try it and getting the same?
Worked fine for me.
Just tested it again and its still working.
We'll try to get the ports back open asap as I think they were shut down last night in the excitement of getting the gaming bit working.......
7130-7135 should do it. G-man, you around?
TL.
That was fast - working again :)
I notice that for the last few days I have been unable to get the chat windows to work in HLSW. Basically when you try to get the logs it fails with a timeout although you can send RCON commands and see the response in the console window.
Can somebody else please test to see if it works for them?
Cheers :D
Its looking all sexy for me :D
I keep getting log timeouts :(
I have been on it for a while havng a poke .....try it now ......i think only 1 admin type person can use it ....
then again if its borked on em all ?
Nope, nothing :(
Works fine for me on all servers.
Not working for me either. :(
Tried forwarding ports and issuing logaddress command but still nowt.
QuoteOriginally posted by OldBloke@Dec 10 2004, 01:36 PM
Not working for me either. :(
Tried forwarding ports and issuing logaddress command but still nowt.
[post=71523]Quoted post[/post]
[/b]
That's a relief! it's not just me then :)
I notice in the "console" page that when you try to get a log it initially tries port 7130 but then flips over to some other randomly chosen port.
OB are you behind a NAT router or anything? I know I am and I'm not sure if NAT is screwing up.
Logs don't work for me either, but as mentioned above it shows in the console log!
TL.
OK Here is what I get in console when I try to get logs:
11:09:21 HLSW NOTE: Connecting to 82.197.65.246:27019 ...
11:09:21 logaddress_add "82.41.79.247:7130"
11:09:21 decalfrequency 7130
11:09:21 server_cvar: "decalfrequency" "7130"
11:09:21 logaddress_del "82.41.79.247:7130"
11:09:22 logaddress_add "82.41.79.247:14159"
11:09:22 decalfrequency 7131
11:09:22 server_cvar: "decalfrequency" "7131"
11:09:22 logaddress_del "82.41.79.247:14159"
11:09:22 decalfrequency 60
11:09:22 server_cvar: "decalfrequency" "60"
I have even tried port forwarding 7130 to my LAN IP but that gives same result. I guess either my router/firewall or the one at HiVelocity is "playing" with port numbers.
Questions:
Is someone at HV looking at this for us just now?
If not what can we do to try and resolve it?
It's really getting on my tits ;)
Cheers :D
It doesn't appear to be anything to do with NAT, or at least not for me. I have NAT with no port forwarding and I can use rcon on all the servers with no problem, including writing logs to text files etc.
What version of HLSW is everyone using?
I'm on 1.0.0.38 (I've tried 37 and 36 both of which used to work but they do not work now)
Version 36 ...it all works apart from the logs on HL2/CSS server
36 And rcon log doesn't work on CS:S though
QuoteOriginally posted by BlueBall@Dec 12 2004, 04:28 PM
What version of HLSW is everyone using?
I'm on 1.0.0.38 (I've tried 37 and 36 both of which used to work but they do not work now)
[post=71683]Quoted post[/post]
[/b]
1.0.0.38?
According to HLSW homepage 1.0.0.36 is the latest. :eyebrow:
http://www.hlsw.net/index.php?url=hlsw_download (http://www.hlsw.net/index.php?url=hlsw_download)
See my post here for where to get 1.0.0.38 from. (http://forum.deadmen.co.uk/index.php?showtopic=8170)
I've been doing some digging and 38 seems to be part of the problem (that and a recent Steam update).
If you dont have 38 then I suggest don't get it yet - wait for a patch
I have .36 and still have the problem.
TL.
Must be more the Steam update than HLSW then. Most of the posts regarding the problem refer to a recent steam update that changed the way logaddress is handled (don't you just love Valve)
Relevant Post on HLSW Forum (http://www.hlsw.net/phpBB2/viewtopic.php?p=13258#13258)
I've seen a few posts mention that restarting the servers might clear the RCON issue through HLSW that appeared recently. Might be worth doing before the competition - it can't hurt can it :)
Running .39 and it still doesn't work.
TL.
The posts seem to indicate that it is a Steam issue more than HLSW. They suggesterd that restarting servers would fix it- dunno but worth a try :D
Servers have been restarted several times since then.
TL.
:(
I still have no problems rconing onto any of our servers with HLSW and am running version .39
Sorry.
QuoteOriginally posted by Gh0st Face Killah@Dec 23 2004, 01:54 PM
I still have no problems rconing onto any of our servers with HLSW and am running version .39
Sorry.
[post=72918]Quoted post[/post]
[/b]
Can you get the logs?
TL.
Yes I can. Everything works as it should.
See here (http://www.hlsw.net/phpBB2/viewtopic.php?t=3704) for latest info from HLSW site. Do we have "log on" set on servers?
QuoteOriginally posted by BlueBall@Jan 9 2005, 02:01 AM
See here (http://www.hlsw.net/phpBB2/viewtopic.php?t=3704) for latest info from HLSW site. Do we have "log on" set on servers?
[post=74231]Quoted post[/post]
[/b]
That's a Source only solution so it does not explain why some peeps can use HLSW fully on CS and CZ and others cannot whilst using the same version of HLSW.
TL.
Mine started working yesterday :huh:
QuoteOriginally posted by OldBloke@Jan 9 2005, 10:43 AM
Mine started working yesterday :huh:
[post=74253]Quoted post[/post]
[/b]
Mine didn't :(
Given that Hi-V are making network changes and your HLSW started working suddenly I'm starting to think that part of the problem lies at Hi-V's end whether it be NAT, Firewall, Port Re-Direction or whatever.
If that were the case surely it would affect everyone using HLSW?
QuoteOriginally posted by Gh0st Face Killah@Jan 9 2005, 11:54 AM
If that were the case surely it would affect everyone using HLSW?
[post=74275]Quoted post[/post]
[/b]
Not necessarily. Are we all getting into Hi-V over the same route? Maybe there is some strange and complex interaction between the NAT router I am behind and whatever is being used by Hi-V? It's all very weird and we don't really have any answers :(
Possible culprits:
Steam
HLSW
Hi-V
My Router
WinXP
All of the above?
QuoteOriginally posted by BlueBall@Jan 9 2005, 12:05 PM
Not necessarily. Are we all getting into Hi-V over the same route? Maybe there is some strange and complex interaction between the NAT router I am behind and whatever is being used by Hi-V? It's all very weird and we don't really have any answers :(
Possible culprits:
Steam
HLSW
Hi-V
My Router
WinXP
All of the above?
[post=74277]Quoted post[/post]
[/b]
Mine was buggered whilst I was still on Zen, so that rules out Hi-V unless both Hi-V and Zen do the same thing - which would mean an HLSW problem as they clearly do not understand the way that the internet works.
TL.
QuoteOriginally posted by TeaLeaf@Jan 9 2005, 05:20 PM
Mine was buggered whilst I was still on Zen, so that rules out Hi-V unless both Hi-V and Zen do the same thing - which would mean an HLSW problem as they clearly do not understand the way that the internet works.
TL.
[post=74316]Quoted post[/post]
[/b]
Yes, you were still on Zen but wasn't it after the server was moved to Hi-V that this started? I'm not wanting to blame Hi-V but for me all this started after the server move. before that HLSW was spot on.
QuoteOriginally posted by BlueBall@Jan 9 2005, 05:24 PM
Yes, you were still on Zen but wasn't it after the server was moved to Hi-V that this started? I'm not wanting to blame Hi-V but for me all this started after the server move. before that HLSW was spot on.
[post=74317]Quoted post[/post]
[/b]
Nope. It was buggered when it was back at Crosswired/MWI.
TL.
Not for me. The CS:S logs didn't work on Crosswired but that was an HLSW issue not a Crosswired issue. The first post in this thread was made after the servers moved to Hi-V.
Remember though that lots happened about the same time - HLSW update, Steam update, server move and thats why it is tricky to pin down what caused it. All i can say is that for me it started post server move, that doesn't mean server move caused it ;)
It had been an issue for a while before that afaiaa.
TL.