Hello all. We developed an app that interacts with Facebook, by posting data to a specific account. This is done by establishing an HTTP request. In my server, this works perfectly. However, when I go to out customer's, it simply won't work.
I know that this guys have very tight security measures. One of those consist on blocking anything to do with Facebook. Now, we requested that for that server and a specific account to be free of such policies. They did so, and when opening the IE, they can connect to Facebook's main page. However, our program still throws a 400 Bad Request.
So I'm wondering if there is anything else blocking such connections. To that end, I downloaded Microsoft Network Monitor 3 and SysInternals TCPView. However, neither shred a light on the situation, other than showing which connections are made.
Thus my question: is there any tool out there that can be used to trace an HTTP connection and then detect where it is being blocked either by a policy or by a firewall? Or a clue on to what could be happening?
Wireshark[^] will show you what's happening "on the wire". If it's local policy, you won't see anything. If it's a firewall, you'll see the 400 coming back. A clue to where it came from would be in the response time - the faster the response, the closer the rejection.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Previously I thought that the difference between pressing the [Del] key alone and the combination [Shift][Del] is that the former one puts the file to the recycle bin, and that's all of the differences. But no, there is more: I changed the access rights to a file programmatically such that only SYSTEM can access it (OK, there is an inconsistency left: I am still the owner of that file). When I look at its properties, only SYSTEM is shown on the Security tab. When I press the [Enter] key, Notepad is started and tries to open the file, and shows an Access Denied message. When I press [Del], the Access Denied message is shown after a few seconds. But when I press [Shift][Del], the file gets deleted immediately. Happens both in Windows XP and Windows 7. How can that be explained?
Ok, maybe some cleverer people than myself can help with this one. We have a business-critical application which runs with a MSSQL backend and generates a lot of documents (letters, etc., in Word and PDF format). At present the documents are just stored in a share on the same server as the database, with the filenames stored in a table and the documents called directly from the application on client computers when requested (I didn't design this, by the way!).
A little while ago, due to storage space issues on the server, I decided to move the documents off the server and onto a dedicated NAS (Netgear ReadyNAS 2100) with lots of capacity rather than just beef up the server's disk space. My reasoning was that the network load would be spread between the server and the NAS, instead of the server's NIC handling both database and document traffic. In practice, the performance of opening documents actually decreased dramatically for those departments which I migrated to the NAS, to the point where I halted the migration. Sometimes documents on the NAS open perfectly quickly, and a user will have no speed issues for several minutes or hours. Then, suddenly, one file will take literally a minute or more to open. These are only small Word documents and I'm only talking about a few dozen users who have been migrated.
ANYWAY, what I'm getting to is that it's time to replace all of this hardware anyway. I'm about to purchase a very powerful, fast server to replace the DB server. Reviews suggest that its I/O performance is exceptional. But I was also going to purchase a new, high-performance NAS and stick with the topology I've already described. My theory is that the speed issues are being caused by some deep-level communication problem between the Netgear ReadyNAS and the clients, which neither they nor I have been able to get to the bottom of. It still seems like sound reasoning to me that separating database and documents will result in a spread network load and increased performance. Am I wrong?
I don't know the technicalities involved in opening a document in a network share. Is it perhaps the case that the process of establishing a connection to the share and opening a file, at least the first time in a session, is much slower than opening the same file stored on the database server, to which a 'connection' is already established due to the user having been using the database?
Any discussion or advice on this topic would be greatly appreciated. If stuffing the database server full of disks and keeping the files on there is going to be the fastest solution, I'll save a whole lot of money!
Hi, i am going to use Wayne nucleus point of sale machine and i am developing my own back office system to manage data from this POS. is there any documentation on how do i configure my back office system with Wayne nucleus point of sale or it will be more convenient if someone can give me a link to Wayne nucleus technical support team via any email address or phone number. thnx.
Yesterday I ran into a oddity that might be handy for some folks.
Recently a SCADA system PC crashed on me, one which we purchased fully integrated and with no documentation. I bought a new Win7 box to replace it, recovered the hard drive, and copied all the files I thought looked related to the SCADA system. I called the manufacturer, but they refused to talk to me, and insisted that the licensing and configuration had to be done by the company that integrated the thing for us. After much haggling, I finally got that outfit to consent to 30 minutes of telephone support.
In the course of setting things up, one of the tasks required was to add a System DSN used to establish ODBC connections to the .mdb database used by the SCADA product, so I opened up the usual ODBC Sources applet in Control Panel. Surprisingly, only SQL Server was installed and available for use - no other drivers were listed. I've never seen that in a Windows system before.
After much gnashing of teeth and rending of clothing, the support guy stumbled on a link somewhere that suggested running an obscure program located at C:\Windows\SysWOW64\odbcad32.exe. I don't know where he found it, but running it produces a ODBC Sources applet identical to the one reached through Control Panel, but containing all the usual sources. From that point on, it was an easy setup, but I would never in many years have found that ridiculous hidden tool.
No I have to wonder, what other missing functionality is hidden in this folder? Any other hints?
I remember reading an article about it a few years back. There were some more examples besides ODBC that was hidden the same way, can't remember which ones though. It seems that when Microsoft drops support for a product (in this case ODBC) they don't actually drop it immediately, they just make it "invisible" for developers so that they won't use it for new products. But they remain available, with some tweaking, for a couple of versions so that they don't lose sales to people in exactly your situation.
Ahh, that's the 32 bit ODBC manager. Basically, on a 64 bit machine, you can have 64 bit and 32 bit ODBC drivers installed. The normal place to look for the drivers is in the 32 bit version, but the actual ODBC applet that runs is the 64 bit one. This is why I have a shortcut to odbcad32 on my desktop.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington