Print

[MikeF]

QUOTE (asktheaet @ Jun 3 2003, 09:12 AM)

I am running evox1.8.3752 off my HDD.  these are my settings under 'network': QUOTE Type IP     0.0.0.0 Line Status   100/full duplex Ethernet Mac Address   00:50:F2:22:CC:9B Setup Network   Yes Use Static IP  No IP    192.168.0.2 Subnet Mask   255.255.255.0 Default Gateway   192.168.0.1 DNS    0.0.0.0 DNS    0.0.0.0 Setup Delay   10 Skip Setup if no link   No Some facts to recap: 1 - I do not want a static IP.  I cant get a static IP to work anyhow. 2 - My PCs NIC is set to find IP automatically.   3 - I am connecting with a crossover cable direct PC - XBOX (no hub, router etc). 4 - It works fine when I boot from my cd-rw which has evox1.8.458 on it.

You can't get the staic IP to work becasue you need to configure your IP address on your NIC in your laptop to be in the same ip range and subnet.

Set your xbox static ip to YES

and your NIC's IP to 192.168.0.1 and subnet o 255.255.255.0 and try that.

[asktheaet]

I have already tried that several times without success.

[MikeF]

Are you sure that you are using a cross over cable to connect your pc to your xbox then.  If its a straight cable then it won't work.

[asktheaet]

100% sure its a crossover cable.  

it says crossover cable on it, and on the package it came in.  the wires cross over in the litlle diagram of the wires inside the cable.  its not regular straight LAN cable, though the connector is the same.

[asktheaet]

QUOTE

IP 0.0.0.0 100/Full Duplex Static IP 000.000.000.000 Default Gateway 000.000.000.000

About twenty seconds after I plug in the cable to my PC, it finds the IP automatically.  It is always 169.254.x.x (the last two are different every time i connect).  The screen at that time changes to:

QUOTE

IP 169.254.183.157 100/Full Duplex Static IP 000.000.000.000 Default Gateway 000.000.000.000

