Hi,
let me rephrase my question.
What could be the reason, that an .exe application, started from the local harddisk, is able to send UDP packets, and _the_same_ application, started from a remote network share, is not?
Any help would be appreciated.
Ryan
Hi,
@TorrentG
tried context-menu of remote .exe file | properties | Compatibility: was not able to set Compatibilty mode permanent (everything greyed out), because app is on a network drive )):-(
tried context-menu of remote .exe file | deal with Compatibility problems (third menu entry from...
Hi,
here is the popup; well, not the real popup. I copied and paste it from somewher, but to give You an idea its OK I think.
I know this Security warning already from XP machines, but on XP machines the started program behaves normally (UDP port wise)
Link Removed due to 404 Error
Ryan
Hi,
I have additional information concerning my case, which I have not mentioned before:
The Client App (the .exe file), which searches for the remote licensing server is located on a remote machine, which I acces via a share.
So I start an .exe program from an remote location (there pops up...
Hi,
thanks, but is there something else I can do, to nail down the problem? Why make the debug-environment more complex, than it is already?
The question for me is, wether a Windows 7 Host (and not a virtual machine running XP) can send high port UDP packets, and what I need to do for that...
Hi,
I have an application running, where the clients contact a licensing server via UDP port 3047.
The Clients run on Win2000, WinXP Prof. Everything works.
Installed a Client on a Win7 box, tried to contact licensing server, no success.
With tcpdump on the Serverside I see about 50 UPD...
antivirus
application
client
connectivity
dns
firewall
licensing
network
packet loss
ports
server
tcpdump
troubleshooting
udp
win2000
windows 7
windump
winxp