Solved Cant communicate
-
@pete-s said in Cant communicate:
Do you have windows firewall enabled on the machines? In that case disable it.
on all machines
It is disabled (thats what i meant by Firewalls are set correctly) -
@wrcombs
Exactly which devices can't communicate with each other?
The error you mentioned above from some log, what log is that and on which machine? -
@pete-s said in Cant communicate:
@wrcombs
Exactly which devices can't communicate with each other?
The error you mentioned above from some log, what log is that and on which machine?The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
The log file is from the Back office.
And the PoS terminals can talk with each other but neither can talk to the back office. -
@wrcombs said in Cant communicate:
@pete-s said in Cant communicate:
Do you have windows firewall enabled on the machines? In that case disable it.
on all machines
It is disabled (thats what i meant by Firewalls are set correctly)That's a confusing way to state that, lol.
-
@wrcombs - Sorry if I missed this detail but do all the systems have passwords set on them? Does the back office system have a password?
-
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
-
@syko24 said in Cant communicate:
@wrcombs - Sorry if I missed this detail but do all the systems have passwords set on them? Does the back office system have a password?
Yes, Everything has passwords, Passwords are all set correctly as that was another thing that was checked.
-
@wrcombs - How is DNS setup on this network and on the machines? Are you trying to connect by IP or by NetBios name?
-
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals -
@syko24 said in Cant communicate:
Are you trying to connect by IP or by NetBios name?
Ive tried Both.
-
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsSo the POS terminals access the Back Office server by windows file sharing?
Have you tried to connect a laptop and open a network share to the back office server (by using the right IP, username and password)? -
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsSo the POS terminals access the Back Office server by windows file sharing?
Have you tried to connect a laptop and open a network share to the back office server?
No havent tried that cause im not on site, I am remoted in.
-
@wrcombs said in Cant communicate:
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsSo the POS terminals access the Back Office server by windows file sharing?
Have you tried to connect a laptop and open a network share to the back office server?
No havent tried that cause im not on site, I am remoted in.
Are the POS terminals running full windows? Can you remote to them as well?
-
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsSo the POS terminals access the Back Office server by windows file sharing?
Have you tried to connect a laptop and open a network share to the back office server?
No havent tried that cause im not on site, I am remoted in.
Are the POS terminals running full windows? Can you remote to them as well?
yes, and yes
-
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@pete-s said in Cant communicate:
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsSo the POS terminals access the Back Office server by windows file sharing?
Have you tried to connect a laptop and open a network share to the back office server?
No havent tried that cause im not on site, I am remoted in.
Are the POS terminals running full windows? Can you remote to them as well?
Can even use our VNC Viewer from the back office and get to the POS Terminals, But I cant Get to the files on Back office for some reason.
-
@wrcombs
Can you try and open the windows share on the back office server from a POS terminal?Either from the windows explorer or from the command line with "net use" etc.
-
@wrcombs said in Cant communicate:
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
The Back office can connect and talk to the POS Terminals. The Terminals Cant Connect and Talk to the Back Office.
"Can't talk to" isn't a useful term. that they can ping means that they are currently talking to each other.
You need to use a different description here, something meaningful that would involve a specific protocol.
okay: The Terminals cant Access the Back office files to pull the data they need to run correctly. our terminals are running in a stand alone state however they are on the network for troubleshooting purposes. , we cant path to the back office using
runand using\\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The TerminalsYou should simplify this for clarity.
Machine 1 is trying to access an SMB share on Machine 2.
That's it. And it is failing. That's all. All the other terms are confusing or ambiguous. Clear and concise for troubleshooting so you stay focused on the issue.
-
What if you try opening from the Windows Explorer?
-
@pete-s said in Cant communicate:
@wrcombs
Can you try and open the windows share on the back office server from a POS terminal?Either from the windows explorer or from the command line with "net use" etc.
when i run
net usejust as it is i get a connection to Term3, when i runnet use \\alohabohi getSystem Error 53 hs occurred. The network path was not found -
@scottalanmiller said in Cant communicate:
What if you try opening from the Windows Explorer?
\\{servername} is not accessible. You might not have permission to use this netowrk resource. Contact the administrator of the server to find out if you havvess permissions. the network path was not found
