fschris Posted January 28 Share Posted January 28 (edited) I upgraded my entire system to a new CPU and Mobo - Asus Z790-P D4 wifi. I am able to boot up - But I cannot ping my servers static IP. I have checked lots of things. I am on 6.12.6 OS I disabled Wifi in the BIOS,. From the Server CLI I can ping 192.168.2.3 ( basically I can ping myself) I cannot ping my Gateway 192.168.1.1 and I look in the router and I do not see my Server. I do see the NIC port is green with activity and it says it has a link... Should i set it to DHCP in the GUI and try that? I can try to get a diag zip but I am guessing it will save to the flash drive and then i Can grab it that way? Maybe this is due to the new mobo utilizing 2.5Gbe Any Ideas?? Chris Edited January 28 by fschris Quote Link to comment
fschris Posted January 28 Author Share Posted January 28 Looks like I need to read this: Quote Link to comment
itimpi Posted January 28 Share Posted January 28 You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. it is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. Quote Link to comment
MAM59 Posted January 28 Share Posted January 28 5 hours ago, fschris said: From the Server CLI I can ping 192.168.2.3 ( basically I can ping myself) I cannot ping my Gateway 192.168.1.1 and I look in the router and I do not see my Server. I do see the NIC port is green with activity and it says it has a link... There is likely a misconfiguration, machine and gateway need to be on the same net unless you are using specific netmasks. Check your addresses and routing tables. Quote Link to comment
JorgeB Posted January 28 Share Posted January 28 8 hours ago, fschris said: Looks like I need to read this: That driver is only needed if you are using jumbo frames with a Realtek 8125 2.5GbE. Quote Link to comment
fschris Posted January 28 Author Share Posted January 28 (edited) Sorry I did not get Diag file. Here it is tower-diagnostics-20230313-1207.zip Edited January 28 by fschris Quote Link to comment
JorgeB Posted January 29 Share Posted January 29 Try renaming /boot/config/network.cfg to bak to go back to default DHCP settings, then reboot and post new diags. Quote Link to comment
fschris Posted January 29 Author Share Posted January 29 Okay - Here is the DIAG after to .bak --- I am now able to see my server on my networh with DHCP. _ I guess I am having an issue with my static settings. Wierd since they worked with the old Motherboard. Here is the new DIAG file: tower-diagnostics-20240129-0938.zip Quote Link to comment
trurl Posted January 29 Share Posted January 29 The fixed IP you had assigned earlier was not on the same subnet as your router. Quote Link to comment
fschris Posted January 29 Author Share Posted January 29 (edited) Here is my Router config - Any tips to use static and 192.168.2.3 ? Edited January 29 by fschris Clarity Quote Link to comment
itimpi Posted January 29 Share Posted January 29 You need to either set Unraid to an address on the 192.168.1.x network or set a gateway on the 192.168.2.x network. Quote Link to comment
Solution fschris Posted January 30 Author Solution Share Posted January 30 Thanks - I ended up using DHCP and reserving the IP in my router... Appreciate the help everyone. Quote Link to comment
trurl Posted January 30 Share Posted January 30 1 hour ago, fschris said: Thanks - I ended up using DHCP and reserving the IP in my router... Appreciate the help everyone. Better to manage IPs all in the one place that really matters. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.