Yet another FTP crisis in nOOb land...

[lunghd]

Ok gang - After a month spent reading a half inch thick stack of printed tutorials from everywhere I'm pulling out my gray hairs trying to get this darn thing to ftp. I'm bound to be overlooking something simple so maybe ya'll can see what I don't.

I flashed the X3 bios via http using a new crossover cable. That took a bit of futzing around to get it but once I got the X3 'page' up, it appeared to flash fine. (I flashed the bios several weeks ago & console has seemed happy since...)

The console recognizes network activity (lan light blinking...) and Static IP comes up on the bios, dash & apps. (Bios, dash & apps have been set to the same Static IP & Gateway.)

Console instantly recognizes when I unplug the crossover cable & gives me the 'no link' message on my bios.

I can sucessfully ping:
the router
the onboard (pc-to-router) Rhine LAN 'card'
the pci (pc-to-xbox) NetGear Nic card.

Pinging the Xbox IP times out w/ no packet return (100% loss). WS-FTP, FTX, QUIX also do not recognize any connection.

I have rebooted to so many combo's of addresses & gateways with both the NIC and the console that I honestly could not say if I've tried this or that particular combo that worked for someone else... but if it's something a Search here will turn up... chances are I've tried it. (Or think I have...)

Here's the info on the current settings while trying to ftp to the Xbox from my pc using a cross-over cable.

I'd appreciate any input & suggestions!

Thanks!!!

------------------------------------------------
Router IP: 192.168.2.1

Winipcfg information:
----------------------------------------------------------------------------
[On-board VIA Rhine II LAN.] (p.c.- to - router):

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.2.30
Subnet: 255.255.255.0
Default Gateway: 192.168.2.1
DHCP Server: 192.168.2.1

----------------------------------------------------------------------------
[ PCI NetGear FA310TX nic card. ] (p.c. - to - XBOX) info:

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.30


X3 BIOS, M$Dash, Avalaunch, Slayers/Evox settings:

DHCP: Disabled
Static: 192.168.1.200
Subnet: 255.255.255.0
Gateway IP: 192.168.1.1
DNS1: 0.0.0.0
DNS2: 0.0.0.0
FTP Log In: x3(bios) or xbox
FTP PWD: x3(bios) or xbox (as appropriate)

 

[RealestDeMo]

enable DCHP on the xbox (duh...)

 

[Martin C]

Basics: for TCP/IP you have an IP Address and a Subnet Mask.

Lets take your config for example...

[ PCI NetGear FA310TX nic card. ] (p.c. - to - XBOX) info:

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.30

You're on the 192.168.1.0 subnet of a class C network. The subnet mask 255.255.255.0 tells us that addresses 192.168.1.1 - 192.168.1.254 can be used.

Since you have two networks (pc -> router and pc -> Xbox), I'm going to ignore the router. Disable the nic connected to the router for the time being.

So 192.168.1.1 / 255.255.255.0 is already taken by the PC NIC. Therefore your address of 192.168.1.200 / 255.255.255.0 should be fine. Try and ping the localhost (127.0.0.1). Then try to ping the local IP (192.168.1.1). If both of these are fine then try to ping the Xbox (192.168.1.200). Remember that any firewalls you have configured (including XP SP2) will need to know that the 192.168.1.0 network is trusted, if this is what you wish to do. Otherwise, you'll need to let the firewall know which ports and/or programs are trying to access the Xbox.

Martin

 

[lunghd]

enable DCHP on the xbox (duh...)

? That gives me a IP of 0.0.0.0 with "Err X" on the bios...

