Ip blocking accounts

This person isn't hacking Xbox Live. He's using software on a PC to see what IP's he was connected to. Once he has the IP he can kick you off of the service using a ddos attack.

The only thing you can do is to disconnect your internet for a little bit and then reconnect so that you obtain a new IP (auto settings)

More info here.

The best way to report a person is via the xbox controls, have you done that yet? You can find out how to do that here. support.xbox.com/.../file-player-complaint.

Did you call your ISP about the issue as well, as they can help you stop it happening if he continues. I assume what they were doing was a denial of service attack, take a look at this FAQ if you haven't already support.xbox.com/.../dos-attacks-faq

I think you get attacked with a DDos

en.wikipedia.org/.../Denial-of-service_attack

If you get a new IP it should not happen again. If you go in a party with someone it´s easy to get your IP. If you get a new IP after 20 Minutes and don´t go in a party with your attacker he can´t know your new IP. Microsoft can´t do anything against it, because he floods your connection not over xbox live.

You should tell your ISP that you think that you got DDosed. Your ISP can see and block it ! Also I hope this kid get banned - and not only his gamertag but also his xbox in general !

[quote user="Xx ROZILLA xX"]

Also I hope this kid get banned - and not only his gamertag but also his xbox in general !

[quote user="BiggWhite01"]Im really sad and upset that me paying for live some child can hack thur my xbox just because I have a pulic ip address. I shouldnt have to worry about this when I play on live.[/quote]This has nothing to do with LIVE. Most online gaming applications today are based on Peer to Peer (P2P) communication which enables two clients to communicate directly to one or the others public endpoints (NAT's public IP addresses and public port numbers). These well-known servers will only help to establishing a UDP session between you two because initially, your NAT does not know how to communicate with another NAT on a private netowork and vice versa. When the server is done assisting an establishing UDP session a first UDP packet can be sent from both endpoints in a new outgoing session. When the first messages has crossed your respective NAT's, holes are now being open in each direction and UDP communication is done directly to your respective NAT's public endpoints.

I know this was posted 5 years ago but who cares. He must have DDoSed you. I bet XBLPET have taken care of him by now.

THANKS!