QUOTE

If you are able to connect to the network when bypassing your router, you may need to configure your router to allow network communication on the specific ports required for Xbox Live. For Xbox Live to work correctly, the following ports need to be open: • UDP 88 • UDP 3074 • TCP 3074

So, block those ports.

shanafan...why would doing this be better than just unplugging the ethernet cord when you have the chip on?

QUOTE (thepro8 @ Nov 4 2003, 06:55 PM)

shanafan...why would doing this be better than just unplugging the ethernet cord when you have the chip on?

Then how can you play on X-Link or XBC?

(BTW, reason I made this topic is so my pinned topic can link to it)

And UDP 88 is just for kerberos authentication which won't ban you so you could just block tcp/udp 3074 and you'll never be banned. Though if you are behind a firewall, to get xblive to work, you'd need to open all three.

Thanks for noticing the other post I said this in shanafan

good point shana...I forgot about that. Ever since live i don't play on tunneling anymore.

Has anyone tried blocking those ports to prevent getting banned?

This is the perfect way to make sure that my brother or his friends don't get me banned by trying to connect to live while the modchip is on and i'm not around.

Malakai2k

QUOTE (Malakai2k @ Nov 9 2003, 11:06 PM)

Has anyone tried blocking those ports to prevent getting banned? This is the perfect way to make sure that my brother or his friends don't get me banned by trying to connect to live while the modchip is on and i'm not around. Malakai2k

Yes.. that is why I showed the ports to block..

can i block these ports through the network connections manager in XP ?

if your xbox is goin through your pc for its internet connection like ICS then that would work. but otherwise, no.

I have currently blocked UDP/TCP 3074 on my router. If I have my mod chip on and "somebody" accidentally chooses an XBOX Live option on a game CD, do I still run the risk of having my Evox Dash replaced with M$? I am trying to think of a fool proof way to make sure my dash doesn't get trashed... I have my young son playing on the XBOX and it is possible he or one of his friends could inadvertedly click on a XBL option in a game when I have the mod chip on...

success!

thanks

QUOTE (jfullam @ Nov 17 2003, 11:49 AM)

I have currently blocked UDP/TCP 3074 on my router. If I have my mod chip on and "somebody" accidentally chooses an XBOX Live option on a game CD, do I still run the risk of having my Evox Dash replaced with M$? I am trying to think of a fool proof way to make sure my dash doesn't get trashed... I have my young son playing on the XBOX and it is possible he or one of his friends could inadvertedly click on a XBL option in a game when I have the mod chip on...

Nope, you'll be fine, all you need blocked is TCP/UDP 3074 and you're xbox wont even be able to connect to live You dont need to bother with port 88, as i think you have already noticed and read the above post.

i brought this up a looooooooong time ago, shanafan

how do i block these through the XP network connections anyone? thanx for ur help in advance!

If you use ICS, get a software firewall and block the port.

The above post is for people with routers.

So blocking those ports Gaurantee me safe online gaming on XBCONNECT without getting Banned.

Just looking for your blessing, and ask if anyone else tried this. I tested it and it seemed to work, XBOX Live couldn't get past the blocked ports.

yeah im ganna try this out! wat software firewall u guys reccomend??

I have a router, and I gave my XBOX an IP address. I blocked the Ports specified, but I just wanna know who else tried this?

Each router has a manual that tells you how to block the ports, I just follow that.

ok tried this but when I go to the settings tab and to network setting and try to connect I still get the message conected to xbox life!... Apparently I'm doing something wrong, but I followed the instructions in the manual...

I have a Draytek Vigor 2200 usb router and set the IP Filter / Firewall Setup to:

Pass or Block: Block Immediately
Direction: OUT
Protocol: TCP/UDP
Source: the IP I entered manualy in the xbox
Destination: any
Subnet Mask: same as my pc which is connected to the same router
Operator: =
Start Port: 3074
End Port: 3074

what I''m I doing wrong?

QUOTE (AirrezzZ @ Nov 21 2003, 03:43 PM)

