xboxscene.org forums

Author Topic: Xexmenu Ftp Problems  (Read 54 times)

thwack

  • Archived User
  • Hero Member
  • *
  • Posts: 785
Xexmenu Ftp Problems
« on: May 05, 2010, 07:11:00 AM »

Have you tried unchecking 'passive mode' on your ftp browser?
Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Xexmenu Ftp Problems
« Reply #1 on: May 05, 2010, 07:23:00 AM »

Connecting via a router that supports DHCP gets rid of 99.99% of such problems, because it takes away the manual configuration element (a.k.a. finger trouble).

Your manually configured IP addresses are entirely private to your network, so there is no risk in sharing them! What are the IP addresses, subnet masks, and default gateways of your PC and Xbox?

Can you ping the Xbox from the PC?

Try Filezilla instead of FlashFXP.
Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Xexmenu Ftp Problems
« Reply #2 on: May 05, 2010, 08:51:00 AM »

Networking 101.

Networks aren't magic - for two devices to communicate they have to have different IP addresses, and either:

A. be in the same subnet and connected to the same logical segment, or
B. be in different subnets, but connected via a router that understands the existence of and relationship between subnet 1 and subnet 2

Ignore B (that's way beyond anything you're likely to see in a home network), you need option A.

To be in the same subnet two devices have to have the same subnet mask, and the same address prefix when their IP addresses are ANDed with the subnet mask. If you use a home router / switch with DHCP it sorts this out for you. However, as you don't have a router to do this, you have to manually set the IP address and subnet mask for your Xbox and your PC so they are different, but in the same subnet, otherwise they can't talk to each other.

So, set your Xbox to 192.168.1.10, your PC to 192.168.1.11, subnet mask on both to 255.255.255.0. The prefix is 192.168.1.0 so they are in the same subnet, but the individual addresses are 10 and 11, so they are different, and hence the devices can uniquely address each other.

/Networking 101
Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Xexmenu Ftp Problems
« Reply #3 on: May 05, 2010, 09:54:00 AM »

QUOTE(jrx09 @ May 5 2010, 04:37 PM) View Post

Thanks but it still didnt work, although when I changed the IP on the LAN connection PC-side it stopped coming up with 'Limited Connectivity' on that connection. Changed the xbox config manually as you said but still can't get it to even ping, let alone connect with FlashFXP. I have used this connection to get on XBL before without needing to fiddle with IP addresses, obviously not on this JTAG console though.

Guess I need a router to sort this out?

Which connection? You said your xbox was connected directly to your laptop via a single cable, and that doesn't get you access to XBL.

You don't need to fiddle with IP addresses if you are connected to the Internet because your router sorts it out for you.......

Try a crossover cable.
Logged

Heimdall

  • Archived User
  • Hero Member
  • *
  • Posts: 3862
Xexmenu Ftp Problems
« Reply #4 on: May 05, 2010, 10:51:00 AM »

There's no reason why it won't work - it's a perfectly normal setup. All I can suggest is that you double check the IP addresses and subnet masks you have defined.

A thought - what's the IP address of your wireless connection? If it's also a 192.168.1.x address then that's your problem. Even if it isn't, you could temporarily disable your wireless connection on your laptop, just to eliminate it from the equation.
Logged

jrx09

  • Archived User
  • Newbie
  • *
  • Posts: 10
Xexmenu Ftp Problems
« Reply #5 on: May 05, 2010, 03:24:00 PM »

QUOTE(Heimdall @ May 5 2010, 05:51 PM) View Post

A thought - what's the IP address of your wireless connection? If it's also a 192.168.1.x address then that's your problem. Even if it isn't, you could temporarily disable your wireless connection on your laptop, just to eliminate it from the equation.


My wireless connection IP is indeed 192.168.1.x but I've had it disabled all this time and have tried changing the ip prefix as well just in case, still no dice.

Will try to find a router to try it with, if that doesn't work I guess it's just not gonna happen!
Logged