"Jason Saidoo" wrote:

> SqlDependency seems to work for me just fine when I am at work and logged
> into my work domain.  I attempted to demo SqlDependency outside of the office
> and it simply would not work.  In debugging, there are zero errors, and the
> code seems to execute "SqlDependency.Start(strConnectionString)" without
> error or delay.  The onchange handler never gets called even though I've
> changed and/or added rows to the table being monitored (the same changes that
> work when I'm logged into my work domain).
>
> I've tried:
> * connecting to the database using localhost and machine name
> * connecting using windows auth and SQL Auth (both system admins and dbo)
> * using inline SQL vs. Stored Procedure
> * using very simple query (SELECT Column1 FROM dbo.Table1)
> * restoring a backup copy of the database on a Virtual PC not associated
> with a domain
> * running the test application on the above virtual PC
>
> If (while away from the office) I VPN into our network, the SqlDependency
> works perfectly.  Disconnect the VPN and the onchange handler is never called
> again. 
>
> Also, once the dependency is created, I can see a service and a queue
> created (looking in Management Studio).  I can also see messages in the queue
> that seem to never be delivered to my application.
>
> Any ideas?