Forum Discussion

undejj's avatar
undejj
Level 3
16 years ago

EV not accessible from any computer other than EVServer

Hi - I'm new to these forums and I would appreciate any help you can give with this issue: We have been using Enterprise Vault ver. 7 for just over a year with Exchange Server 2003. Two days ago, I changed the IP addresses on both EVServer and SQLServer. Both servers were moved from 192.168.54.0/24 network to 10.1.3.0/26 network. The Exchange server remained on the 192.168.54.0/24 network for now, with plans to move that server to the new network within the next week. DNS - I modified DNS names for both EVServer and SQLServer to point to the new IP addresses. Nslookup on both servers and workstations was tested and resolves to the new IP addresses. Networking - There are currently no ACLs preventing the old and new networks from communicating. On EVServer, everything functions normally. I can access Enterprise Vault Administration Console and also access the vault and full archive functionality via http at evserver/enterprisevault. From any other server or workstation on either network, I cannot access the vault by browsing to http://evserver/enterprisevault. Instead of the Enterprise Vault site, a search page is displayed, just like when a web site cannot be found or a name cannot be resolved. Also, when opening an archived item from Outlook, I receive a bar at the top of the e-mail window stating, "There was an error loading this item -- some functionality may not be available." I believe the cause of this is probably the same as the previously mentioned error where I cannot access the vault via http. On first glance, this would appear to be a networking or DNS issue. But the DNS name of EVServer is resolving normally and their are no limitations on the network that would prevent communications. Another point to consider is that the IP Address of SQLServer was also changed, and there is a web site operating on that server also. The SQLServer web site is operating normally and is accessible via its DNS alias from any computer on either network. All of these points taken together lead me to believe that there may be a setting in Enterprise Vault that I am missing?
  • The issue was Windows Firewall, which was enabled on evserver and port 80 was not setup as an exception. Prior to changing the IP address on the server, everything functioned normally with evserver, so port 80 must have been setup as an exception, and then, when the IP address was changed, I guess that this setting was automatically unset? Thank you Windows !@*#% Paul and Tony, it was your questions regarding IP addresses that got me thinking about all things IP address related, and for that I thank you! It's good to bounce around ideas until something sticks.
  • what are the ping results from the user computers for evserver?

     

    If you type in the ipaddress\enterprisevault in IE does that open the search page? 

  • what are the ping results from the user computers for evserver?

     Normal .. if I ping evserver, it returns results from the new IP address

     

    If you type in the ipaddress\enterprisevault in IE does that open the search page? 

    Nope. I even tried telnet to port 80 on the evserver IP address from a workstation and no connection.

     

    Also, there are no errors in the logs on evserver or on the various computers that I have attempted connections from.


  • Sounds as though there is something amiss in IIS. On the vault server do the following:-

    1. If you goto http://localhost do you get the under construction screen?

    If so then it would appear we are good from the IIS point of view. If not then we have an IIS problem.

    2. If 1 is OK then goto http://localhost/enterprisevault If you get an error here then it would appear that it is the Virtual Directory with the problem

    3. If 2 fails then setup a dummy virtualdirectory called test for example and point it to a directory on c you created called test. Create an asp file with the hello world script you can find off the internet and see if you can run that asp file successfully.

    If you can do step 3 then we have narrowed the problem to the ev virt dir. The fact that you cannot telnet on 80 though indicates a more fundamental IP issue if you do not have telnet blocked.

    4. Check the properties of the default website and look at the IP address field. Is that set to your old IP address by any chance? I think this will be it and you need to change this to your new ip address

  • 1. If you goto http://localhost do you get the under construction screen?

     Yes.

     

     

    2. If 1 is OK then goto http://localhost/enterprisevault If you get an error here then it would appear that it is the Virtual Directory with the problem

     No error. Normal operation if browsed to from the vault server.

     

    4. Check the properties of the default website and look at the IP address field. Is that set to your old IP address by any chance?

    This is set to (All Unassigned) and the only other option is the new ip address of the server.

     

    There are no other web sites running on this server - the server is dedicated to EV.

    Thanks to all for your swift replies .. this one has me perplexed!

  • The issue was Windows Firewall, which was enabled on evserver and port 80 was not setup as an exception. Prior to changing the IP address on the server, everything functioned normally with evserver, so port 80 must have been setup as an exception, and then, when the IP address was changed, I guess that this setting was automatically unset? Thank you Windows !@*#% Paul and Tony, it was your questions regarding IP addresses that got me thinking about all things IP address related, and for that I thank you! It's good to bounce around ideas until something sticks.