Print

[snivlem]

Is your firewall off?  Make sure it is.  That's all I can think of now.

[kickassdude]

i dont have a firewall installed

[SS113]

QUOTE (kickassdude @ Jan 15 2003, 11:15 PM)

hi i am having some problems ftping into my xbox, at first i thought i had a bad cable but now im sortof able to connect but i get disconected in flashfxp it starts to connect and sometimes connects and either when it says Connected to 192.168.0.2 Port 21 or 220 Please enter your login name now. USER xbox Connection failed (Connection timed out) is when i get timed out & disconected heres the log file from flash fxp Connecting to 192.168.0.2 Connection failed (Connection timed out) Delaying for 120 seconds before reconnect attempt #1 Connecting to 192.168.0.2 #1 Connection failed (Connection timed out) Delaying for 120 seconds before reconnect attempt #2 Retry attempt Aborted Connecting to 192.168.0.2 Connected to 192.168.0.2 Port 21 Connection failed (Connection timed out) Delaying for 30 seconds before reconnect attempt #1 Connecting to 192.168.0.2 #1 Connected to 192.168.0.2 Port 21 Connection failed (Connection timed out) Delaying for 30 seconds before reconnect attempt #2 Connecting to 192.168.0.2 #2 Connection failed (Connection timed out) Delaying for 30 seconds before reconnect attempt #3 Connecting to 192.168.0.2 #3 Connected to 192.168.0.2 Port 21 220 Please enter your login name now. USER xbox Connection failed (Connection timed out) Delaying for 30 seconds before reconnect attempt #4 Connecting to 192.168.0.2 #4 Connection failed (Connection timed out) Delaying for 30 seconds before reconnect attempt #5 Connecting to 192.168.0.2 #5 Connected to 192.168.0.2 Port 21 Connection failed (Connection timed out) im pretty sure i have the evox ini right or else it wouldnt get this far ive also tried pinging my xbox and it ussually just recieves 1 ping out of 4 if enybody knows how to help me, please im really stuck here

List what your IP settings are for the Computer and the Xbox. and Gateways

SS113

[SS113]

QUOTE (kickassdude @ Jan 16 2003, 12:40 AM)

my xbox ip is 192.268.0.2 gateway is  192.168.0.1 on my pc th ip is 192.168.0.1 and i set the gateway on my pc to 192.168.0.2 (i know i should leave it blank but without this it wont even ping the xbox successfuly) both subnetmasks are 255.255.255.0

gateway in both the computer and the Xbox need to be the same or they will not respond to the right address.

computer
192.168.0.1--------IP
192.168.0.1--------Gateway

XBOX
192.168.0.2--------IP
192.168.0.1--------GATEWAY

SS113

[kickassdude]

nope doesnt work. now i cant even get as far as
Connected to 192.168.0.2 Port 21
and cant ping xbox either

[SS113]

QUOTE (kickassdude @ Jan 16 2003, 01:08 AM)

nope doesnt work. now i cant even get as far as Connected to 192.168.0.2 Port 21 and cant ping xbox either

You did restart the computer and the Xbox after any changes right?
SS113

[SS113]

QUOTE (kickassdude @ Jan 16 2003, 01:46 AM)

not the comp, is it important? i did the xbox it didnt seem to be when i was changing my ip and then i could actually ping my xbox i have winxp <= any difference? its  just that i have a nasty bug in my system that keeps rebooting it after powerup, it takes half an hour of rebooting & scandisks to get my system stable and after that i leave it on, its been on for over a month is this absolutely neccesary? i really dont want to spend half an hour fixing my system edit: ahh to hell with it ill try rebooting neway

Well you had me a little concerned when you said it didn't work!
so to be sure I did not give you wrong information I shut down one of my networked computers and hooked up to the Xbox with a CrossOver Cable
First My IP was 192.168.0.121 and Gateway was 192.168.0.1 and I had no problem logging into the xbox. so I went back to the nic card and changed it all around to read
192.168.0.1----IP
192.168.0.1----Gateway
255.255.255.0 SUB.

And I left the Xbox at 192.168.0.92 it is set to static YES in the INI file. Does not matter if you look to see what the address is before trying to access the Xbox, just look on the dash if it is listed there if not go into system managment and check what it shows for IP address and Gateway and be sure nothing has changed or is what you think it is anyway.

So after my changes to a crossover cable with orignial settings and with the one's listed above I had no trouble accessing the Xbox.
Now I feel better that I did give you correct info. and by the way sorry for you having to restart the computer I did not know you had XP at most you only had to log out and back in. I use XP and there was no problems again sorry for the restart.

SS113

[kickassdude]

oh well no luck here, i think ill call it a night
neway thanks for trying to help SS113

[SS113]

QUOTE (kickassdude @ Jan 16 2003, 04:40 AM)

oh well no luck here, i think ill call it a night neway thanks for trying to help SS113

I would look at trying a differant CrossOver cable looks like the addresses are no longer an issue here and it is a problem with comunication and that it is being broken because of a bad cable or even a bad cable end.
if you use a strait through cable you will get nothing, data lines are in the wrong place in the connectors. next time you try to connect look at the lights on the network cards both should have bright green steady lights and either an amber or green light that blinks as data moves, if at anytime the one that is on steady blinks or goes out for a second there is a cable or hardware problem.

