mark seaton

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by mark seaton

  1. Its in Bridge mode

     

    root@Tower:~# docker ps
    CONTAINER ID   IMAGE                                     COMMAND                  CREATED          STATUS                          PORTS                                                                                                                                     NAMES
    d3d6abe41d10   nodiaque/steamcmd:enshrouded_proton       "/opt/scripts/start.…"   56 minutes ago   Up 4 minutes                    0.0.0.0:15636-15637->15636-15637/udp, :::15636-15637->15636-15637/udp                                                                     Enshrouded_Proton

     

    image.thumb.png.abaccebd38ce4c78d8affbc93d938ed1.png

    Logs.txt

  2. Cant see game server using ether build in game browser or steam browser, I have tried pinging the ports and there is no response.

     

    I can ping my unraid server ip fine but not the docker, I have tried stopping/Starting docker, rebooting unraid, and still nothing any help would be appreciated. Also there are no port conflicts as far as i can see.

     

    C:\Users\mseat>ping 10.0.0.211:15636
    Ping request could not find host 10.0.0.211:15636. Please check the name and try again.

     

    C:\Users\mseat>ping 10.0.0.211:15637
    Ping request could not find host 10.0.0.211:15637. Please check the name and try again.

     

    C:\Users\mseat>ping 10.0.0.211

    Pinging 10.0.0.211 with 32 bytes of data:
    Reply from 10.0.0.211: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.211: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.211: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.211: bytes=32 time<1ms TTL=64

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

  3. On 7/21/2021 at 2:01 PM, ljm42 said:

     

    Is that the server's LAN address?

     

    If you connected with "remote access to server", then you will not have access to the LAN IP address. You need to use the server's tunnel IP listed in the webgui

     

    If you want to access the server's LAN address then choose "remote access to LAN" instead.

    I changed the connection to "remote access to Lan" and I still cant connect to the shares on my unraid server which has a LAN ip of 192.168.1.109, what am i missing?

     

    Here is a screen shot of my settings, the blanked out is my duckdns

    image.thumb.png.f900538c143e563fc16f7246460ab0d5.png

  4. 17 hours ago, ljm42 said:

    So if the remote client is a Windows box you would go to the search bar and type:

      \\10.252.1.1

    and Windows would use SMB to connect to that IP address. 

    So if my unraid server was 192.168.1.109 and a share on it was say movies then in windows i would use

     

    \\192.168.1.109\movies

     

    and I would have to do this for each of my shares on my Unraid box

     

    I can also Map Network drive in windows correct?

     

    is the reason for this because Wiregard is a silent VPN and does not allow SMB and NTF broadcasting?

     

  5. Better VM Graphics needs to be a priority, i have gone through 4 different computers and 3 different graphic cards all with mixed mostly failed results, and the videos by Spaceinvader and others are out of date and in those videos issues are pointed out that should have been addressed by now, and i have not found a updated list of supported tested hardware ether, the wiki by unraid is very out of date.

     

    Unraid is looking less and less of a option for me unless the whole VM issues get fixed/updated

    • Like 2