| Author |
Topic |
|
Norwich
Posting Yak Master
158 Posts |
 Posted - 2006-01-23 : 09:01:57
|
| HiWhen I run the "xp_cmdshell" and the "Net Send" Command from QA on the Production Server it says that the "Command Completed" but I never get the Net Send. When I try the same Proc from the Dev server I receive it. What configs could create this devilish behaviour??? RegardsNIf you want your computer to be faster then throw it out of the window. |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-01-23 : 09:06:58
|
| Are you sending 'across 2 different domains'? The "NET SEND" command doesn't wait for messages to be delivered. Maybe you need to prefix the recipient username with it's domain name. Does the NET SEND work 'manually' on each server? |
 |
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-23 : 09:17:03
|
| The servers are in the same domain and it stopped working after a the Production Box was started but the Boys inthe basement (network eng) don't seem to know what they did. Prefixing the Name and Domain don't seem to work eitherNIf you want your computer to be faster then throw it out of the window. |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-01-23 : 11:25:53
|
| Have you taken QA out of the equation...ie by running the NET SEND direct at a command prompt on the production server? If it doesn't work it's NOT a SQL problem. If it does work, then it's SQL/SQL Security(permissions) related. |
|
|
|
Srinika
Master Smack Fu Yak Hacker
1378 Posts |
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-24 : 01:38:37
|
quote:
...ie by running the NET SEND direct at a command prompt on the production server?
That's doesn't seem to work either - Thanks.So it's not a SQL Problem!quote:
Check :http://support.microsoft.com/default.aspx?scid=kb;en-us;839018
It's a win 2000 box and the Messenger service is running and it's on Automatic.Anything else I should look out for?If you want your computer to be faster then throw it out of the window. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-01-24 : 02:18:41
|
| firewall restrictions?--------------------keeping it simple... |
|
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-24 : 02:32:54
|
| Would that be a factor if we are running in the same domain?If you want your computer to be faster then throw it out of the window. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-01-24 : 03:39:08
|
| i don't know in your case, but from previous experience, the network guys were able to setup individual firewalls producing what they call "sub domains", the workstations/servers are on the same domain but they are restricted to each other depending on a need basis to connect to each otherHTH--------------------keeping it simple... |
|
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-24 : 03:46:45
|
| That might be the case.I've tried everything including calling MSI guess I will have to work on a Work-Around SolutionNIf you want your computer to be faster then throw it out of the window. |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2006-01-27 : 08:42:26
|
quote:
Originally posted by Norwich
That might be the case.I've tried everything including calling MSI guess I will have to work on a Work-Around SolutionNIf you want your computer to be faster then throw it out of the window.
Have you tried:"NET SEND * TEST" or"NET SEND [WORKSTATION NAME GOES HERE] TEST" Daniel, MCP, A+SQL Server DBAwww.dallasteam.com |
|
|
|
Norwich
Posting Yak Master
158 Posts |
Posted - 2006-01-27 : 10:57:02
|
| It's some config on the box that we can't seem to figure out.I've decided to the Email route insteadNThe revolution won't be televised! |
|
|
|
|
xp_cmdshell + Net Send