Solved Cant communicate

[scottalanmiller]

@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.

[WrCombs]

@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.

[syko24]

@wrcombs - How is DNS setup on this network and on the machines? Are you trying to connect by IP or by NetBios name?

[WrCombs]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

[WrCombs]

@syko24 said in Cant communicate:

Are you trying to connect by IP or by NetBios name?

Ive tried Both.

[1337]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

So 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)?

[WrCombs]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

So 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.

[1337]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

So 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?

[WrCombs]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

So 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

[WrCombs]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

So 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.

[1337]

@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.

[scottalanmiller]

@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 run and using \\\192.168.128.xxx(the Back office IP) Which we can do that on every other site.
The Terminals

You 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.

[scottalanmiller]

What if you try opening from the Windows Explorer?

[WrCombs]

@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 use just as it is i get a connection to Term3, when i run net use \\alohaboh i get

System Error 53 hs occurred.
The network path was not found

[WrCombs]

@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 

[1337]

@wrcombs said in Cant communicate:

@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 use just as it is i get a connection to Term3, when i run net use \\alohaboh i get

System Error 53 hs occurred.
The network path was not found

The usage is like this:
net use <driveletter>:\ \<server>\<sharename> /USER:<domain><username> <password>

With just a workgroup you can skip the domain so it's:
net use <driveletter>: \ \<server>\<sharename> /USER:<username> <password>

PS. For details type: net use ?
I had some formatting problems with backslashes above.

[dafyre]

@pete-s said in Cant communicate:

@wrcombs said in Cant communicate:

@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 use just as it is i get a connection to Term3, when i run net use \\alohaboh i get

System Error 53 hs occurred.
The network path was not found

The usage is like this:
net use <driveletter>:\ \<server>\<sharename> /USER:<domain><username> <password>

With just a workgroup you can skip the domain so it's:
net use <driveletter>: \ \<server>\<sharename> /USER:<username> <password>

PS. For details type: net use ?
I had some formatting problems with backslashes above.

<Off Topic> You do not have to specify drive letter when using net use unless you want to mount it. </Off Topic>

Try...

net use \\192.168.128.xxx\sharename /user:username

It should prompt you for the password and then tell you whether or not it works.

Edit: This command can be run both from the POS Terminals and the Backoffice system.

[1337]

Also run the command

net share

on the back office server and post the results.
It will show you what shares and folders are shared on the server.

[WrCombs]

@pete-s said in Cant communicate:

Also run the command

net share

on the back office server and post the results.
It will show you what shares and folders are shared on the server.

[dafyre]

@wrcombs said in Cant communicate:

@pete-s said in Cant communicate:

Also run the command

net share

on the back office server and post the results.
It will show you what shares and folders are shared on the server.

Are those the shares you expect to see?