Net Send Problem... Wrong recipient!?

  • Thread starter Thread starter JM
  • Start date Start date
J

JM

My app sends Net Send messages to a user when an application process fails.
The intended recipient is receiving the messages as expected, the problem is
that another user, who is not supposed to get the messages, is also
receiving the messages. He is irritated, and wants them stopped.

The Net Sends are originating from Win2k Advanced Server - SQL Server. They
are being sent to the user's domain login like this "bjohnson". The login
of the guy who's getting them (who shouldn't be) is "jsmith". I also
checked their machine names, and they are both the same as their logins..
bjohnson and jsmith, respectively.

Any ideas on what to look at? Is this a network problem?

Thanks! JM
 
Hi Phillip,

No, I thought of that, but that isn't the case. Any other ideas? Could
there be wires crossed on the network somehow?

Thanks,

JM


Phillip Windell said:
Is one of those machines a clone of the other (like done by Norton Ghost)?

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

JM said:
My app sends Net Send messages to a user when an application process fails.
The intended recipient is receiving the messages as expected, the
Click to expand...
problem
is
that another user, who is not supposed to get the messages, is also
receiving the messages. He is irritated, and wants them stopped.

The Net Sends are originating from Win2k Advanced Server - SQL Server. They
are being sent to the user's domain login like this "bjohnson". The login
of the guy who's getting them (who shouldn't be) is "jsmith". I also
checked their machine names, and they are both the same as their logins..
bjohnson and jsmith, respectively.

Any ideas on what to look at? Is this a network problem?

Thanks! JM
Click to expand...
Click to expand...
 
JM said:
Hi Phillip,

No, I thought of that, but that isn't the case. Any other ideas? Could
there be wires crossed on the network somehow?
Click to expand...

No, ethernet is all one "logical" wire. Machines aren't identified by the
"wire". I would recommend you not use machine names that match user names. I
don't know anyone who does that, but I'll just betcha there will be problems
with that. Use their job title or something, then you don't have to change
it if the person leaves and is replaced. I have started using the machine's
serial number for the machine name,...makes it much more difficult for a
hacker to know what machine they are dealing with if they get in.

But as far as a specific solution,...I really don't know right now.
 
Back
Top