ok tried this but when I go to the settings tab and to network setting and try to connect I still get the message conected to xbox life!... Apparently I'm doing something wrong, but I followed the instructions in the manual... I have a Draytek Vigor 2200 usb router and set the IP Filter / Firewall Setup to: Pass or Block: Block Immediately Direction: OUT Protocol: TCP/UDP Source: the IP I entered manualy in the xbox Destination: any Subnet Mask: same as my pc which is connected to the same router Operator: = Start Port: 3074 End Port: 3074 what I''m I doing wrong?

I did exact same thing and I can still play live...

PLz i need help with this... And my manual to my routher is gone ... searched everywhere

anyone?

Any comments on how to block these ports in my router for ONE ip-adress (or MAC-adress) only? The manual for my alcatel speedtouch 510 v4 i router is waaay to complicated

My other virgin-xbox is used for x-box live purposes only...

QUOTE (scorpion303 @ Nov 25 2003, 03:01 PM)

Any comments on how to block these ports in my router for ONE ip-adress (or MAC-adress) only? The manual for my alcatel speedtouch 510 v4 i router is waaay to complicated My other virgin-xbox is used for x-box live purposes only...

If your other virgin-xbox is used for x-box live purposes only, then why do you care? The modded one will get banned if you accidentally log into Live with the modchip on, but you have a virgin-xbox for x-box live purposes only already!

plz I still need help.....

i'd try spanning the port range 1 in each direction to se if it's like a greater than compared to where most are greater than or equal to

and if the box gets banned it's just the box not the account so why would you care.

M$ did it for security reasons on the live network. not to piss of a person. they just don't want people with chipped boxes logging in and hacking

I want to take this a step further.

I want globally block 3074 UDP/TCP. Effectively disabling live.

Then I want to unblock it for 192.168.1.170.

If I manually configure the MSDash/Live to use 192.168.1.170.
And I manually configure my Evox Dash to use 192.168.1.175.

If I boot with the Modchip off. (ending up with *.170), then Live should work.

If I boot with the Modchip on. (ending up with *.175), then Live won't work.

Now my only question is, if I play a backup while the modchip is on, and try to access Live with it. Will it use the settings from Evox (175) or the settings from the MSDash (170)?

Conneen

QUOTE (jfullam @ Nov 17 2003, 06:49 AM)

I have currently blocked UDP/TCP 3074 on my router. If I have my mod chip on and "somebody" accidentally chooses an XBOX Live option on a game CD, do I still run the risk of having my Evox Dash replaced with M$? I am trying to think of a fool proof way to make sure my dash doesn't get trashed... I have my young son playing on the XBOX and it is possible he or one of his friends could inadvertedly click on a XBL option in a game when I have the mod chip on...

If u do in fact have an x2.2 pro like your tag says... just leave your original dash as xboxdash.xbe and name evox as evoxdash.xbe... your bios will try to boot from evoxdash.xbe first. Then any time Live! is chosen it can only modify xboxdash.xbe not your evox!

Probably not such a good idea to block port 88 globally, just in case you're one of those users whose mail server is elite enough to support Kerberos logins. Just a thought...

So give your Xbox an address, and then block exactly those three ports from exactly the one address.

The question I have on top of this is, what stops MS changing the port next month, and getting people banned all over the place?

