ok, with the process i'm doing at the moment with my brother up for a couple days, i've built him an unraid server, but they don't like being on at the same time as eachother.

 

i first dumbed all the stuff on his hard drives to my server, setup his, then to put everything back.

 

but when i have both of them on at the same time, and yes they have different names and ips, one being server .4 and the new one as tower .10.

 

anyway with them both on at the same time, you get constant time outs trying to use the webpage for setting things up(on both unraids), if you do pings your lucky to get 1 packet to be successfull each 4 packets.

 

so i'm now having to pull bit by bit from my server onto main computers, shutdown, and then move onto new tower.

 

is there something else i can do, to get these working together properly?

do

 

ifconfig        | logger

ethtool eth0 | logger

smbstatus -v | logger

 

Post your syslogs

 

Maybe this will reveal something.

 

I have 2 unraid's on my network and there is no issue.

 

 

 

ok, i did that in the console, but i don't know where to find the syslog, never done it before. checked in the flash and the closest thing in there was a sysctl which is a config file, nothing else was sys***. had a quick look under mc, but couldn't find a syslog file.. if you can guide me to it, i'll post

Try the Troubleshooting link in WeeboTech's signature (also in mine and others).  We've been trying and trying to make sure that link and all of the other helpful Wiki links are prominently available to new users, but are clearly failing.  If you have any suggestions, please feel free to give them.  I'd like to stress to ALL new users how to get help, and the importance of the syslog, but we can't seem to find the right place or the right way to publicize it better.

 

> The importance of the syslog, but we can't seem to find the right place or the right way to publicize it better.

 

This is something that Tom needs to add to the user interface(emhttp).

Once the syslog and a download capability is available via emhttp it will get much easier.

 

 

Try the Troubleshooting link in WeeboTech's signature (also in mine and others).  We've been trying and trying to make sure that link and all of the other helpful Wiki links are prominently available to new users, but are clearly failing.  If you have any suggestions, please feel free to give them.  I'd like to stress to ALL new users how to get help, and the importance of the syslog, but we can't seem to find the right place or the right way to publicize it better.

 

how about a sticky at the top of the forum?

ok here is the system log for my server and my brothers

 

syslog.txt is mine

 

syslog2.txt is his

 

ps. something i've just noticed the mac address of both are exactly the same  ... isn't the mac address bound the the nic and are all individual?

You are right, they should be different.  That of course is causing the trouble, confusing the router.  One of the MAC addresses HAS to be changed.

 

The syslogs show no significant issues.  The networking looks fine on both, but then you booted each separately, and not at the same time.

You are right, they should be different.  That of course is causing the trouble, confusing the router.  One of the MAC addresses HAS to be changed.

 

The syslogs show no significant issues.  The networking looks fine on both, but then you booted each separately, and not at the same time.

 

yep, ok, next question, how do i do that

 

 

ok here is the system log for my server and my brothers

 

syslog.txt is mine

 

syslog2.txt is his

 

ps. something i've just noticed the mac address of both are exactly the same  ... isn't the mac address bound the the nic and are all individual?

 

LOL!!!! OMG I was going to ask this dumb question, only every NIC is suppose to have a unique MAC address.

I remember years ago whereby cheap nics from questionable companies used the same MAC address, but I've never seen it happen.

This is surely your problem.

 

From the man page of ifconfig

 

       hw class address
              Set the hardware address of this interface, if the device driver supports
              this operation.  The keyword must be followed by the name of the hardware
              class and the printable ASCII equivalent of the hardware address.   Hard-
              ware  classes  currently  supported  include ether (Ethernet), ax25 (AMPR
              AX.25), ARCnet and netrom (AMPR NET/ROM).
[/code


Here's how to do it with ifconfig.
http://linuxhelp.blogspot.com/2005/09/how-to-change-mac-address-of-your.html

[code]
# ifconfig eth0 down
# ifconfig eth0 hw ether 00:80:48:BA:d1:20
# ifconfig eth0 up
# ifconfig eth0 |grep HWaddr

 

Note that it will be a bit cumbersome to do this because you will have to set the address again.

 

I believe you do this by running

/etc/rc.d/rc.inet1 start

 

 

You might be able to get away with setting the variable HWADDR in /etc/rc.d>more /var/tmp/network.cfg

 

This is made by emhttp.

 

root@Atlas [2] /etc/rc.d>more /var/tmp/network.cfg

# Generated network settings

USE_DHCP=yes

IPADDR=

NETMASK=

GATEWAY=

 

It looks like there is code in /etc/rc.d/rc.inet1 to handle the HWADDR variable.

 

 

[/code]

that looks a bit hard for me to try...

 

and there must be more to it then the nic.. cause mine is using the onboard ethernet, and the other i tried 2 completely different brand/types of nics in it, 1 being a 1Gb card and the other a 100Mb and i was having troubles with both

If they BOTH have the same MAC address, then this is your problem.

 

Sep 23 13:32:32 Tower login[1687]: ROOT LOGIN  on `pts/0' from `192.168.1.5'
Sep 23 13:32:43 Tower logger: eth0      Link encap:Ethernet  HWaddr 00:14:6C:C0:2D:07  

Sep 23 13:29:56 Server logger: eth0      Link encap:Ethernet  HWaddr 00:14:6C:C0:2D:07  
Sep 23 13:29:56 Server logger:           inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0

 

Look at the /boot/config/network.cfg file.

See if it has a hard coded mac address.

If not try and set one on one of the machnes by adding the line

 

HWADDR=00:14:6C:C0:2D:07

Changing one of the digits of course.

 

then from the CONSOLE

run

/etc/rc.d/rc.inet1 stop

/etc/rc.d/rc.inet1 start

 

See if that helps

 

you cannot do this via network because the stop will shutdown the network first.

 

go to your unRAID settings menu, see what MAC ADDRESS is displayed on both also.

 

yep, that did it thanks webo, that "HWADDR=00:14:6C:C0:2D:07" line was in the network config file, so changed some of the numbers and were all good now.

 

so this is definatly something tom needs to look into, if his releases are bounding the mac to the same on every one, it's gonna start causing problems for ppl who want to get 2 running, even if it is temporary, to share files between, family/mates....

 

 

 

I don't recall ever seeing an HWADDR line in the network.cfg file before, it is not in mine or any others I've seen.  I'd like to hear from other users who find it in theirs.  Since it is in both of yours, is it possible that you set up one of the machines first, and then copied the config files over to the other.  That would account for both being identical.  You might experiment by removing the HWADDR line from both (or commenting it out, preceding it with a #), and see if they, on reboot, do not each have a different and unique MAC address.

I'm no unraid expert, pretty new myself, but I wanted to note that I installed 2 machines on the same network with no trouble, so I don't think UnRaid comes with the mac address in the config file