| Anders Gustafsson 2006-11-17, 1:11 pm |
| Austin Williams,
> I'll let you
> know if it fixes the problem.
>
Probably not, since that is a minor fix, meanwhile, this is what I got from Novell:
Well, with NetWare 6.5 there are several points of dns resolution that can
occur.
(1) The error he is receiving might just be cached. Have him clear all of
the cache in his browser and then try again. Also as a quick browser test
he can do a CNTL F5 or CNTL refresh to clear the initial cache. This might
very well be the issue.
(2) It also depends on whether or not it is Tomcat or Apache giving the
error. In this case it looks like it is Apache, but it might not help to
get a screen shot in case the other suggestions don't work.
(3) Next I would see how his server information is setup in the default
apache configuration file. Just to see if it is the IP address or not.
(4) When they ping, are they pinging from the workstation or the server? The
workstation may very well be seeing it properly but the server may not be
resolving it properly.
(5) The route that we are going from the workstation is important as well.
Are we going outside the firewall to resolve, or is the resolution
happening locally? I guess what I mean is, what is his workstations DNS
server set to? A local DNS server or an external DNS server? Same
information would help us with the dns setup on the server side.
(6) Last but not least, a quick and easy test would be to put in a local
host entry on the server and the workstation (just as a test) so that we
bypass DNS because we will hist the local host file information before
going on to DNS.
I really suspect #1 or #5
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2195
|