Print

[kironohasama]

Alright I recently upgraded from XP to Windows 7 x64. I used to be able to FTP to my Xbox when i was running XP, but now no matter what tutorial I follow, I can't connect to my Xbox.

Here are the setting that used to work on XP, but don't on 7 for some reason.
I set the IPv4 settings on my PC to
IP: 192.168.0.2
Gateway: 255.255.255.0
and the rest left blank.

I set the IP setting in EvoX, XBMC, and M$ Dash to
IP: 192.168.0.5
Gateway: 255.255.225.0
and the rest left blank.

Now as I said these settings worked perfectly for me before. Any ideas?

[Heimdall]

Can you ping the Xbox?

Have you tried temporarily disabling the Firewall / AV on your PC?

[kironohasama]

QUOTE(Heimdall @ Feb 19 2011, 06:07 PM)

Can you ping the Xbox?

Have you tried temporarily disabling the Firewall / AV on your PC?

 I try to ping the IP but when it finishes it says that it took 0ms. And I know that is not possible. I also tried disabling my firewall and AV and no difference.

[Heimdall]

It's completely possible that if it takes less than 0.5mS the ping program will round the displayed result down to 0.

Did it say that there was 0% loss. like this?

CODE

Pinging bthomehub.home [192.168.1.254] with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

This post has been edited by Heimdall: Yesterday, 01:15 PM

[kironohasama]

QUOTE(Heimdall @ Feb 20 2011, 05:13 AM)

It's completely possible that if it takes less than 0.5mS the ping program will round the displayed result down to 0.

Did it say that there was 0% loss. like this?

CODE

Pinging bthomehub.home [192.168.1.254] with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Yeah that's pretty much exactly what it displayed.

[kironohasama]

okay I just tried pinging the IP with 1024 bytes and it sent and received all the packets. So CMD can connect to it, but Windows itself won't.

[Heimdall]

Which AV are you using? I set up a Win7 PC for a friend a couple of weeks ago, and could ping the world but connect to nothing, nomatter which protocol I used. Short version, once I removed the bundled Bullguard AV and replaced it with Microsoft Security Essentials, everything started working perfectly. Disabling it made no difference, I had to remove it. So, you might want to try removing your current AV and installing another, and Security Essentials is free and worked for me.

This post has been edited by Heimdall: Today, 04:12 AM

[kironohasama]

QUOTE(Heimdall @ Feb 20 2011, 08:05 PM)

Which AV are you using? I set up a Win7 PC for a friend a couple of weeks ago, and could ping the world but connect to nothing, nomatter which protocol I used. Short version, once I removed the bundled Bullguard AV and replaced it with Microsoft Security Essentials, everything started working perfectly. Disabling it made no difference, I had to remove it. So, you might want to try removing your current AV and installing another, and Security Essentials is free and worked for me.

I'm using avast free edition. I removed it anyway. No difference.

This post has been edited by kironohasama: Today, 05:59 AM

[kironohasama]

Good news. I tired using a different FTP program and it connected immediately. Thanks for all your help, Heimdall.