OK, so I've been on the horn with my company IT for going on 3 months. Yesterday we had a sort of breakthrough in that we know where the packets are going.
Cliffs notes:
I'm in Massachusetts. My company's Data Center is in California. I remote into a server in California, and that server has an application that needs to connect to a printer in Missouri.
In Massachusetts, I dial into the server.
In the application, I put the IP address of the printer I want to connect to, and it comes back with a generic can't find message.
The IT guy runs sniffers and tracert and all that geeky stuff, and come to find out when I go to connect to the IP addy of the printer, it's going to a totally different IP addy. Why? Nobody knows.
Yesterday's breakthrough - come to find out that the mystery IP is actually my workstation here in Massachusetts!
Question - has anyone seen this behavior?
RDP into server, application sends packets to the wrong IP addy, which is the workstation I'm on.
?
Cliffs notes:
I'm in Massachusetts. My company's Data Center is in California. I remote into a server in California, and that server has an application that needs to connect to a printer in Missouri.
In Massachusetts, I dial into the server.
In the application, I put the IP address of the printer I want to connect to, and it comes back with a generic can't find message.
The IT guy runs sniffers and tracert and all that geeky stuff, and come to find out when I go to connect to the IP addy of the printer, it's going to a totally different IP addy. Why? Nobody knows.
Yesterday's breakthrough - come to find out that the mystery IP is actually my workstation here in Massachusetts!
Question - has anyone seen this behavior?
RDP into server, application sends packets to the wrong IP addy, which is the workstation I'm on.
?
via International Skeptics Forum http://ift.tt/1UVu1xS
Aucun commentaire:
Enregistrer un commentaire