3com NBX Off-site notification not working with internal Exchange server
We have a 3com NBX phone system on the same network as a SBS 2003 (fully patched) server. The off-site notification for our company e-mail will not work with Exchange because it uses the Public IP address for the URL (ex., mail.mycompany.com) of our company when trying to send the off-site notifications. We have watched the traffic and we see the public IP no matter what we set the NBX SMTP information too. We have talked with 3com but they do not understand how Exchange and Public verses Priviate IP's are handled on a network. We have IIS web servers that can send local e-mail, all-in-one copiers, etc. and all work fine with the SMTP.
Last Comment
How is the NBX getting the public IP address? Do you not have internal DNS that resolves to the internal address? Are you allowing relay?
ASKER
How is the NBX getting the public IP address?
It converts the SMTP Domain Name to the outside IP address whether you use mycompany.local or mycompany.com
Do you not have internal DNS that resolves to the internal address?
Yes, we have internal DNS that resolves to the internal address.
Are you allowing relay?
Yes we are allowing relay through SMTP
Here are the fields that the NBX has:
Host Name: NBX Name
SMTP Domain Name: mail.mycompany.com or mydomain.local (neither works)
IP Address: internal NBX IP
Default Gateway: Router IP
Subnet Mask: 255.255.255.0
Primary DNS: internal DNS server IP
Secondary DNS:
Tertiary DNS:
It converts the SMTP Domain Name to the outside IP address whether you use mycompany.local or mycompany.com
Do you not have internal DNS that resolves to the internal address?
Yes, we have internal DNS that resolves to the internal address.
Are you allowing relay?
Yes we are allowing relay through SMTP
Here are the fields that the NBX has:
Host Name: NBX Name
SMTP Domain Name: mail.mycompany.com or mydomain.local (neither works)
IP Address: internal NBX IP
Default Gateway: Router IP
Subnet Mask: 255.255.255.0
Primary DNS: internal DNS server IP
Secondary DNS:
Tertiary DNS:
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Yes, several times on three separate network setups and we have worked with 3com (submitted the traffic using Wireshark) on the logs with no luck. On another network setup with Cisco phone system no issues with their system talking to the Exchange server. It is a 3com related problem and just trying to find someone with 3com and Exchange knowledge.
I have implemented over a hundred NBX systems and integrated with Exchange on quite a few of those. Not an exchange expert per se but have never had the issues you are describing.
In the capture - what address is the DNS server responding with?
I understand you are a little frustrated but personally I would not rule out issues other than the NBX yet.
Which version of NBX software are you running? Were you with first level support with 3Com?
In the capture - what address is the DNS server responding with?
I understand you are a little frustrated but personally I would not rule out issues other than the NBX yet.
Which version of NBX software are you running? Were you with first level support with 3Com?
ASKER
NBX version: R6_0_49
The NBX is showing in the Wireshark scan:
907 17.854497 192.168.1.190 192.168.1.100 DNS Standard query MX mydomain.com
916 17.993605 192.168.1.100 192.168.1.190 DNS Standard query response MX 10 mail.mydomain.com
Host Name: NBX_Name
SMTP Domain Name: mydomain.local (recommended by 3com)
IP Address: 192.168.1.190
Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.100
Secondary DNS:
Tertiary DNS:
The NBX is showing in the Wireshark scan:
907 17.854497 192.168.1.190 192.168.1.100 DNS Standard query MX mydomain.com
916 17.993605 192.168.1.100 192.168.1.190 DNS Standard query response MX 10 mail.mydomain.com
Host Name: NBX_Name
SMTP Domain Name: mydomain.local (recommended by 3com)
IP Address: 192.168.1.190
Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.100
Secondary DNS:
Tertiary DNS:
OK - I see your DNS server is responding - What address is it responding with though? 192.168.1.X or the external address?
ASKER
In addition:
All User Configuration groups CoS is checked for off-site notification
In the System-Wide Settings > System Identity I changed url to: http://nbx/sec_cont/urlindex.htm and changed the task_settings to "enabled"
All User Configuration groups CoS is checked for off-site notification
In the System-Wide Settings > System Identity I changed url to: http://nbx/sec_cont/urlindex.htm and changed the task_settings to "enabled"
OK - what about the earlier question?
Also - COS also has to be enabled under NBX Messaging/Offsite Notification
Also - COS also has to be enabled under NBX Messaging/Offsite Notification
And for the user - so in 3 places
ASKER
What address is it responding with though?
We have tried it two ways:
1. Responding with the public IP address of the MX record
2. Responding with the private IP address of the MX record
NBX Messaging/Offsite Notification is enabled
User: Enable offsite notification for all messages is set
We have tried it two ways:
1. Responding with the public IP address of the MX record
2. Responding with the private IP address of the MX record
NBX Messaging/Offsite Notification is enabled
User: Enable offsite notification for all messages is set
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Also - what are you seeing in your NBoss logs? Did tech support have you enable extra logging for SMTP?
ASKER
Off-site notification is in the first slot and it is the only one. We can use other e-mail such as Yahoo e-mail and it will work, just not our internal e-mail. I have tried putting the off-site notification in the second slot with the internal e-mail and no luck.
Solution after all this with 3com was setting an internal MX record into the DNS of the server. Also, the e-mail addresses must be user@mydomain.local and the SMTP on the 3com must be set to:
SMTP Domain Name: mydomain.local
I would like to thank both of you for all the help and will split the points.
Solution after all this with 3com was setting an internal MX record into the DNS of the server. Also, the e-mail addresses must be user@mydomain.local and the SMTP on the 3com must be set to:
SMTP Domain Name: mydomain.local
I would like to thank both of you for all the help and will split the points.
ASKER
To sum it all up here is what we had to do:
3com NBX settings:
System-Wide Settings > IP Settings (on NBX v3000)
Host Name: NBX_Name
SMTP Domain Name: mydomain.local
IP Address: 192.168.1.190
Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.10
Secondary DNS:
Tertiary DNS:
NBX Messaging/Off-site Notification is enabled
Users: Enable off-site notification for all messages is set
All User Configuration groups CoS is checked for off-site notification
In the System-Wide Settings > System Identity I changed url to: http://nbx/sec_cont/urlindex.htm and changed the task_settings to "enabled"
E-mail addresses for users must be user@mydomain.local in their off-site notification
Microsoft settings:
There must be an internal MX record set to mydomain.local
Exchange System Manger needs SMTP relay for NBX IP address
3com NBX settings:
System-Wide Settings > IP Settings (on NBX v3000)
Host Name: NBX_Name
SMTP Domain Name: mydomain.local
IP Address: 192.168.1.190
Default Gateway: 192.168.1.1
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.10
Secondary DNS:
Tertiary DNS:
NBX Messaging/Off-site Notification is enabled
Users: Enable off-site notification for all messages is set
All User Configuration groups CoS is checked for off-site notification
In the System-Wide Settings > System Identity I changed url to: http://nbx/sec_cont/urlindex.htm and changed the task_settings to "enabled"
E-mail addresses for users must be user@mydomain.local in their off-site notification
Microsoft settings:
There must be an internal MX record set to mydomain.local
Exchange System Manger needs SMTP relay for NBX IP address
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
