Topic: Eth1 not coming up in ver. 6.01

[rparkin]

Hello all,

Despite using SME Server for some time now, I consider myself a rank newbie so...

Don't know if this has been brought up in a previous post or not.  I've looked throughout the FAQ as well as many of the postings here but, if this question has already been posted please give me a pointer.

Anyway, I've been using SME Server for a couple of years now without any problems whatsoever.  However, I upgraded a few months ago to ver. 6.01 and that's when this problem surfaced:  For some reason, Eth1 doesn't come up during reboot and even after it has successfully booted, I'm not able to get it up.

I'm using a cable modem with Comcast as the provider and I've got a small internal network made up of Windows 2003 Server, Windows XP, and variants of Linux machines throughout.

I've got the SME Server set up with the following settings:

- Dedicated Server & Gateway operation mode & I'm passing an account name as the identifier
- DHCP client is enabled
- No external proxy
- I'm using it as a workgroup & domain controller

Both NIC cards are recognized & to be sure that both are working, I checked them on other machines.  I still went and purchased a D-Link modem anyway & tried that as well.

Is there any console level configuration commands that I might be able to use to get it up.  I've already tried ifconfig eth1 up and I was then able to see it but, it was not configured at all & it doesn't stay up after reboot.

I'd appreciate any suggestions that you might offer!

Thanks in advance & Happy New Year all!!

Rob

[crazybob]

I dont know if this is the same thing I had a long time ago, but here is someting to check.

Are both nics trying to be on the same subnet? If they are, one wil not work. I do not know what the subnet  of the cable modems are, but  make sure that they are not the same as the ip subnet for eth1.

It drove me nuts when it happened to me

Bob

[MSmith]

I'm not able to get it up.

 

Sorry, couldn't resist.

[rparkin]

No, they're not on the same subnet.  The thing that I don't understand is that it's been working for quite some time using ver. 5.6 but, now no go.  Can anyone suggest a console command or series of commands that I could use to get the ball rolling?

& as for the "I can't get it up" quote, maybe it means I'm confident in my manhood    Hope there'll be nothing said about the "ball rolling" comment.  Then I'll know for sure that this is a "special" group  

Thanks for the reply!  Let's see if there'll be more that might get me on the road to solving this problem.  It's getting just a tad frustrating.  Especially after having so much success with it over the last couple of years.

Rob

[crazybob]

I used Comcast for a while, and I configured it to pass the ethernet address as the identifier. That worked great.

A couple of questions.

Are the nics the same type?

Have you tried physicaly swaping them?

what does ifconfig tell you about eth1?

it is possible that it just picked now to die


Bob

[CharlieBrady]

Both NIC cards are recognized & to be sure that both are working, I checked them on other machines.

That doesn't mean that they work with the newer linux kernel, or that they are still working (you tested them a while ago, right?).

Firstly, your LAN is working OK, right? If so, then we know that the upgrade hasn't swapped eth0 and eth1.

Look though your messages log files and look for dhcpcd messages. Also log in on the console and see what these commands tell you:

mii-tool eth1
dhcpcd -R -I <client_id> eth1

[rparkin]

The NICs are both 10/100 but different brands.  One is a 3com 3c509 & the other is a hp100.  They both work although I haven't tried swapping them.  I also bought a new Dlink NIC and tried that with the same result.

btw:  I tried the one connected to Eth1 in another machine and it works fine.

ifconfig shows that all the TX packets result in errors.  No packets received.  Other than that, it doesn't tell me much other than it's not UP.

I notice that eth0 shows that the link is "UP BROADCAST MULTICAST MTU:1500 Metric:1" & it shows "EtherTalk Phase 2" whereas eth1 doesn't show the "EtherTalk Phase 2".

Thanks,

Rob

[rparkin]

I've checked the NICs recently.  They both work.

mii-tool eth1 gives me the following:

"SIOCGMIIPHY on 'eth1' failed: Operation not supported"

dhcpcd -R -I <client_id> eth1 gives me nothing.  <client_id> is the system name pandagate.  The same result without the client_id.

Thanks,

Rob

[CharlieBrady]

ifconfig shows that all the TX packets result in errors.  No packets received.  Other than that, it doesn't tell me much other than it's not UP.

Have you checked the cable? I see nothing to suggest that it is working correctly. Unforutnately your NIC doesn't support MII, or mii-tool would tell you whether link was up or not, and that autonegotiation had succeeded.

I notice that eth0 shows that the link is "UP BROADCAST MULTICAST MTU:1500 Metric:1" & it shows "EtherTalk Phase 2" whereas eth1 doesn't show the "EtherTalk Phase 2".

You're not running appletalk on the WAN interface, so that's not surprising.

> btw: I tried the one connected to Eth1 in another machine and it works fine.

Was that other machine running SME, or RedHat 7.3?

I'd try to get fold of a NIC which supported MII. I wouldn't look for other problems until I knew that a link was up and speed negotiation was successful, and MII would tell me that.
Check the cable, and link lights first. Only after link is up correctly do you need to look at DHCP operation.