Messenger service, issues on startup...

bluetech · 22 Mar 2007 at 21:51

OK, this is a good one:

1) start > run > services.msc > messenger > automatic > start (applied on PC "A "and PC "B")

2) PC A "net send (PC "A") test" - Works fine

3) PC A "net send (PC "B") test" - Works fine

4) PC B "net send (PC "B") test" - Works fine

5) PC B "net send (PC "A") test" - Works fine

6) Restart PC "A" and PC "B"

7) Check service "messenger" through start > run > services.msc > messenger service is started and set to automatic

8) Repeat steps 2 - 5 however none work

9) start > run > services.msc > messenger > stop > start (applied on PC "A "and PC "B")

9) Repeat steps 2 - 5, working fine

Why does the service not work when it clearly states in services.msc the service in running and require a stop / start to work >>> ???

I know I could write a batch to run on startup but I would rather the service just "work". Any ideas?

I am creating a simple batch to work as a messenger between two PC's instead of shouting to the other person across the hallways. Here is the code (works a treat) :

Code:

@echo off
set /p choice=Enter Message:
echo.
echo Please Wait, Sending Message...
net send (NETBIOS NAME HERE WITHOUT BRACKETS) %choice%

Thanks guy's. Your help will be appreciated...

The_KiD · 23 Mar 2007 at 08:57

Does anything appear in event viewer ?

bluetech · 23 Mar 2007 at 13:18

The_KiD said:
Does anything appear in event viewer ?

I will check that later today and give you an update. Any other ideas?

Thanks for your response.

Dr_Evil · 23 Mar 2007 at 13:23

allow messenger communication through group policy.

check your firewall

Voo · 23 Mar 2007 at 13:24

If it was GPO, it wouldn't allow messenger communication at all.

bluetech · 23 Mar 2007 at 13:33

Dr_Evil said:
allow messenger communication through group policy.

check your firewall

Firewall is good as if the firewall was blocking it. It wouldent allow the communication success in the first instance.

How do I allow it through group policy? Havent done this before.

Voo said:
If it was GPO, it wouldn't allow messenger communication at all.

So the group policy part dosent matter in this circumstance?

Dr_Evil · 23 Mar 2007 at 13:35

GPO settings overrule firewall settings.

on the server, manage group policy objects.

bluetech · 23 Mar 2007 at 19:16

Dr_Evil said:
GPO settings overrule firewall settings.

on the server, manage group policy objects.

There is no "server", just two Home PC's running Microsoft Windows XP Home SP2.

Why is it that they work when the service "messenger" is stopped and then started (lasts the whole session) and then once restarted, not work. Even though it cleary states in services.msc that it is. And then works once again when the service on both PC's is stopped / started?

Very strange if you ask me. Must be a reason for it.

Dr_Evil · 26 Mar 2007 at 10:14

bluetech said:
There is no "server", just two Home PC's running Microsoft Windows XP Home SP2.

Why is it that they work when the service "messenger" is stopped and then started (lasts the whole session) and then once restarted, not work. Even though it cleary states in services.msc that it is. And then works once again when the service on both PC's is stopped / started?

Very strange if you ask me. Must be a reason for it.

Maybe that's the reason - as your PC's are not in the same Domain, security prohibits from the messages to be received...

bluetech · 28 Mar 2007 at 01:04

Dr_Evil said:
Maybe that's the reason - as your PC's are not in the same Domain, security prohibits from the messages to be received...

If this is the case. Then why do they initially send? We are in the same "workgroup".

Dr_Evil · 28 Mar 2007 at 10:11

I'm in a windows domain here, using a SBS, and the net send command runs properly and it looks as if the messages have been sent, but they never arrive.