Topic: Changed IP Address. Now no network access.

[wifinetguy]

I have SME 7.1.2. We had a need to change the IP addressing at the office. I went to the console, logged in as Admin and ran  the configure server option. Here I changed the IP address of the server and verified all other addressing specifics. Then I  rebooted. After the reboot, I  can no longer access the network. I can't ping anything except the internal network adapter's IP address. I've tried to ping using both names and IP addresses. No go on either one. I've rerun the setup from the console, thinking that I must have missed something. All of the values are correct. Rebooted, same result. All other computers on the network are on the same subnet and  can access internal (except the SME Server) and external (Internet) resources. I don't know what to look for now. I've tried a different cable, just in case.

Any help is appreciated.

[maounique]

As i understand, you do not run your SME server as gateway. If you have 2 network interfaces on, try to see if you did not plug the cable in the wrong one, then try this command logged in as root:
ifconfig
It should list your interfaces (eth0, eth1 if there is one, etc.) If you only have loopback interface (lo), then you might want to check the NIC and then the driver assigned to it, to match the hardware.

[wifinetguy]

No, actually it's in server-only mode. I have an IPCOP as my firewall/gateway. It does have 2 NICs (and I tried both to make sure I didn't have a hardware  failure). IFCONFIG shows the correct IP information such as address, broadcast, etc.

[maounique]

You may want to remove or to disable the NIC you do not use.
Do the leds (if available) on the switch and/or the NIC lit up ? Try to ping the IP of the server from internal network. Do that continuously (in windows use the -t as in ping x.x.x.x -t and watch the leds. Do the blink ? Try to see if you have another IP on the network which is the same as the servers IP. Try changing the server's IP to another one you are sure it is not in use then ping it again.
If you have 2 similar hardware NICs (same chipset), and you do not want/can't remove one, try all the steps above alternatively on each NIC.

[wifinetguy]

The thing is: this has been working great for about 6 months. The only thing I did yesterday was run the config to change theIP address. Then it stopped working.

[maounique]

I understand that. I did that countless times and i have also 2 NICs in the machines as i mostly use them as gateways. Suddenly, during reconfigure, the eth1 becomes eth0 and i have to switch cables because i am too lazy to run reconfigure again and it takes forever on PI 200. Also, reinstalling on the same machine, sometimes changes the order, (I marked the NICs IPCop style, using colors).
Since you have 2 NICs it may well be the case. It is something i tell you from experience, I know it should not happen, but it does.

[wifinetguy]

OK.Thanks for the suggestion. But I did swap the cable to the other NIC. Same result.

[maounique]

Also checked the LEDs, the IP not to be a duplicate, etc ? Using both NICs each time ? Tried changing IP ?
IF you did and everything looks good but it still no network access, plug 2 cables in the both NICs and the other ends in the switch. Assign the other NIC an IP from the internal network and put the server in gateway mode. try to ping both IPs from internal network. Watch the LEDs on the NICs if they blink correctly when they are ping-ed.
I would do all these steps. After that, I would go crazy and change NICs with some different chipsets and reconfigure.
If everything looks fine in the IFCONFIG output, then it must be the card, the media, the switch. After this, i don't know...

[wifinetguy]

OK, Maounique. Thanks very much for your help. I appreciate it.