Topic: migrated to New Hardware - DDNS and email issues.

[groutley]

Hello,
 I am hoping for some help.
I have migrated my sme 7.3 server to new Hardware by following the http://wiki.contribs.org/Moving_SME_to_new_Hardware procedure using affa.
The process worked very well, and after shutting down the old server and rising the new I am having a couple of issues..

1/ It doesn't seem that the new server is registering with dyndns.org,  I have manually updated the current ip address with dyndns.org

2/ I am not receiving any emails from external, (I would put this down to problem #1, but with the manual update of the ipaddress I cant see it as the issue.)

Internal emails seem to be working fine.

any ideas  on possible causes..  or what to check  would really be appreciated..

G

[groutley]

Update:
  I have noticed the following in the server-manager "Review Configuration"

Code: [Select]

Review configuration
Networking Parameters
Server Mode servergateway
Local IP address / subnet mask 192.168.37.251/255.255.255.0
External IP address / subnet mask 192.168.38.100
Additional local networks 192.168.38.0/255.255.255.0 via 192.168.37.252
192.168.37.0/255.255.255.0
DHCP server disabledIt is the 'External IP Address" that concerns me..
I do not know where it has record of this address..
During Build of the server I did have the 'external' interface connected to that Subnet router..
But an 'ifconfig eth1' (my external adapter)  shows

Code: [Select]

[root@l1nuxsvr bin]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:06:29:71:C4:0F
          inet addr:124.188.3.16  Bcast:255.255.255.255  Mask:255.255.240.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16096 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5296 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2146080 (2.0 MiB)  TX bytes:1175717 (1.1 MiB)

This certainly explains why I  have problems when my Laptop has obtained that 192.168.38.100 address !
but could it be the root of all my issues ?
and how do I fix it ?

Thanks

[janet]

groutley

login as admin
Select Configure this server

[groutley]

login as admin
Select Configure this server

Thanks Mary,  I have done this quite a few times now  but does not change anything

[janet]

groutley

I have done this quite a few times now....

What is it that you have done a few times ?
You should be setting up your dyndns account details (dyndns user name & password) in the Configure this server screens, and the IP should be getting automatically updated, assuming of course that you are in server gateway mode, are you in that mode ?

[groutley]

mary,
  I have performed the configure under admin log on  numerous times..
I have removed the dyndns definitions, and re added them.
Nothing helps...
My concern is the fact the server-manager shows an incorrect IP address..
If it shows up in that display, what else is that address affecting ?
i.e.  the dydns updates with wrong ip address, therfore mx record is not updated to point correctly.

I assure you I have performed configuration correctly,  even though that also appeared to carry accross correctly from the previous server hardware.
( I have also compared screen for screen, the admin configure pages, and the server-manager pages,  new to old servers and everything is identical !
The old server was happily recieving email and updating dyndns for a long time (years)
The only difference I spot which is very suspect is that "External IP address"  pointing to one of my private subnets !!

[janet]

groutley

Time to lodge a bug report

[m]

groutley,
please raise a bug in the Affa contribs section.
Post the bug number here.
Thanks.

[groutley]

Bug#:      4209  raised.

Note:  I have resolved the problem.
by performing a console /admin configure to swap the eth0 and eth1 interfaces over to each others adapters,
the problem cleaned up, and all email etc now works fine.
Subsequent configure to put the adapters back to the Desired interfaces remained resolved.
Bug open for possible investigation to why and where the rogue IP address came from.

Thanks for your help