Jump to content

HAVOC

Members
  • Content Count

    330
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HAVOC

  • Rank
    Advanced Member
  • Birthday 08/24/1982

Converted

  • Gender
    Male
  • Location
    New Jersey

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Quick question in regards to accessing unraid through the opnevpn docker. I have it all setup through the bridged mode. I can connect with my iphone. I have no access to unraid, I can access everything else with in my network such as other pc's through rdc. Im just curious if I have to edit anything in regards to the docker settings or open vpn. Thanks
  2. Guys thanks for the help but I reverted back to 6.1.19. I just reinstalled and all my shares are back. I have no idea what i screwed up. Just dont have the time to have my shares down. Thanks for the help and hopefully somehow i can resolve this at a later time.
  3. Bridging is enabled and my docker apps are working.
  4. When I type the ip in explorer im prompted to enter a username and password. I have all shares set to public. All machines doing the same thing. How come the ip is coming up 192.168.122.1? Thats weird right?
  5. No I deleted the old dhcp reservation. Just rebooted the router.
  6. Yeah but I updated the new mac address..... I also pulled the flash drive out and updated that network file in the config folder.
  7. Let me re-clarify I have unraid dhcp reserved for 192.168.1.6. During the upgrade I had to switch the ports on the server due to connectivity issues. I feel like im getting close to the root of the problem.
  8. Thanks. I did have an issue with no connectivity. I had to switch the Ethernet port to one that I wasn't using. IPMI is working fine. I feel like their is an issue with unraid not broadcasting itself. Is their a way to reset the network configuration?
  9. I have set unraid as the static for 192.168.1.6
  10. Lets try one more thing. First, download your diagnostics file. 'Tools' >>> 'Diagnostics'. Open up the zip file and navigate to the system folder. open up the file named ifconfig.txt. Look for the section named eth0. you will find a line like this: [/code] inet 192.168.1.242 netmask 255.255.255.0 broadcast 0.0.0.0 The inet parameter is the server's IP address. (in this case--- 192.168.1.242) Second, take this address and open up Windows Explorer: type \\192.168.1.242 in the address bar. (Those are back-slashes, NOT forward-slashes!) You should now be able to see the server with the User Shares and flash drive folders. This is what the file says: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.6 netmask 255.255.255.0 broadcast 192.168.1.255 ether 00:25:90:57:9e:a9 txqueuelen 1000 (Ethernet) RX packets 1419455 bytes 211967415 (202.1 MiB) RX errors 0 dropped 56100 overruns 0 frame 0 TX packets 1282458 bytes 3318919791 (3.0 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:cd:e7:d7:41 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28760 bytes 2034678 (1.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 00:25:90:57:9e:a9 txqueuelen 1000 (Ethernet) RX packets 1424034 bytes 238004584 (226.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2403349 bytes 3402779201 (3.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7e00000-f7e20000 eth1: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 00:25:90:57:9e:a8 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xf7d00000-f7d20000 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 6179117 bytes 642850649 (613.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6179117 bytes 642850649 (613.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethde531ee: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 0e:8a:10:9a:e0:80 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28760 bytes 2034678 (1.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:02:8d:99 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 52:54:00:02:8d:99 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I found something strange in the network.cfg file the IP address of my server is 192.168.1.6 not 192.168.1.22 # Generated settings: USE_DHCP="yes" IPADDR="192.168.1.22" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" BRIDGING="yes" BRNAME="br0"
  11. You have to precede the IP with \\, just the same as when you type in the servername. \\IP_of_your_unRAID Also, did you ever read that link? If you can access a public share then SMB is working and the secret to accessing a secure or private share is there in that link. The problem is all about the way Windows works for accessing any network files and is not really an unRAID problem. Alright no luck with entering the server ip address all I get is a windows security prompt to enter username and password. I opened up a cmd command line and entered "net use * /delete" the read back was their are no entries in the list. I found something strange in the network.cfg file the IP address of my server is 192.168.1.6 not 192.168.1.22 # Generated settings: USE_DHCP="yes" IPADDR="192.168.1.22" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" BRIDGING="yes" BRNAME="br0"
  12. I'm at work I'll give it a try when I get home. I can't access any shares all are public. Weird thing is plex and air video hd work. I agree it's a windows problem but I can't even see the server from windows end.
  13. I put the ip in and the browser pops up.