Print

[Orangey]

QUOTE (dzv @ Dec 24 2003, 05:58 PM)

Can somebody confirm that you can still get banned even without an Account?

I'm Fairly Sure You Can... From what I have read here over the months.

[dzv]

QUOTE (hellasei @ Jan 2 2004, 06:44 PM)

The simplest method is to use a static IP address for your Xbox Evox or whatever dashboard, to sign into to live you need to have it set to automatic otherwise it won't be able to logon. You can do the switch just prior to going live.....

This is not true.  I have my IP settings on manual, and I connect to Live without problem.  I think what you mean is to manually set your Network Settings to something incorrect (eg. enter an invalid Gateway address).  This would prevent Live from connecting.  But way too much screwing around for me, and it would also mean that with my modchip enabled, my Xbox wouldn't have proper network connectivity.  I like having full network acccess on my 'box without having to fiddle around with the settings all the time.

However, I still find the Memory Card to be the easiest, and I haven't been banned yet.  I'm even trying to 'intentionally accidentally' get banned, but I haven't managed it yet

brienj seems to confirm my theory in the thread about Live Aware games.

I'm still doing more testing.

[hellasei]

Yes, you could be right, my static IP address is 192.168.0.101. May be because it is over 100 that Xbox live doesn't like it??
When I use the chip enabled I connect to the net fine, when I diisable and go into the MS dashboard it says "cannot connect to Live" so I have to go into settings and change it to automatic.
It could be I just have the coolest router made i.e. the nexland isb soho and its acting as my guardian angel..........

[Hyper_Eye]

XBox Live does not care what your local IP is. It dosn't even know what it is. When you connect to an IP external to your local system all it sees is your external IP. I know a pretty good bit about the subject as I am a tech at Digium (creators of Asterisk - A open-source Linux application that serves as a PBX, VoIP, anything phone solution) and I deal with network setups day in and day out.

What I do to keep from getting banned is

1) Set my DNS settings to something invalid (in my case my DNS is 192.168.0.1 and I set my DNS to 10.10.10.10

2) Leave my CAT5 cable unplugged unless I need to ftp in or want to connect to Live.

[hellasei]

Here are my internet settings in Evox, try it out I bet you won't be able to log into Live.

IP address: 192.168.0.101
Subnet mask: 255.255.255.0
Gateway: 192.168.0.1

My $0.02....

[Hyper_Eye]

Well this is one thing I have noticed... if I set a static IP in evox but I dont set the same static IP on the router (in this case I don't set any static IP for the XBox at the moment) XBox Live has a problem connecting. When I set it to automatic it pulls a different IP and then it can connect. This has nothing to do with the IP being over 100 as my static assignments on my router are 65 - 70 and my DHCP pool is 71 - 80.

My theory on this is... since you set the IP static in evox the XBox never send a DHCPREQUEST to the router... thus the router never send a DHCPOFFER. So... the IP is not pulled from the router and the router has not assigned that IP to the XBox. That leaves that IP in the pool of available IP's on the router.

If you configured in any one of the following ways it would connect:

1) Configured the static IP at the router instead of in evox.

2) Configured the static IP in evox, took that IP out of the DHCP pool on the router, and configured the same static IP for the XBox on the router as you have configured on in evox.

3) Go dynamic... even if your pool is over 100 I guarantee it will connect.

[Hyper_Eye]

Well... it isn't 100% failsafe. If the last DHCP assigned IP you recieved (the IP you were given the last time you set yourself to automatic) is the same as your static IP and your DHCP lease on the router hasn't expired... as long as your DNS settings are correct (as yours are) it may very well connect. As matter of fact... I would bet on it. Solution to that... make sure your static IP is not a valid IP in your DHCP pool.

[dzv]

QUOTE (hellasei @ Jan 3 2004, 10:17 AM)

Here are my internet settings in Evox, try it out I bet you won't be able to log into Live. IP address: 192.168.0.101 Subnet mask: 255.255.255.0 Gateway: 192.168.0.1 My $0.02....

You're right, it won't work for me, because my router (gateway) is not 192.168.0.1

In your case, it's possible your router is not 192.168.0.1, which would be the reason why Xbox Live can't connect when trying that as the gateway.

Or... Perhaps your router IS 192.168.0.1  But what are your DNS servers configured to in EvoX?

[dzv]

QUOTE (Hyper_Eye @ Jan 3 2004, 11:19 AM)

Solution to that... make sure your static IP is not a valid IP in your DHCP pool.

Not quite true.  I can set my IP manually to any IP I want, as long as it is a valid IP on the correct subnet (in my case, 192.168.0.xxx).  I will still be able to connect to Xbox Live, because my gateway and DNS Server settings are set correctly.

[dzv]

QUOTE (Hyper_Eye @ Jan 3 2004, 10:29 AM)

My theory on this is... since you set the IP static in evox the XBox never send a DHCPREQUEST to the router... thus the router never send a DHCPOFFER. So... the IP is not pulled from the router and the router has not assigned that IP to the XBox. That leaves that IP in the pool of available IP's on the router. If you configured in any one of the following ways it would connect: 1) Configured the static IP at the router instead of in evox. 2) Configured the static IP in evox, took that IP out of the DHCP pool on the router, and configured the same static IP for the XBox on the router as you have configured on in evox.

It doesn't matter if you set an IP that is in your router's DHCP pool, outside the pool, part of the available IPs, one of the reserved IPs, over 100, or whatever.  If you set ANY valid IP in EvoX (that is not already used by another device), then your Xbox will be able to connect to Xbox Live, as long as the Gateway and DNS servers are set correctly.

[dzv]

 I will update on this over the next few days.


FYI, here are my WXYZ codes which I get while my modchip is ENABLED (Memory Card unplugged):

W: 0000 - 000B
X:  0000 - 000D
Y:  00A8 - 4800
Z:  0000 - 0000

I also checked my codes with the chip DISABLED, and they were exactly the same.

I hope I don't get banned over the next few days  

[Orangey]

[Hyper_Eye]

Well... I guess that is a difference with my router (www.smoothwall.org.) It will not allow a device to access the outside if it didn't assign the IP that device has (whether or statically or dynamically.)

[Hyper_Eye]

It is a very small Linux distrobution that runs on PC hardware... (mine is a Pentium 75, 32mb RAM, and two ne2000 ISA cards.) It uses a standard NAT procedure (One network card for external IP and one for local running DHCP.) It is actually quite similar to a standard household router in the way it works except it contains many more features then a standard router would and if you are Linux savvy it is much more customizeable. It has a very simple install and a nice web admin interface through secure http. From a home user perspective it is no different then a standard router minus the fact it is run on a computer and from a networking perspective it is a standard NAT.

It really begins to show its superiority when it comes to features, upgradeability, cost, and customizeability.

One of its excellent features is to have the ability to have three networks. One is the local, the other is the external, and one is a complete DMZ network seperated from your local. This, of course, requires three network cards.

Anyway... thats just a bit of info on the router and how it compares to a standard router in funcionality and operation.

[Orangey]