This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems Accessing SSVM Logs Share

Is anybody else having trouble getting into the logs share on the new SSVM?

At first I thought I maybe I'd mistyped the password during the setup, but I can log onto the Security VM console using Sophos / password without any problems.  I've gone through every variation of the username that I can think of .\sophos, HOSTNAME\sophos, IPADDRESS\sophos, sophos@IPADDRESS, sophos@HOSTNAME all with no success.



This thread was automatically locked due to age.
Parents
  • As long as the networking exists, you should be able to open file explorer (I was originally trying this from my web browser and it obviously wasn't working) from the applicable location and use \\IPADRESSOFSVM and that should take you to log folder location. You will then use the username:sophos and the support password that you configured during the SVM install. The key is to make sure the location you are using file explorer from can access the SVM, I would confirm with ICMP if you have that enabled on your network. 

Reply
  • As long as the networking exists, you should be able to open file explorer (I was originally trying this from my web browser and it obviously wasn't working) from the applicable location and use \\IPADRESSOFSVM and that should take you to log folder location. You will then use the username:sophos and the support password that you configured during the SVM install. The key is to make sure the location you are using file explorer from can access the SVM, I would confirm with ICMP if you have that enabled on your network. 

Children
  • I can browse the SSVM in File Explorer, get into the Public folder without any problems.  It's when I try to get into the log folder that it's not accepting the credentials however I try to input then.  As I said I know the password is correct as I can use it to log into the console of the SSVM, it's only when I'm trying to get into the Logs folder that I run into issues.