When I see this, I can type 169.254.183.157 into my FTP program on my PC and connect no problem (so long as my NIC card is set to find IP automatically.  If it is set to a static IP it won't connect, although interestingly evox will still find an IP beginning with 169.254.x.x not 192.168.0.3).

My PC can connect to the internet regardless of whether my NIC is set up to a static IP (ie. 192.168.0.2
) or to find one automatically.

Is it anything to do with those weird files such 'items.txt'  'settings_adoc.xip' etc mention earlier?

I am really concerned about this as I am waiting to put in my new 120gb HDD but I wont do it until I get my network settings 100% sorted out.

[mrRobinson]

QUOTE

when I see this, I can type 169.254.183.157 into my FTP program on my PC and connect no problem (so long as my NIC card is set to find IP automatically. If it is set to a static IP it won't connect, although interestingly evox will still find an IP beginning with 169.254.x.x not 192.168.0.3).

the 169.254 is not a real ip address. what i mean by that is it is the address given to the nic by your pc when it is set to automatically get an IP and it CAN'T.  it can't because you have no fuckin DHCP server when you crossover from your nic to your xbox!!  this has all been said to you already and your thickhead isn't remembering any of it.
Assign static ip to your nic and to your xbox (and SAVE it) and you will be able to connect fine.  YOU DON'T WANT AN AUTOMATIC IP WHEN CONNECTING WITH A CROSSOVER CABLE  can you possibly comprehend this at all?  


ps. i dont know the rules on this board and if i've said something that gets me kicked well it was worth it.

[asktheaet]

Chill dude.  If you feel frustrated imagine how I feel.

If you read what I had already said, you would see that I have tried what you are saying over and over again without success.  The only way I can get it to work is by using an automatic IP with the ancient version of evox run from cd-rw.

People just keep saying the same thing over and over again, even though I have said many times that I have tried the static IP way and it doesnt work.  You are trying to tell me that it cannot work using an automatic IP and crossover cable, but I know for a fact that it does work cos I have used it about 30 times already.

The problem is, why dos it work with my old version of evox, and not with the latest version installed on the HDD?  All the relevent info has been posted by me above with my ini file, network settings display etc etc.

[asktheaet]

OK maybe we are getting somewhere here.

I have NOT set a static IP for my NIC card.  Under the TCP/IP settings, it is listed as 'find an IP address automatically'.  But yet it connects ok with the cdrw old evox.

But this is the interesting bit:

1.  When it works, the xbox finds my PCs IP address.  It is always 192.168.x.x.

2.  When I look in zonealarm (which I always shutdown before I try to connect to the xbox by the way), it lists my buffalo network card as having an IP of 192.168.x.x

Thus, it seems that although I have set my NIC to find an IP automatically, there is some other force working here that makes my IP always 192.168.x.x.   I have RASPPPOE installed, maybe its something to do with that?

WHAT DO I DO NOW?  I THINK WE HAVE NEARLY SOLVED THIS, BUT IT JUST TAKES ONE MORE LITTLE STEP!!!  COME ON!!!

[mrRobinson]

QUOTE

even after i changed my PC's network settings so that it looked for the IP 192.168.0.3 it still didnt work.

You don't make your PC "look for" 192.168.0.3, if you set static to yes in the evox.ini and below that your xbox has 192.168.0.3 then on your pc nic you will want to give your pc a STATIC ip of 192.168.0.2
THEN in your ftp program you will try to connect to your xbox and try to connect to 192.168.0.3

Now since the nic in your pc is apparently at some point getting by DHCP an address of 192.168.x.x well then you have a router or cable modem, whatever that is also acting as a DHCP server for you.  No ISP can give you these addresses to get you onto the internet, they are internal addresses.  Now i could ask you more questions about your network but really it makes a rat's ass of a difference since with a crossover from your pc nic to your xbox none of the other stuff will come into play.

Why does it work from your old evox cd??? maybe that has static set right in it for the xbox and you aren't doing it right from the hard drive boot...  OR BIG ONE... do you have ftp set to yes in the evox.ini on your harddrive?? I haven't seen that mentioned here yet? It could be set to yes on the cd.

QUOTE

1. When it works, the xbox finds my PCs IP address. It is always 192.168.x.x. 2. When I look in zonealarm (which I always shutdown before I try to connect to the xbox by the way), it lists my buffalo network card as having an IP of 192.168.x.x Thus, it seems that although I have set my NIC to find an IP automatically, there is some other force working here that makes my IP always 192.168.x.x. I have RASPPPOE installed, maybe its something to do with that?

1.  How does the xbox find your PCs IP address???  this is like when you said you changed your PCs IP to "look for" your xbox... if you see an IP address on your xbox that is your xbox ip address, not your xbox "finding" your PC.  I just want to make sure you understand that.

2. OK... well your RASPPPOE could be doing something funny.  if your nic has the 192.168.x.x then either its getting it from DHCP, which means its not crossover connected to the xbox, or it the static you assigned to the nic so it better be 192.168.0.2, if not you didn't or haven't set the static right and maybe this is something the RASPPPOE is preventing.


So that's it. take it from there... i've done all i could.  This will be my last post in this thread for health reasons.

[asktheaet]

QUOTE

You don't make your PC "look for" 192.168.0.3, if you set static to yes in the evox.ini and below that your xbox has 192.168.0.3 then on your pc nic you will want to give your pc a STATIC ip of 192.168.0.2 THEN in your ftp program you will try to connect to your xbox and try to connect to 192.168.0.3

Yeah 'look for' was my bad use of language.  I understand now that the ftp program 'looks for' (tries to contact) x.x.x.x and the NIC and xbox IP settings are 'made to be' x.x.x.x.  Anyway, I tried the above many times and it didnt work.

I dont have a router. Maybe I have a cable modem, I dont know.  I connect to ADSL using a regular LAN cable and an ADSL modem.  But the modem isnt connected yo my PC when I connect to my xbox, as I only have one NIC.

People saying that it 'cannot' work with my NIC set to find an automatic IP, but I am telling you that is the only way it has worked in the past.  And every time the IP has come up as 192.168.x.x (just like my adapter is listed in zonealarm) on my xbox and I just typed that into my FTP program.

QUOTE

do you have ftp set to yes in the evox.ini on your harddrive?

Yes definitely.

In zonealarm, my NIC is said to be an IP of 192.168.2.x
So, should I change the IP setting in evox 'menu.ini' to be 192.168.2.2?

Interestlingly, I noticed my PC will connect to the internet regardless of whether I set it to find an automatic IP, or as 192.168.0.3

Come on Mrs Robinson, come out of retirement and help me!  Oh, and your icon looks like Winnie The Poohs evil twin sister touching herself in parts she shouldn't...

[asktheaet]

new development!!!

I connected my xbox via crossover cable, and left Zonealarm on this time.  It discovered the new network device (the xbox) and listed its IP as 169.254.0.0.  I then made that a 'trusted' zone.  What should I do now to connect?

[asktheaet]

 

I did two things.  First I changed zonealarm so it doesnt even load on startup, and then rebooted.  Next, I changed the default gateway settings in my menu.ini file from 192.168.0.1 to 0.0.0.0   THEN IT WORKED!!!

THANKS TO ALL WHO PUT TIME IN TO HELP ME OUT!!!

[MikeF]

Glad to see that you finally got it working.  To be honest if Zonealram is configured correctly it will still work with it enables like it does for me.

[asktheaet]