How far away are they? If they are closeish go there and have them try it. It won't work. Blow it out or whatever and show them that it works. Tell them to try that next time so they don't get the "to many support requests" fee. Or tell a boss that they need to have a fee put on.
I have no boss. If I tried to explain this shit to anyone else in the building I would get a blank stare as they slowly backed away.
There are roughly 216 stores. I'm not driving to each one. Its a DNS/MAC address issue with the network. Whether its a local network or corporate network issue has been the debate. The only current fix is to manually reset the ATA at the store. It fixes that store's issue but the issue can and has started up again after that was done.
My thinking is that the program running on the machine is trying to acquire a MAC address and their network is not wanting to assign one. They think the program is trying to connect to a forbidden DNS. I keep telling them that the DNS is assigned by their network but they don't want to listen to that.
I've been sitting here running the program over and over with it hooked up to a packet sniffer. I'm thinking of doing it for 8 hours straight and sending them the logs just to keep them from calling me so much. They need some busy work.
err, MAC addr are fixed. ip address are dynamically assigned.
I know they are *supposed* to be. The terminal has one, I can see it. But what if this program is trying to act as a second machine? Or what if the accessory they hook up to it to read checks has a separate MAC address? What if their network doesn't see the MAC address fast enough and rejects the request?
My theory is its something with the MAC. However I can't prove it because I don't have access to their network.
foxy, what's a good program that I can hook up to my PC to find out what IP and shit this terminal is trying to connect to?
I figure I can hook up the ethernet out from the terminal to the in on my PC
assuming you have a terminal in your lan you can test with
http://www.techrepublic.com/blog/five-apps/five-free-dead-easy-ip-traffic-monitoring-tools/
wireshark is what I've been using. I don't see any inbound requests from the terminal.
Hrmm...maybe this won't work.
you would need to have a server and a client to test the traffic no?
....and it finally happened
Someone hacked the server. Its dead.
RIP server
my bad. but it needed to go.
Pardon my ignorance, but, how? Couldn't they/you reset it? How did they permanently break it?....and it finally happened
Someone hacked the server. Its dead.
RIP server