(I'm using a crossover cable to a 2nd NIC card in the pc.)

 

[lunghd]

Hey Martin -
I appreciate the response. I've read thru several of your posts helping others on this & thought I'd covered the bases after reading thru all the info on this. Networks just aren't that hard to set up at this level which is why I thought I must have just overlooked something simple that might be obvious to someone not in the middle of it.
Going thru your reply - here's what I have been experiencing and just redid all step by step while reading your post.:

Since you have two networks (pc -> router and pc -> Xbox), I'm going to ignore the router. Disable the nic connected to the router for the time being.

Will do. I'll redo this entire sequence with the onboard LAN disabled after posting this and rebooting.

So 192.168.1.1 / 255.255.255.0 is already taken by the PC NIC. Therefore your address of 192.168.1.200 / 255.255.255.0 should be fine. Try and ping the localhost (127.0.0.1).

127.0.0.1 Pinged "ok".

Then try to ping the local IP (192.168.1.1).

192.168.1.1 Pinged "ok".

If both of these are fine then try to ping the Xbox (192.168.1.200).

192.168.1.200 "Request timed out."

Remember that any firewalls you have configured (including XP SP2) will need to know that the 192.168.1.0 network is trusted, if this is what you wish to do.

Yup. Xbox 'network' 192.168.1.0 was allready in my "trusted zone" within ZoneAlarm Pro. Also tried w/ ZA shutdown with no joy there either. I'm running Win98SE so I should be free of any MicroSloth imposed firewalls unless some security update is killing me in the background.

Otherwise, you'll need to let the firewall know which ports and/or programs are trying to access the Xbox.

Martin

ZA is set to notify me if a new program or hardware wants to use the connection(s) but after shutting ZA down and having no luck I'm almost thinking I have a hardware issue with the NIC card at this point. Given that I can access the net with the onboard LAN... I may swap connections while I'm at it and try the onboard to connect.

Thanks for your input - I'll disable the onboard LAN & try again then post back w/ results.

Thanks,
lunghd

 

[lunghd]

Martin - Disabled onboard 'card' & went back thru the entire sequence... no change. I also confirmed with winipconfig that the p.c did not detect the disabled onboard lan 'card'.
I then swapped the x-over cable to p.c.'s onboard lan 'card' & reset that IP to match the xbox 'network', rebooted both pc & console... No change.

The odd thing was that the console would show it's correct static IP 192.168.1.200 when plugged into the disabled onboard lan 'card'. (Unplugging either end would give the proper 'no link' message from the X3 bios - but static IP was "active" when plugged into the disabled lan's port.) That one I cannot explain since I had disabled the onboard 'card' in the p.c.'s bios. As far as the computer was concerned, only the NetGear 'pc-to-xbox' nic card remained active and the onboard 'card' did not exist ... how the xbox found a link, I dunno. Some type of 'loopback' that exists in a nic that only indicates a card exists??? (Related to wake on lan function, maybe?)

I know the onboard lan works, so I reset it's IP correctly for the Xbox 'network', re-enabled it in the bios and rebooted the p.c. with the x-over cable now plugged into it. That eliminates everything but the new X-over cable that I bought expressly for modding the console. From my limited experience - using either card w/ the proper static IP... this 'network' should work and actually did function long enough initially (after a bit of fooling with it...) to http in and flash the bios when first modding the console.

I have a crimp tool & connectors so I'll pick up some more cat5 and run a line direct to the router and ditch the x-over cable since that's the next cheapest potential solution. (Unless someone has more ideas/input???).


Thanks!
lunghd

 

[Martin C]

What version of Windows are you running? I'm getting the impression its 95/98/ME ??

Martin

 

[Catalyst]

------------------------------------------------
Router IP: 192.168.2.1

Winipcfg information:
----------------------------------------------------------------------------
[On-board VIA Rhine II LAN.] (p.c.- to - router):

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.2.30
Subnet: 255.255.255.0
Default Gateway: 192.168.2.1
DHCP Server: 192.168.2.1

----------------------------------------------------------------------------
[ PCI NetGear FA310TX nic card. ] (p.c. - to - XBOX) info:

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.30


X3 BIOS, M$Dash, Avalaunch, Slayers/Evox settings:

DHCP: Disabled
Static: 192.168.1.200
Subnet: 255.255.255.0
Gateway IP: 192.168.1.1
DNS1: 0.0.0.0
DNS2: 0.0.0.0
FTP Log In: x3(bios) or xbox
FTP PWD: x3(bios) or xbox (as appropriate)

Here's my opinion. This can work except for some weird sttings you have. If you look here...

----------------------------------------------------------------------------
[ PCI NetGear FA310TX nic card. ] (p.c. - to - XBOX) info:

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.30

