rekrul

I think it's either in the server.log file or the .rpt file. It should say something along the lines of Spawing ATV..... Spawning UH-1H etc. It might include coords as well, I'm no admin so I wouldn't know but check the Server section under Support.

Oh yeah I forgot to add an important point. :) The reason for these very variable IP rules are due to legacy. Old telcos who previously offered dial-ups and/or pppoe/oa on xDSL tend to rotate more often than newer who had to build up their network from ground the last 10 years. The new ones don't have the legacy support systems that were made to rotate IPs as they don't come from that era nor had any need for it. Usually the old telcos would have many more customers than actual IPs and/or they needed to authenticate the customer for billing purposes. (They still offered static IPs but they were rarely needed.)

Wow, you all agree that IP-banning is pissing in the wind but yet you argue over semantics... As you all know, the IP the customer receives is very rarely static in the CPE. Even when static, the CPE usually receives the IP from a DHCP server. Now strictly technically speaking this means that the IP is dynamic, even though it's receiving the same IP every time, however I'm sure it's sold and marketed as static and if the customer choose to - he can probably set the static IP on the CPE. Now to clarify something when it comes to dynamic IPs, it's always the DHCP server which decides what happens. When the DHCP server hands out an IP it also tells how long it is valid, called the lease time. Once the CPE has had the IP for half the lease time, it will send a DHCP Request packet with the existing IP asking to keep the IP. The DHCP server will decide, based on its configuration, whether this is ok (sends DHCP ACK) or not (DHCP NAK). If not, the CPE will send an DHCP Discover and the server will send an DHCP OFFER. (Some servers might send an DHCP OFFER immediately after the DHCP NAK.) So we all agree that the DHCP server decides everything from how often the CPE asks (except for a reboot/disconnect which triggers a DISCOVER/Request on non-static IP CPEs) and how long it's allowed to keep the ip, right? Right. So now to what's common when it comes to keeping the IP, how often it changes, etc and here's the gist - there is no standard behavior! For every ISP you have slight variations. Some ISPs change every 24 hrs or less, but it's far from common since it will leave a lot of TCP connections hanging. Some ISPs never change except for when they're reordering the IP pools, some change every time there's a discover. Inherently the DHCP server was never meant to juggle IPs to make sure a customer never receives its previous IP. The DHCP server and the RFC are doing everything it can to make sure that customer keeps the IP it had. The ISP I work for (one of Norway's largest) has a 6 hour lease time but never rotates IP or pools, but we're free to do so as we don't charge for it. The ILEC (telenor) rotates every time there's a DHCP Discover. The ISP I'm using at home (cable) is roting IP anywhere from 2 -12 weeks. For our corporate customers who pays for a static IP, we assign them a /30 net where they can either set a static IP themselves or request on from our DHCP server. Our router will add an DHCP Helper IP on the other /30 IP leaving the DHCP server with only one possible IP to hand out. However with all the Data Retention Directive from EU (and probably some patriot act in the US) and other legislative actions and regulations the ISP are responsible for knowing which customer had what IP at any given time which is making more and more ISPs reducing IP rotations to minimize logging and gain better control. Some already had this and probably won't change, while others might restructure their IP pool policies. So while there is no "standard" behavior amongst the ISP, even within the same country, let alone in the same region, it is moving more towards "static dhcp" rather than "rotate every 24hrs or less".

Items will never get you globally banned. BE bans on two conditions from what I know (they obviously don't inform of what they check or how they ban) - one is trying to circumvent BE with cheatengine or similar, and secondly manipulating memory and injecting stuff either directly into memory or the BE-protected process. Also, BE doesn't immediately ban when you hack. It can go anywhere from hours to days. Also they are constantly evolving catching more and more hacks and newer and newer versions. I find it incredible suspicious that this happens now, a couple of days after a new BE version was released. Personally I think you got caught by the new BE update but if you are innocent, go here: http://www.battleye.com/support.html Read the instructions carefully and follow it to the letter. If you are innocent, they will get back to you and lift your ban. If you don't follow their instructions, they won't check. If you follow the instructions, they check. If they see you were caught hacking they won't bother to reply. If you're innocent they will reply and lift the ban. Good luck.

The ban is an admin ban, meaning the server admin banned you, not BE. I don't know how Steam works but it seems like Steam is still using your old key.

Sticky: http://dayzmod.com/forum/index.php?/topic/97180-the-complete-thread-about-serialcd-key-problems/

You only need the OA key. BE only ignored you if you didn't follow the rules for contacting them, as stated on their website. If you followed them, they check - but if it's a legitimate ban, you won't get an answer.

Why don't you just use Play withSix and select OA as the "mod" and launch it from there? I don't have Steam and have a desktop icon with OA (and another for A2) so I can't really relate.

Dude! Punctuation - use it.

It was running 1.184 when I played 9 hours ago and I didn't experience any of these problems but I jumped from 1.17x something. Anyways, seems as BE has been quite good a plugging security holes lately. Funny how people are outraged because BE doesn't do anything about hackers and then when you get weekly updates the players freak out even more. Yes I see the frustration of obvious bugs in their rollout, but they are fixing it quite fast. And there's not a lot of hacks left as far as I can tell. Seems like most of them are unable to spawn shit now and they're left with teleporting and HUDs.

Did you try contacting BIS? Although it's your responsibility they might offer a hand if you reported it as soon as you realized your mistake. If you're really lucky, that's why they banned it but I doubt it since it happened in a weekend. And in your defense, you didn't DL a hack but a fix for a problem and you could link to this thread as well.

Jesus guys, show some courtesy. For gog, it seems to install a default key that is banned if the installation wasn't followed correctly. There are probably some steps in the installation process you didn't follow. First of, uninstall Dayz and SixLauncher. Then re-read the installation instructions from GOG. Also remember that you need both a serial and cd-key. Then try to join an Arma2:OA server. If that works fine, DL Dayz commander and use that to install Dayz and try again. DL only from official sites. If someone offers you a "fix" be very wary as there are a lot of cd-key stealers out there. I would strongly advise against running files received in a PM. If it is an official fix you'll find it on official sites.

It almost seems as you claim that the hacker ported you to a different server... I'd guess that the hacker sent you off-map and you're now in the debug-plains. Try connecting to a different server and if that doesn't help, try to die.

I would recommend contacting BIS immediately and report what happened. BIS' instructions; Details of where you purchased the game from The installation method included with this purchase (DVD/Digital etc) Photo or screenshot of the key (if applicable) Photo or screenshot of the receipt IP address from www.whatismyip.com To send screenshots you'll need to email directly to [email protected] instead of using the webmail option. --- Sorry to say, but you just lost your CD-key if you ran that on the PC where you have Arma2/Dayz installed.

If you mean you want an icon showing yourself when looking at the ingame map, set difficulty to Recruit on the server. I believe this will show other players in vicinity on the map too though. At least it does in A2/OA, they might have stripped it in Dayz.

http://dayzmod.com/forum/index.php?/topic/97180-the-complete-thread-about-serialcd-key-problems/

This usually happens when the server kicks you since BE isn't replying while you're loading and the client never realize that it has been kicked.One more thing. I had this happen to me again last night, after I had downloaded something with uTorrent. I have a cap on connections set to 200 in uTorrent, but checking my router I had 1600 connections. I quit uTorrent, waited a couple of minutes until it was halved and tried again with no problems which is a bit weird since the router should have no trouble handling 2000 connections per host. It might have been random or it might not. :) Anyways, if you have torrent running on any PC in your network, try closing it down.

This might have been mentioned already, but I didn't feel like reading through 4 pages of "alpha" and off-topic chit chat, but OP is right. However, Rocket himself said that this stage of the game, let's call it "birth", was only meant to be one, maybe two days of gameplay in his scheme. As in, getting to know the game and he was surprised at the attention and amount of play it received. He's also stated several times that the zombies are not scary now (I think he classified them as 2 while he wants 7 - 8) so basically. All in all we can't really base a lot of the Dayz gameplay on what we've seen so far as this was only supposed to be a tiny part of it. We have gotten introduced to framework of Dayz which I think most people are happy with, apart from the hackers, what most people are complaining about now is content. And we haven't really seen any. For a game with basically no content, we sure have had hours of fun.

When you tried reconnecting, did you replace the dll first? You might have a two-headed troll on your hand. My old "replace dll everytime" and a router with limited simultaneous connections. A couple of additional things - are you running any torrent software on any of the PCs in your network? Are you running wireless or cable? If wireless can you try cable? If cable can you try to update the driver?

I hope you read that page carefully.

I always had my commander running - shouldn't matter. One thing though, if you refresh all the servers in commander while connecting, there might be a problem. You see, Commander uses UDP which is stateless (unlike TCP which establishes a connection/session and ends it after it's done) so for every server that commander checks (about 5200 on mine) it takes up an entry in the NAT-table (translating from your 192.168.1.x/10.x.x.x IP to an internet IP) and this is handled in router's memory. So if you have an old/cheap router with not a lot of memory, the router can only handle a fixed amount of connections at the time. Now usually the router will either overwrite an existing entry in the NAT-table or it might just drop the packets (preferably overwriting). This usually shouldn't impact BE which runs TCP (I believe, haven't checked) but some routers might overwrite TCP sessions with new UDP packets, it depends on your router. If it drops packets it probably drops both UDP and TCP unless the TCP is an established connection.In short, it's not likely to be the root of your problem but it might. The workaround is to wait 1-3 minutes (maybe even 5 if you're really unlucky and/or have some weird ass router) after Commander is done refreshing servers before connecting. That means that regardless of the behavior of the router (overwrite/drop) it should handle new connections at that time. If this is the problem you shouldn't be able to connect to a server every time and then luck out on the BE session when it is as consistently as you describe so it's not likely to be the problem but give it a try. Commander doesn't auto-refresh (except for maybe the one server you clicked on) so you can leave it running. It has nothing to do with BE, only the game pokes around with BE. Once the game is running (e.g. you're in the main menu) the game doesn't care how it's launched and BE certainly doesn't care). Hope my explanation was clear enough, if not - just ask.

Well for me it didn't matter if I did it before Dayz commander started dayz or before I connected. My issue seemed to be that once BE had initialized, it couldn't be "re-used" on another server. So before I joined the other server I had to copy the dll again. It doesn't make any sense, but it worked. And I'm on a 70/10 Mbps line with a router capable of routing 800Mbps with NAT and firewall enabled so that isn't (wasn't) the problem.

I should add that my problems with not responding always happened when joining. Once I survived the first minute, I could play for hours on the same server.

Known bug/error. http://forums.bistudio.com/showthread.php?135736-Bad-serial-number-given-in-setup-use-this-thread-for-help

I had the same problem. My solution was to download the dll to desktop, then before I connect to any server I copied the dll file to the OA/Expansion/BattlEye folder. This gave me a success rate of 9/10, but I had to do it before connecting to any server, meaning if I jumped out of one server with Dayz still open, I couldn't connect to a new server before I copied the file. If I didn't, I had a success rate of 1/10. It sounds weird, I know, because they never write to the file. Anyways, since 1.171-ish came I haven't had this problem anymore. One annoying thing, which is BIS' fault, is that every time I update A2 with a new beta, I always get an old BE-client which has to be updated. Previously this has been successful once out of maybe 20 tries. This time it went without a glitch so I'm suspecting that BE has updated their router's firmware. ;)