Cant communicate
-
@momurda said in Cant communicate:
@wrcombs said in Cant communicate:
combination Master Terminal/BOH
There can be only one. It sounds like you have two terminals trying to be Master Terminal. Turn off the peasant terminals see if the Master returns.
Make sure SYNCTIME is not running on a combination Master Terminal/BOH Fileserver. -
Troubleshooting needs to be done in a logical manner.
You want to verify things by testing and excluding things that work.
It might take forever to find something if you do it by checking things haphazardly. -
@pete-s said in Cant communicate:
Troubleshooting needs to be done in a logical manner.
You want to verify things by testing and excluding things that work.
It might take forever to find something if you do it by checking things haphazardly.Since apparently (cause youre here right?) I didnt Troubleshoot correctly . What should I try?
-
@wrcombs Yeah this is an ongoing issue and from previous thread it does sound like he has troubleshooted logically in my opinion.
-
@wrcombs said in Cant communicate:
You might not have premissions,Contacted server Administrator to find out if you have premission
Start with, can you ping it (by IP.)
-
@scottalanmiller said in Cant communicate:
@wrcombs said in Cant communicate:
You might not have premissions,Contacted server Administrator to find out if you have premission
Start with, can you ping it (by IP.)
Yes.
-
-
Do you have windows firewall enabled on the machines? In that case disable it.
-
@pete-s said in Cant communicate:
Do you have windows firewall enabled on the machines? In that case disable it.
It is Disabled...
-
@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)?