Your IP has to be in the same network as your Default Gatway. A default gateway is how a PC crosses over networks via your router. So the Default gateway has to be an IP that your router holds on the 192.168.1.0/24 network. If you look at your PC you can see that it is set to an IP of 192.168.2.30 and it's gateway is 192.168.2.1. The 192.168.2.1 IP address is the router. Now the reason you can ping the PCI NetGear FA310TX nic card is because it's directly connected to your PC. Alls you gotta do to make this work is change the Gateway on your second nic on your PC from 192.168.2.30 to 192.168.1.1 and your done.

Simple huh?

 

[Catalyst]

Martin - Disabled onboard 'card' & went back thru the entire sequence... no change. I also confirmed with winipconfig that the p.c did not detect the disabled onboard lan 'card'.
I then swapped the x-over cable to p.c.'s onboard lan 'card' & reset that IP to match the xbox 'network', rebooted both pc & console... No change.

The odd thing was that the console would show it's correct static IP 192.168.1.200 when plugged into the disabled onboard lan 'card'. (Unplugging either end would give the proper 'no link' message from the X3 bios - but static IP was "active" when plugged into the disabled lan's port.) That one I cannot explain since I had disabled the onboard 'card' in the p.c.'s bios. As far as the computer was concerned, only the NetGear 'pc-to-xbox' nic card remained active and the onboard 'card' did not exist ... how the xbox found a link, I dunno. Some type of 'loopback' that exists in a nic that only indicates a card exists??? (Related to wake on lan function, maybe?)

I know the onboard lan works, so I reset it's IP correctly for the Xbox 'network', re-enabled it in the bios and rebooted the p.c. with the x-over cable now plugged into it. That eliminates everything but the new X-over cable that I bought expressly for modding the console. From my limited experience - using either card w/ the proper static IP... this 'network' should work and actually did function long enough initially (after a bit of fooling with it...) to http in and flash the bios when first modding the console.

I have a crimp tool & connectors so I'll pick up some more cat5 and run a line direct to the router and ditch the x-over cable since that's the next cheapest potential solution. (Unless someone has more ideas/input???).


Thanks!
lunghd

Lemme try and answer some more of your questions. First of all understand that the link light denotes a layer 1 connection. This just means at the most basic level there is connectivity. Esentially there is an electric charge going through the wire.

I truly believe that your cable is ound because you got a link light. If you just set it up as before and change that one entry on your PC you should be fine. There is a slight chance that with both NIC's enabled that your PC will try to send out info accross the NIC that is connected to the router as opposed to the one connected to the XBox... I doubt this will happen but since you've already disabled that NIC I guess it can't hurt. Try what I said and if you have some trouble or want to work with both NICs active so you can surf the web and ftp to your xbox I can walk you through making a "static route" on your pc that will point to your xbox.

Anywho... I'm pretty sure it will work with the new settings. Good Luck!!

 

[Martin C]

The default gateway is only used when an address outside of the subnet is needed. I cannot see how this would be affected as we're making sure the Xbox and PC NIC are in the same subnet. Even with the gateway set to something else, it shouldn't impact direct addressing in the subnet.

Martin

 

[lunghd]

What version of Windows are you running? I'm getting the impression its 95/98/ME ??

Martin

Windows98SE.
(Sorry - had that in there and lost it during my cut & paste episode.)

 

[lunghd]

Here's my opinion. This can work except for some weird sttings you have. If you look here...

----------------------------------------------------------------------------
[ PCI NetGear FA310TX nic card. ] (p.c. - to - XBOX) info:

DNS Servers: 192.168.2.1
Node Type: Broadcast
IP Address: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.2.30

Your IP has to be in the same network as your Default Gatway. A default gateway is how a PC crosses over networks via your router. So the Default gateway has to be an IP that your router holds on the 192.168.1.0/24 network. If you look at your PC you can see that it is set to an IP of 192.168.2.30 and it's gateway is 192.168.2.1. The 192.168.2.1 IP address is the router. Now the reason you can ping the PCI NetGear FA310TX nic card is because it's directly connected to your PC. Alls you gotta do to make this work is change the Gateway on your second nic on your PC from 192.168.2.30 to 192.168.1.1 and your done.

Simple huh?

Thanks for the input!
I just gave it a try... didn't work. (Pretty sure I'd tried it before but reset the gateway, rebooted & pinging still times out w/ no response.

 

