Identity Manager on Tomcat AND name resolution

The summary of the problem is this.

I have modified the "host" file on the windows machine and I can ping a host fine but the Tomcat served Sun Identity Manager test connection or any other java application will not resolve the hostname matt.base4u.com.

Your comments would be appreciated

Test connection failed for resource(s):

LDAP: Could not connect to LDAP server 'MATT.base4u.com'. ==> javax.naming.CommunicationException: MATT.base4u.com:489\n

Above is the error message that I receive when testing a connection to an LDAP server.

If I ping the hostname it resolves fine

C:\>ping matt.base4u.com

Pinging matt.base4u.com [192.168.0.103] with 32 bytes of data:

Reply from 192.168.0.103: bytes=32 time<1ms TTL=128

Reply from 192.168.0.103: bytes=32 time<1ms TTL=128

Reply from 192.168.0.103: bytes=32 time<1ms TTL=128

Reply from 192.168.0.103: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.103:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

[1177 byte] By [SavorToday] at [2007-11-26 10:50:24]
# 1

javax.naming.CommunicationException: MATT.base4u.com:489\n

is this the actual port number LDAP is running on? how about 389?

if 489 is the port, try connecting using the ip address and not the hostname to see if you can connect. If so, then you have some type of name resolution problem.

mfortune99 at 2007-7-7 3:02:59 > top of Java-index,Web & Directory Servers,Directory Servers...