Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: spook on January 28, 2006, 10:07:48 PM
-
How will SME server react if I plug in a 3Com NIC, and disable the onboard NIC that it has been using so far? There's only one NIC in the machine, how much re-configuring will be necessary?
-
Given that it's in server-only mode, you most likely won't have to do anything at all.
-
unless the on board nic is the same chipset as the card you are putting in, it will not work. All you have to do is re-run the server configuration and choose the new nic, everything else will stay the same.....
HTH
-
It IS server-only, I use it for mail, web and file storage. And some time in the future, printing.
Re-run the configuration? How? And won't that screw up my users, ibays, SQL databases and everything? Or can I just redo the nic config?
-
you can re-run the console configuration as many times as you like and it will only change the bits you alter!
I have changed NICs in systems many times.
-
Sweet, I think I'll do that. Now I just hope that it solves my problems... (Check "Samba problems" thread)
-
Damn, no luck. I installed the other NIC, and disabled the onboard one. I ran the configuration from the server console, and it acted like nothing had changed. Except that now there was no connection to the internet from the console, and no ping from other machines on my network.
Any ideas? Do I have to run any other configuration thingies?
On a side note: Plugged in the printer (Brother HL-1440, USB) and it works like a charm. A painstakingly slow-ass charm. Like file transfer, printing is insanely slow from Samba. Which is why I was trying to change the nic in the first place...
-
ok, gotta start this one over. Why were you changing network cards if it was working before? Are you sure it was the nic? Why do you think it was the nic?
-
How will SME server react if I plug in a 3Com NIC, and disable the onboard NIC that it has been using so far? There's only one NIC in the machine, how much re-configuring will be necessary?
WHat version do you have?
If it's 7.0pre1, you will need to log in as root, and run "kudzu -q", then log in as admin, and choose the configure option from the menu.
-
If it's 7.0pre1, you will need to log in as root, and run "kudzu -q", then log in as admin, and choose the configure option from the menu.
Spot on, it IS 7.0pre1, I'll try it right away!
-
Ding-ding-ding, we have a winner!
Kudzu -Q did the trick, thanks a bunch!
Problem solved :)