"blomm" <bl**********@no-mx.msusenet.com> wrote in message
news:bl**********@no-mx.msusenet.com...
This is probably more of a SQL server issue, but its also .net related I
think... I have the client side of my application installed in the US,
with the application and the database servers running in london.
The program language is C#, all built in visual studio.
When the user in the US runs the program and it gets to the import
progress part, they are getting no feedback as to the progress of the
import. ie, nothing is being sent to the US from the london server.
But everything runs smooth the other way, ie, tables are written to the
sql db's in london etc... And I get data sending and receiving here in
london when i run the client app on my machine and send to the servers,
so its some problem with the connection with the US.... anyone come
across anything like this?
Cheers mike
Hi Mike,
I don't know your app at all, so I don't know what you mean by
"it gets to the import progress part"
I infer that you have some kind of upload or background processing going on
and that you want to see a progress bar.
It is quite possible that the progress bar is implemented with a
"side-channel" type of operation. Perhaps the progress bar control is
sending requests for the value to display but it is not getting a response
from the London server? That sounds likely. If so, take a close look at
your progress bar control. Does it use HTTP to communicate to a page on the
London server that returns this value? Does it use port 80? If the answer
is 'no' to either question, then it is very very likely that you have a
firewall (either in your USA ISP or your London ISP) that is blocking the
traffic on the grounds that it is not HTTP over port 80 and is therefore
probably a virus.
You can monitor TCP/IP traffic using a variety of tools (assuming you are
sitting on the console of the web server itself or are connected via
Terminal Services). Some of these tools are open source, others cost money.
I won't recommend a specific tool. However, using a traffic monitoring
tool, you should have no difficulty 'seeing' the packets that carry the
status information on the London server, and 'seeing' the broken
communication on the USA server.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--