WebSphere Edge Server - Problems with DNS resolution of Edge server's name

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Edge Server > January 2004 > Problems with DNS resolution of Edge server's name





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Problems with DNS resolution of Edge server's name
news.software.ibm.com

2004-01-19, 3:02 pm

We have the following configuration installed:

- 2 X Windows 2K servers with Edge Server 4.0 with the Load Balancing
(Network Dispatcher v. 4.x) components installed.

Currently the Load Balancing (we have two servers in load balancing ) is
operating successfully and the users are
able to work on the application server cluster without any problems.

The problem:

it's no possible to call by browser the cluster server using his URL (i.e if
my cluster sever url is http://myserver, I
cannot call it by browser, I must use his IP address i.e
http://xxx.xxx.xxx.xxx), but if I call directly one server (a server in load
balancing) directly by his url, it works.
If I do a ping from every workstation in the LAN using IP address of my
cluster sever, I receive by DNS his network name.

Is there someone that could explain to me this problem?
Thank you.
Gennaro


JLee

2004-01-19, 3:02 pm

What happens when you run 'nslookup <mycluster>' from the client? Does
that resolve to the cluster IP address correctly? Do users go through a
proxy or something in between the client and the Dispatcher?

Jeff

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com