(I'm actually tempted to block *everything* from the Xbox, and enable one service at a time where I need it, for things like live weather updates.)

If xbox is behind NAT router it prevents INCOMING connections except on the few opened ports and then only to the IP specified in the route. BUT any pc/xbox can initiate comms OUT of any ports. Is this xblive secure or not?

buy adding a passcode for security, would that help prevent on connection to live? or does it check after you connect?

why not block any traffic to their servers? It basically comes down to determining if they have a set ip range or and point to a dns name/pool.

i have (probably a stupid) question.
shanafan says to block ports
UDP 88
UDP 3074
TCP 3074

why shouldn't we also block
UDP 53

Because UDP 53 is used for DNS, and you might want that for other things

If I have 1 box with 2 hdds. One Softmod for FUN, the other retail for Live. I use static IP on both with different IP addresses. I would be safe just blocking the ports on the softmod IP right?

since there has been no confirmation of this method in this thread, i decided to test it partially, but since i did not desire to force a hacked xbox to connect to xbl not thoroughly... unfortunately, i may have gotten banned(99% positive) in my testing method anyways, but i will not know that until tomorrow.

the only thing that did not work for me with conneen's theory was that after several reboot tests, the retail dash network settings would very often accept the the hacked dash ip address - not sure why...

the only way to keep my retail dash from assuming the same manual ip from the hacked dash, was to set the retail dash network settings to dhcp. after this, i could block xbl access for my manually configured hacked dash ip by adding an access restriction rule to my router which allows the hacked dash ip internet access, but blocks udp/tcp 3074 port access specifically.

EDIT - after re-reading this, i realize it is not clear how i tested it. to test whether xbl access was blocked to a specifc ip, i tried connecting to xbl through the retail dash which was manually configured with the ip i wanted to block. once i had it blocked, i tested for internet access by launching my hacked dash and making sure i could still download a skin with the same manually configured ip and the xbl blocking rule enabled.

i have tested it several times over the last hour with as many reboot combinations as i can think of and it is still working for me.

if i receive the ban message due to this testing i have done so far, i will have an *expiring in 3 weeks* flagged gt to do some more tests and i have been wondering about the validity of the flagged gt *extra testing* theories anyways. however, if i do those tests, i will write a new post for it.

I thought I read somewhere on this forum that there was an edit to the EvoX config file to make sure that Live didn't connect? Or have I got this wrong?

I've just setup my entire network so that my XBox runs through my PC with internet connection sharing, and although I'm going to try to disconnect the network lead each time I'm not on Live without the chip, I'm worried I'll forget.

Any automatic solution to allow only Live with the chip off and allow everything except Live with the chip on would be a complete blessing!

Keep up the good work guys, I'll wait patiently for the perfect fix..

Hang on.. if we're all looking for a way to make sure we don't connect to Live when our modchips are on, why can't EvoX just be setup to hide the directory on the HD with all the gamertag information?

Surely if that was hidden to the Xbox, it couldn't connect to Live at all.. or am I just being dumb?

Uh.. anyone?

Still waiting..

the gamertag isnt in a directory, its in the HDs partition table

and evox cant do anything liek that, i dont think anything can except maybe that softmod with the virtual C (all it could do is hide your online dashbaord and have a virtual C with an older dash, of course any Live game can update that)

but seriously, why cant you just use a Live blocking bios like the rest of us?

Does one exist, and is guaranteed to work?

I asked around a while ago but was told it couldn't be done! I have an Aladdin Advance chip, I don't know if that makes any difference..

There is a lot of Live blocking bios (LBB) around mate... X2's, X3's, IND's, m8 metoo, etc, etc... just check around the ussual places, and read the readme's or howto's in the zips for full info.

Just to start you off, let me link you to my favorite and the one I use: IND-Bios

Enjoy your research mate.

From the IND-BiOS readme:

"All games should be patched with smo's patch to disable Xblive.
All MS dash .xbe's should be patched to block the network completely,
stopping dash updates which the first patch does not.
Please note that this last patch effects all .xbe's with the same titleID as the
MS dash. So if you are working on an MS dash mod (thc, blackstormx, etc), please
change your titleID if you are including any networking capabilities, such as FTP.
Thanks to smo for this patch info."

So Magnus, seeing as you use this one yourself, does this mean that I need to patch the games as well as using the BIOS? Because most of the games I use aren't backups, I have an Aladdin Advance chip on a 1.4 Xbox running eVoX - isn't there a BIOS I can install and block Live, simple as that?

Hope you're willing to help, thanks..

the live block int eh biso is like a seatbelt, the xbe patching is like the airbag, its just a secondary precaution

I installed having had help from this page:

http://forums.xbox-scene.com/lofiversion/i...hp/t319980.html

..and now it seems to work great! Obviously I'm still not going to try and connect to Live with the modchip on but I trust it'll protect me if I ever do that by accident.

Thanks all..