View Single Post
  #46  
Old October 30th 18, 11:16 PM posted to rec.photo.digital
Eric Stevens
external usenet poster
 
Posts: 13,611
Default Got to admit; when Windows fails, it does so spectacularly.

On Tue, 30 Oct 2018 05:12:01 -0700 (PDT), Whisky-dave
wrote:

On Monday, 29 October 2018 23:42:45 UTC, Eric Stevens wrote:
On Mon, 29 Oct 2018 06:56:55 +0000, David Taylor
wrote:

On 29/10/2018 04:29, Eric Stevens wrote:
[]
Now you tell me.

I'm currently trying to make my two Windows 10 computer _each_ talk to
the other. Corsair gets on fine with Dell but rejects Dell whenever
Dell tries to talk back. The instructions on line sound as though they
were written by those guys.

Check:

Share/directory/file security
Network public/private
Network discovery
Try IP addresses rather than names


Done all that. My problem is that any attempt of Dell to contact
Corsair gets a response of "You are not authorised to ... " or words
to that effect. I've been through all the settings that I (and others)
can think of and they are identical on both machines. Yet Corsair is
succesful in contacting Dell while Dell is unsuccesful in getting a
useful response from Corsair. The problem may lie in the fact that
Corsair is W10 Home while Dell is W10 Pro.


You;re not suggesting that thgis is a Windows problem are you ?

Not at all. I've boiled it down to probably being a user name and
password problem. I hope to know later in the day. The problem is that
Windows can do so many things (sometimes in so many different ways)
that unless you know exactly what you are doing you can be brought up
short by a security barrier at almost any stage. What I now have to do
is make sure that he two computers are so configured that they can
actually talk to each other.
--

Regards,

Eric Stevens