Jump to content
OGXbox.com

Search the Community

Showing results for tags 'networking'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Rules
    • Why Can't I Download?
  • Subscribed Members Only
    • Subscribed Members Only
  • Off Topic
    • New Member Introductions
    • Rumble Pit
    • Suggestion Box.
  • General Xbox Discussion
    • General Xbox Discussion
  • Original Xbox Modding Forum
    • Hardware Mods
    • Modchips
    • TSOP Flashing
    • Softmods
    • Repair
  • Xbox Case Modding
    • Case Mods
    • Lighting & Electrical Mods
  • Tutorials
    • Official Tutorials
    • Tutorial Submission
  • Software
    • Bios
    • Dashboards
    • Installation Disks
    • Applications
    • Games
    • Emulators
    • Homebrew
  • Xbox Collecting
    • Xbox Collection Showcase
  • Rare and Uncommon
    • Rare and Uncommon Xbox Hardware
    • Rare and Uncommon Xbox Software
  • Vendors
    • N64 Freak's Products
    • Barnito's Products
  • Development
    • Rocky5's Projects
  • Online Play
    • Game Night
  • Classifieds
    • Wanted
    • For Sale
  • Moderator Section
    • Moderator Back Room

Product Groups

  • Vendor Forum
  • Membership Subscriptions
  • Forum Ads

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 3 results

  1. Basic Networking Guide: I have seen several posts on here from people who avoid FTP because they can't understand networking. I've seen advice from people who don't understand networking. I've seen people try to connect to their xbox but have no clue how. Let me explain this to you. If you don't understand, keep reading it over and over. Nobody can help you any more than this. 1. IP addressing - Your IP address is a series of numbers that gives your devices their identity on your local network. Think of it as a street address that will only mean anything to other people who live in your neighborhood. Anyone who doesn't live in your neighborhood would have absolutely no idea what it means or how to find that address. For example, here is the most common IP scheme (subnet) in the world: 192.168.1.*. for our purposes, we're going to throw away the high level stuff about subnetting here. You'll only ever be dealing with a consumer grade network... or you'd already know this by now. For any 2 devices to communicate on your local network, they need to belong to the same subnet. This means they both need a 192.168.1.* address. (Please remember that I am trying to simplify this for the lay person.) So your pc should be for example: 192.168.1.15. Your xbox could be: 192.168.1.37. As long as they don't have the same number in the fourth slot(octet) as any other device, as long as it is >=1 and <= 254, it will be able to communicate with any other device on that same subnet. By now, you're confused.... "but he's calling the ip address range the subnet but I have another slot named subnet mask"..... 2. Subnet mask - This is a way to chop up a network and keep certain computers from talking to other ones on that network. It was created in the early days of networking as a form of security. It's necessary to configure it for communications, but not necessary to understand it. What you need to understand is that a subnet: (for example) 192.168.1.1 Through 192.168.1.254 is a range of ip addresses. A subnet mask is what determines which IP addresses are in the subnet, so that they can communicate with each other. For our purposes, we're going to always set our subnet masks on all devices identically. 255.255.255.0. This allows each device to talk to each other device. Think of this as a fence... so only certain members of the neighborhood can interact with each other. 255.255.255.0 takes that fence down (by allowing 254 devices to communicate). (Again, I'm trying to simplify this for the lay person. If you get really into networking and realize there are subnets MUCH larger than what we're dealing with and therefore the subnet mask allows this, you may want to argue. I do this for a living and know that the description isn't dead on technically... I'm just trying to make it easy to understand.) All of our neighbors can communicate with each other. 3. Default Gateway - This is only necessary when you need communication OUTSIDE of your subnet. This is always going to be the ip address of your router. It must exist on the same subnet as the device we're trying to give access to. So for instance, your computer is 192.168.1.15 and you want to give it internet access. Your router's ip has to be 192.168.1.something.... If it's anything else your pc can't talk to it. Routers are usually the first available ip address in a subnet. It doesn't have to be this way, but that's usually the way it's set up. So, your pc so far is: IP: 192.168.1.15 Mask: 255.255.255.0 Gateway: 192.168.1.1 Think of the default gateway as the ONLY entrance and exit to the neighborhood. You can't enter or escape this neighborhood without knowing where that gateway is. 4. DNS - Dns is what translates www.whatever.com into an ip address. Your pc uses ip addresses to browse the internet. You just don't know that because we know humans don't remember numbers as well as names. The names mean something to us, so we know them and can use those. So DNS is there to make the conversion for us. This setting for primary and secondary DNS is necessary for internet access. (You need at least one to work. It's not necessary to have both as long as one works.) Google provides free public DNS you can point to, and it will work just fine. 8.8.8.8 8.8.4.4 DNS is like a phone book. You know the name of the person you're wanting to talk to, but can't remember the number. 5. Physical Connectivity - If you're relying on DHCP, both devices will have to be connected to your device that is handing out the addresses via DHCP. This can be directly or via a switch. (think of a switch as being a splitter for ethernet. It's MUCH more sophisticated than that, but for your purposes you can think of it this way.) This will handle the addressing portion as well as make the physical connection properly. You'd only have to configure your devices to use DHCP, and they will get addresses from the DHCP server and you'll be set. If you don't have a router or switch, you'll have to plug a cable directly between your two devices. Since this is an xbox group, we'll focus on cat5 cables and above. (You should be using at least cat5e in this day and age.) Network cables by default are called "straight through". What you need to know is they have 4 pairs of wires inside of them. Some are designated as send. Others receive. For the devices to communicate, one device has to have it's send connected to the other's receive... or else they won't be able to hear each other talk. Switches do this automatically. Some devices will sense this automatically and make the change on their own. This feature is called MDI/MDIX. The xbox doesn't have this feature. If your pc doesn't, you'll have to have what is called a "crossover cable". This cable simply connects send to receive so your two devices can communicate without a switch. 6. Usage - You may ask for clarification on this article, but don't ask for any more networking advice outside of this article. Everything you need is right here. If you're wanting someone to just tell you what to put into each box, ask obama. If you're not willing to do the work yourself and try to understand what you're doing... you don't belong here. If you see someone asking for networking advice in our group, send them the link to this write-up.
  2. Hello, I thought some here may be interested in a tool I have created with the help of ChatGPT. I wanted my Xbox to connect to the Internet but my PC only has wifi so I figured out a way to bridge the connection and share it but my wifi did not really support bridge mode so I had to learn how to set up a NAT and now I have written a program that helps set this up easier. With this your xbox will get internet over Ethernet cable and FTP still works. There is some error handing (such as if bridge is already configured). Basically this will Emulate a bridge and change the ip/port settings for static use when nobridge capability is available for the wifi card. Took about 50 hours to get the program up and going maybe someone else may want to test it and give me some feedback? https://github.com/Iridule/Xbox_Nat_Helper
  3. HackDaBox's Tutorials - Networking Ok here is a basic Networking guide to get you up and running as easy as possible. Check if you have a NIC (Network Interface Card) build-in to your motherboard and if not buy one they are really cheap. Grab a crossover cable (cat 5) to connect your xbox to your PC. Now go into windows xp and right click on My Network Places, click properties, right click on Local Area Connection, click properties. Click internet protocol (TCP/IP), click properties, click on use the following IP address. Type in 192.168.0.1 Click on Subnet Mask and enter 255.255.255.0 Click ok , Click ok, Click X to close the window. Now the computer is setup. Now download Flashfxp and install it. Click on "Site Manager" then click to create a new site. Name it Xbox and for the IP enter 192.168.0.3, verify the port is 21. The username and password are both "xbox", all lower-case and without the quotes. Now if you have installed a large hard drive then Evox dashboard will be setup so you can just boot Evox and then connect using Flashfxp. Boot Evox dashboard then choose System Management, System settings. Enter these settings.IP 192.168.0.3 Subnet Mask 255.255.255.0 DefaultGateway 192.168.0.1 You can't leave the Evox Menu while you are networked , if you play a game for example the link is broken. If you haven't installed a large hard drive then download my Spiderchip Reflash Cd (xbins) as it has Evox Dashboard and networking setup. Just boot the Spiderchip Reflash Cd and then connect using Flashfxp. C - System folder Used for storing the MicroSoft Dashboard files. Also other dashboards you install like Evolution x for example. D - DVD-ROM folder This shows the files on the DVD or CDRW in the DVD-ROM drive if there is one otherwise it will be blank. E - Game Save Folder This is where the save games are stored also any music you have ripped using the MicroSoft dashboard. F - Games & Apps Folder This is where you will put all your games and applications. This is only available if you have added a large hard drive. G - Games & Apps Folder This is where you will put more of your games and applications if you have this folder. This folder is for large hard drives over 137 gigabytes with a bios that supports F and G. The space before 137gig is on F and the rest is on G. Some bioses just put all the available space on F. X Y Z - Temp Folders - the xbox throws data in these cache folders and deletes it later on. Untill you understand more about the folders just don't touch anything except F or G if you have one as these are your folders. To copy files or folders simply right click on the file or folder and click on transfer. The right side of the screen is the xbox. The left side of the screen is your computer. To copy the C and E drives from the original xbox to your computer you would right click on C ( on xbox side ) and click on transfer. When it's finished right click on E ( on xbox side ) and click on transfer. Then after you have changed the hard drives and installed it with Slayer's Evox Auto Installer Cd you would right click on C ( on PC side ) and click on transfer. When it's finished right click on E ( on PC side ) and click on transfer.

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.