A good connection looks like this:

Connecting to 192.168.0.92:21
Connected to 192.168.0.92:21 in 0.080, Waiting for Server Response
220 Please enter your login name now.
Host type (1): Automatic detect
USER xbox
331 Password required for xbox.
PASS (hidden)
230 User xbox logged in , proceed.
SYST
215 UNIX Type: L8
Host type (2): UNIX (standard)
Host type (I): UNIX (standard)
PWD
257 "/" is current directory
PORT 192,168,0,120,8,141
200 Port command ok.
LIST
150 Opening ASCII data connection for ls /.
transferred 385 bytes in < 0.001 seconds, 3007.813 Kbps ( 375.977 KBps).


SS113

[gurbao]

I also have all kinds of problems with getting ftp to work.

Here is what I have:
- brand new xbox chipped with matrix (flashed with d6)

I use a crossover as I haven't got a network.
As the PC and the TV are on different floors I can't see the dash when I trying to hook them up together.

I boot with Slayer's tool v2.0 (modified to StaticIP = Yes),  and have verified that it boots ok. As I verfied the booting on my TV (no network) I didn't get a IP assigned (the IP field on the dash was empty).

The xbox IP: 192.168.1.20
Mask             255.255.255.0
Gateway       192.168.1.1

The PC IP:    192.168.1.21  (tried different, including .1.1
Mask             255.255.255.0
Gateway       192.168.1.1

My question is
With the StaticIP = Yes in the evox.ini, I guess the IP the xbox get when booting should be the one in the evox.ini? Or could it be assigned another IP somehow? Do I need to buy a long crossover to verify the xbox IP?

When I change the PC nic's settings, reboots the pc, boot the xbox with these settings I can't even ping my xbox!?

I guess I should try another cable to be sure, but as a long as a thrustworthy friend says it's ok, I don't think that will help. I don't want to spend 30$ on a new cable (need 20 meters (>60 feet)).

Anyone with a clue here?

[SS113]

QUOTE

I also have all kinds of problems with getting ftp to work. Here is what I have: - brand new xbox chipped with matrix (flashed with d6) I use a crossover as I haven't got a network. As the PC and the TV are on different floors I can't see the dash when I trying to hook them up together..

I dont understand how you are using a crossover cable unless you have a looong cable going from upstairs to downstairs? either way you only need to look at the evox screen to see what the IP address is then go to the computer and using that address in the ftp to reach it. Nothing changes on the evox screen when you are FTPing into it.

QUOTE

I boot with Slayer's tool v2.0 (modified to StaticIP = Yes), and have verified that it boots ok. As I verfied the booting on my TV (no network) I didn't get a IP assigned (the IP field on the dash was empty).

This is because it does not see ang network or other computers in its address range or the cable is unpluged.

QUOTE

The xbox IP: 192.168.1.20 Mask 255.255.255.0 Gateway 192.168.1.1 The PC IP: 192.168.1.21 (tried different, including .1.1 Mask 255.255.255.0 Gateway 192.168.1.1

this should work fine even an un changed install disk would work, The setting for static yes/no is if set to yes then this is the only address it can use, if set to no then if the address in the INI file is already in use it will aquire a differant one if the network uses DCHP

QUOTE

My question is With the StaticIP = Yes in the evox.ini, I guess the IP the xbox get when booting should be the one in the evox.ini? Or could it be assigned another IP somehow? Do I need to buy a long crossover to verify the xbox IP?

the address of the ini file when set to static is the address the xbox will have to use if it see's a network.

QUOTE

When I change the PC nic's settings, reboots the pc, boot the xbox with these settings I can't even ping my xbox!?

still dont understand how you cant look at the TV then go to the computer and run the ftp with the address on the evox screen

QUOTE

I guess I should try another cable to be sure, but as a long as a thrustworthy friend says it's ok, I don't think that will help. I don't want to spend 30$ on a new cable (need 20 meters (>60 feet)). Anyone with a clue here?

Hmmmm.

[kickassdude]

at first i thought it was a bad cable, because i made it myself out of a straight through network cable, i just opened it up and crossed the wires that needed it but
neway the first time i tried i couldnt get a connection but after i changed the default gateway on my pc i could ping the xbox and my pc recognized it as a lan connection so i assumed the cable was good, could it be bad cable even though i can occasionaly ping the xbox?
btw how many pings out of 4 go through for you, i only get 1/4

[shamelessbill]

Are you sure your crossover is correct? Its not just opposite. Do a search on google for proper wiring diagram. I messed w/it 4 2 days then gave it to the IT guy at work and alls good since then.
SB

[kickassdude]

obviously i didnt just cross random wires, i saw i guide for which wires need crossing
the only thing i could think of is that i fucked it up while soldering

[SS113]

QUOTE (kickassdude @ Jan 16 2003, 11:32 PM)

obviously i didnt just cross random wires, i saw i guide for which wires need crossing the only thing i could think of is that i fucked it up while soldering

The cat5 cable is a twisted pair cable and when making the RJ45 connection you should only un twist just enough wire to make the connection to the plug, un twisting will cause data errors. Personaly I would get a crossover cable pre made or get replacment ends and cut the soldered area out and replace with a new end and wire it to crossover.

as for pinging I get 4 pings with an avg. 3ms you should get no errors or time outs.

SS113