Yet another Communication issue....
-
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
issues.
They rang in an order on the terminal, but it wasn't being seen anywhere else - not the other terminals.Can you ping the IP of the odds from an even, and vice versa?
Negative, Host is unavailable. . .
Would this be hard ware issue potentially?
Switch going out on some ports?
Sounds like maybe there is a VLAN on the switch.
Are odd and even machines both getting IPs from a single DHCP server? are they both in the same scope? Do they both use the same Default Gateway?
These are Static IPs, Same Default Gatway.
This is a Plug and Play switch - I dont believe there is a VLan on the switch.. -
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
issues.
They rang in an order on the terminal, but it wasn't being seen anywhere else - not the other terminals.Can you ping the IP of the odds from an even, and vice versa?
Negative, Host is unavailable. . .
Would this be hard ware issue potentially?
Switch going out on some ports?
Sounds like maybe there is a VLAN on the switch.
Are odd and even machines both getting IPs from a single DHCP server? are they both in the same scope? Do they both use the same Default Gateway?
These are Static IPs, Same Default Gatway.
This is a Plug and Play switch - I dont believe there is a VLan on the switch..Unplug everything from the switch except 1 odd and 1 even machine. reboot the switch, and see if pinging works.
Do these machines have internet access?
-
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
issues.
They rang in an order on the terminal, but it wasn't being seen anywhere else - not the other terminals.Can you ping the IP of the odds from an even, and vice versa?
Negative, Host is unavailable. . .
Would this be hard ware issue potentially?
Switch going out on some ports?
Sounds like maybe there is a VLAN on the switch.
Are odd and even machines both getting IPs from a single DHCP server? are they both in the same scope? Do they both use the same Default Gateway?
These are Static IPs, Same Default Gatway.
This is a Plug and Play switch - I dont believe there is a VLan on the switch..Unplug everything from the switch except 1 odd and 1 even machine. reboot the switch, and see if pinging works.
Will try and see what happens.
Do these machines have internet access?
No internet access; they go through Server
-
@JaredBusch said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
apparently, I'm not working on this call anymore or helping with the call. It came in to the other tech, but for the sake of learning , I'd be up to hearing ideas.
If Aloha is as bad as Bevo, it is probably some stupid shit like working on DNS names and not updating or something.
DNS was not resolving names...
Updated host file in all of the terminals and the server.
-
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
issues.
They rang in an order on the terminal, but it wasn't being seen anywhere else - not the other terminals.Can you ping the IP of the odds from an even, and vice versa?
Negative, Host is unavailable. . .
correction CAN Ping by IP but not by host name.
Then DNS error.
-
@scottalanmiller said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
@Dashrender said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
issues.
They rang in an order on the terminal, but it wasn't being seen anywhere else - not the other terminals.Can you ping the IP of the odds from an even, and vice versa?
Negative, Host is unavailable. . .
correction CAN Ping by IP but not by host name.
Then DNS error.
Not Windows error. Network configuration error.
-
@WrCombs said in Yet another Communication issue....:
@JaredBusch said in Yet another Communication issue....:
@WrCombs said in Yet another Communication issue....:
apparently, I'm not working on this call anymore or helping with the call. It came in to the other tech, but for the sake of learning , I'd be up to hearing ideas.
If Aloha is as bad as Bevo, it is probably some stupid shit like working on DNS names and not updating or something.
DNS was not resolving names...
Updated host file in all of the terminals and the server.
Yup, that was guaranteed from your description. If you can ping by IP, but not my hostname, that's hostname resolution errors, guaranteed. It's the only piece to fail (that or you personally got the hostname wrong.)
-
When troubleshooting on the network, always start at the bottom and work up.
Start with a ping to the IP (not the hostname.)
Then ping the hostname.
Then nslookup the hostname.These basic steps tell you what is working and what isn't. Don't hop around, use progressive testing and you'll get to answers really quickly.
-
@scottalanmiller said in Yet another Communication issue....:
When troubleshooting on the network, always start at the bottom and work up.
Start with a ping to the IP (not the hostname.)
Then ping the hostname.
Then nslookup the hostname.These basic steps tell you what is working and what isn't. Don't hop around, use progressive testing and you'll get to answers really quickly.
That's good advice,
We usually start with Aloha based issues such as the control service running on Server, any files telling it to stop, that sort of thing.
Then we move to Windows/networking. -
@WrCombs said in Yet another Communication issue....:
@scottalanmiller said in Yet another Communication issue....:
When troubleshooting on the network, always start at the bottom and work up.
Start with a ping to the IP (not the hostname.)
Then ping the hostname.
Then nslookup the hostname.These basic steps tell you what is working and what isn't. Don't hop around, use progressive testing and you'll get to answers really quickly.
That's good advice,
We usually start with Aloha based issues such as the control service running on Server, any files telling it to stop, that sort of thing.
Then we move to Windows/networking.If you know other things are working, you can move up the "stack" to where you can guarantee success. Like if you are transferring files, you know ping works.
