Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 1 subscriber
  • Views 60991 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

problem with connected computer not showing as connected

Jvuz

Hello,

I'm having a problem with one of our machines. It is connected, but doesn't show as connected in the console. The firewall isn't on and I can ping the ip-address. And it seems the machine is till doing his update, probably via the sophos server (I set it up to be the second update server) instead of our server. What could it be?

Jo

:13235


This thread was automatically locked due to age.
Parents
  • 0

    Hello Jo,

    thanks for the log. Unfortunately I don't know what's causing the CORBA/NO_PERMISSION:1.0 error reported.

    Some observations though:

    The client first unsuccessfully searches for PC20-121.RBINS ( which is not a valid FQDN). You might want to reassess you mrinit.conf. Might be that a reverse lookup of your server's address resolves to this name among others, but it doesn't seem to be valid. Anyway the client then tries the NetBIOS name and succeeds in getting the IOR (with the expected 192.168.20.121 as first address).

    Do all your PCs have the 192.168.xxx.1 addresses and is their name also resolving to these? It looks somewhat strange. If your working PCs have a similar line (Local IP addresses: 192.168.20.xxx 192.168.56.1 192.168.226.1 192.168.253.1 ) in their router logs then this should not be the cause of the problem though.

    Could you please also post the client's ClientMRInit-yyyymmdd-hhmmsss.log from %windir%\TEMP and the MRInit.conf? Can't say it will help but it's worth a try.

    Christian

    :13301
Reply
  • 0

    Hello Jo,

    thanks for the log. Unfortunately I don't know what's causing the CORBA/NO_PERMISSION:1.0 error reported.

    Some observations though:

    The client first unsuccessfully searches for PC20-121.RBINS ( which is not a valid FQDN). You might want to reassess you mrinit.conf. Might be that a reverse lookup of your server's address resolves to this name among others, but it doesn't seem to be valid. Anyway the client then tries the NetBIOS name and succeeds in getting the IOR (with the expected 192.168.20.121 as first address).

    Do all your PCs have the 192.168.xxx.1 addresses and is their name also resolving to these? It looks somewhat strange. If your working PCs have a similar line (Local IP addresses: 192.168.20.xxx 192.168.56.1 192.168.226.1 192.168.253.1 ) in their router logs then this should not be the cause of the problem though.

    Could you please also post the client's ClientMRInit-yyyymmdd-hhmmsss.log from %windir%\TEMP and the MRInit.conf? Can't say it will help but it's worth a try.

    Christian

    :13301
Children
No Data