vmware windows xp server cant connect to it

Discussion in 'Bukkit Help' started by mrgreaper, Feb 12, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    mrgreaper

    ok our server worked ok on a test pc
    we moved it to a windows xp vmware pc
    ran it
    no errors on the console

    but no one can connect to it! both port 25565 and 8123(dynamic map) have been fwded buy the chap running the vmware for us but no joy

    we tried changing server ip: in server properties to the wan ip of the pc (as got from whatsmyip) and it told us it couldnt bind to the port

    we re-booted the pc and tried again and still it failed to bind. made the line blank again and it booted but still no access

    were pulling our hair out here anyone had this problem and fixed it?
     
  2. Offline

    DerpinLlama

    There should be a bridge network adapters option in VMWare somewhere.
     
  3. Offline

    mrgreaper

    the bridge option was ticked
    the ports are fwded
    the vmc can access the net
    BUT if i go to canyouseeme.com and test port 25565 or 8123 nether wrok (they timeout)
     
  4. Offline

    Toasty

    Solution: Don't use VMWare. USe Virtualbox instead. Even better, use Ubuntu instead of Windows XP.

    Is the PC running the VMWare machine using a firewall? If so, what is it? Are the ports being allowed though the firewall? Also, is the guy hosting the computer using a WiFi router? If so, are the ports forwarded properly on the WiFi router?

    Most importantly, are the ports being forwarded to the right IP adress? They should be forwarded to the internal (assuming the machine is running on a local network) IP address of the VMWare machine. Use "ipconfig /all" in the command line in the virtual windows box to get it's internal IP address, and make sure all the ports you need are forwarded to that location. You also shouldn't need to set an IP address in the bukkit config file.

    (oh yeah, and YML is far superior to .txt. Text files are a nightmare for this kind of stuff)
     
Thread Status:
Not open for further replies.

Share This Page