LinuxNooB wrote:
>
> Hey Bill when you asked me to ping the sme server, my sme
> acts as server and gateway would I be pinging my main ip or
> the default gateway ip, I can ping all the ips I can ping
> the networked machines 192.168.0.65 and 192.168.0.66, default
> gateway is 192.168.0.1 and my isp is 216.***.**.*** I can
> ping all the isps. Btw from my networked machine how can I
> get into or even see the server machine where I can access
> the sme manager from a networked machine, only thing I see is
> my other networked computer not the server.. Thanks
Well, both are supposed to work, but pinging the SME's internal IP would be the simplest test (i.e. client to server, and nothing else).
You should be able to access
https://yourdomain.com/server-manager/ from anywhere on the LAN, and from external sites specified in Server Manager's "Remote Access" panel.
For computers to see each other in Network Neighborhood, they all need to be using the same workgroup name. NN is basically just convenience, as you can access any computer on the LAN via \servername also.
To figure out what's wrong, we need as much info as possible, not just "it stopped working". What does/doesn't work: local ping, \(IP address), \(servername), Network Neighborhood, http://(website IP), http://(website name), etc. As I said, my problem was that the SME's local NIC stopped completely. No connection of any type would work from the LAN, but everything worked fine from the internet. You say you can ping the SME and your ISP, but "the internet was lost to both comps"... What exactly doesn't work?
7 Replies
468 Views