Topic: Name Resolution Problem

[Kevin]

I have a problem with resolution. Everything works fine within my local private net but I also am WAN attached to another leg of our company. We each have our own Windows domains and there is a two-way trust relationship set up.

The clients on my side point to the Mitel Firewall as their gateway and dns server. But I hand DHCP out from my PDC on the windows domain. They get their WINS info from that machine which also is aware of all of the WINS info on the WAN connected lan.

So from a command promt, I can for example PING OPSWEB and it will resolve and ping and a trace shows that it takes the proper route. However, if I try to use a web browser and type http://opsweb/ (which is a legitimate intranet web server) I get the response:

The requested URL could not be retrieved
While trying to retrieve the URL: http://opsweb.tti.net/

The following error was encountered:
Unable to determine IP address from host name for opsweb.tti.net

The dnsserver returned:
Name Error: The domain name does not exist.

This means that:
The cache was not able to resolve the hostname presented in the URL. Check if the address is correct.

How do I stop it from tagging my local fake network on and just resolving the way that the client machines do from the command line? Even HOSTS file entries don't work. Somehow the firewall asserts itself in front of the normal resolution chain of command.

Thanks for any help,

Kevin

[Piero Lodato]

I have the same problem, I have 2 networks, each one with a SME server 5.6 U4,
both are connected via routers, I can ping the remote SME Server, if I put "http://remoteipaddress/e-smith-manager", I can see the control panel, but if I put "http://remotenameserver/e-smith-manager" I can't retrieve the control panel.

Thanks