Please help me! I get temp banned from a server by mac adress bann. If i change my mac adress by tmac, or macmakeup, i get same error message:
Please help me to fix this problem!
Thank you!
Attachment removed, screenshot is fixed in thread.
I like to discourage threads about people getting banned. :3
Changing your MAC wont help you, nor changing IP..
And if you're too dumb to actually read what the error actually says then you shouldn't be playing anyways..
I have dinamic ip, i changed 100 times my ip, but i got MAC bann.
I'ill try today "halfgen" and "shadowx360". Thanks for your help. Please dont close this thread admin!
Originally Posted by sddhkl
I have dinamic ip, i changed 100 times my ip, but i got MAC bann.
I'ill try today "halfgen" and "shadowx360". Thanks for your help. Please dont close this thread admin!
Download the iw22_fix.zip there and extract + run the file inside of the archive. Then your problem will be fixed.
It's nice that not even the minions read what the error actually says is the problem and proceeds to just throw unban tutorial after unban tutorial over the poster even though that wont help..
It kinda says "WHY:"
WHY: #1: hamachi #2:Interface MS TCP Loopback interface
I wouldn't consider this an error, it's just an indication that the loopback interface is being used. A loopback is a communications channel with only one endpoint. Any message transmitted through such a channel is immediately received by the same channel. The loopback interface is used for some administrative purposes, diagnosis & troubleshooting, and as a virtual endpoint for certain communications.
In the case of the loopback interface, since it typically doesn't lead to any significant performance degradation, you can exclude the interface. To do this, you would open Diagnostic Server Administration, select the appropriate (or default) connection, choose the Network - Percentage Bandwidth alarm, and then "Override the default settings..." to "Add..." the MS TCP Loopback interface and then change or disable the alarm severities and notifications.
Spotlight's got a default threshold set for network interface saturation, just as it's got default thresholds set for all of the alarms in the product. The approach is of a general nature, meaning that when a DBA installs the product, we will alarm on anything that appears to be amiss and allow you to determine whether action should be taken. The Alarm editing capabilities have been designed to allow you to configure exceptions and/or specific actions down to the lowest level of granularity available to ensure that you can customize the product to work as your infrastructure requires. In some cases, like with the Days Since Last Backup alarm for example, there are clearly databases that should be ignored so we do that by default. When we start to delve into things like network configurations however, individual customer sites have unique implementations that make default exclusions inappropriate or dangerous, so we err on the side of caution in those cases and allow you to control how the product responds in your environment.
I hope that helps
Originally Posted by aIW|Convery
It's nice that not even the minions read what the error actually says is the problem and proceeds to just throw unban tutorial after unban tutorial over the poster even though that wont help..