[lunghd]

Lemme try and answer some more of your questions. First of all understand that the link light denotes a layer 1 connection. This just means at the most basic level there is connectivity. Esentially there is an electric charge going through the wire.

I truly believe that your cable is ound because you got a link light. If you just set it up as before and change that one entry on your PC you should be fine. There is a slight chance that with both NIC's enabled that your PC will try to send out info accross the NIC that is connected to the router as opposed to the one connected to the XBox... I doubt this will happen but since you've already disabled that NIC I guess it can't hurt. Try what I said and if you have some trouble or want to work with both NICs active so you can surf the web and ftp to your xbox I can walk you through making a "static route" on your pc that will point to your xbox.

Anywho... I'm pretty sure it will work with the new settings. Good Luck!!

Hey, Thanks again for the info. Yeah - something's wierd with this thing... these settings "should" have worked.

The netgear nic is for the xbox only & my onboard lan 'card' is the only way out to the router & the net. With it active, or disabled, the result is the same - pinging the xbox times out. I have both 'cards' active now & still have gateway on netgear nic set to your suggestion.

 

[Catalyst]

The default gateway is only used when an address outside of the subnet is needed. I cannot see how this would be affected as we're making sure the Xbox and PC NIC are in the same subnet. Even with the gateway set to something else, it shouldn't impact direct addressing in the subnet.

Martin

You would think so but Windows needs a GW. It's pretty stupid but I swear when I hook up two PC's to a dumb switch without a correct gateway I get no love. I even lost a bet over this. It's something to do with the OS.

Well, it didn't work anyway so I suck.

 

[Catalyst]

Hey, Thanks again for the info. Yeah - something's wierd with this thing... these settings "should" have worked.

The netgear nic is for the xbox only & my onboard lan 'card' is the only way out to the router & the net. With it active, or disabled, the result is the same - pinging the xbox times out. I have both 'cards' active now & still have gateway on netgear nic set to your suggestion.

Man... I got two strikes... crap.

Um, did you try using the NIC that is currently running to the router. Your going to have to swap cables 'cause your router is using a stright through... (that is if your using a linksys router which is actually a switch with a rsm on it... which makes it a DCE to DTE connection so your actually getting timing off your PC for that connection... nevermind)

Anywho... you can try that and see if it's the NIC that's the problem...

Sorry that my first thing didn't work. It's just whenever there is a network problem Martian C always tries to beat me to it...

jealousy is an ugly thing...

j/k!

I don't know what he's jealous of 'cause I was wrong but... you get the idea.

 

[RealestDeMo]

:-/ sorry, missed this "the pci (pc-to-xbox) NetGear Nic card" assumed they were both connected to the router... heh...

 

[Martin C]

I was gonna suggest swapping LAN connections, so it's worth doing now two of us have suggested it

Also in regard to the GW, I've never had one set on the PC NIC for my Xbox connection....

Martin

 

[Catalyst]

I was gonna suggest swapping LAN connections, so it's worth doing now two of us have suggested it

Also in regard to the GW, I've never had one set on the PC NIC for my Xbox connection....

Martin

Yeah I actually screwed that up too...

When you have two conncetions to a switch you would think that as long as it's layer two that they would talk. But if the two IP's are on different networks.. they need a default gateway... even if the one you put in doesn't exsist... that's where I went wrong. So I was dead wrong...

But it's Monday. So I get a mulligian.

You know, sometimes you get good advice and sometimes... I answer your posts

 

[lunghd]

What fun! Ran some new Cat5, paid way too much for some patch cables, mounted a fancy new port plate on the wall... then discovered that the new Cat5 I pulled downstairs had a break in it somewhere.

Solution: A $25 D-Link network switch and my old Cat5 line that I still had dropped to the computer. Heck - I was even able to use my crossover cable (didn't realize I could do that...) so I can at least recover $20 for the 50' patch cable. Either way - WS-FTP scored right into the bios on the first try after a reboot.

I really appreciate the input guys. Now I can blow the console up from the inside!

 

[Martin C]

Glad you finally got it sorted!!!

Quite a few switches have an auto-sense feature to use both straight-thru and crossover cables. Mine does!

Have fun

Martin