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

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
  • Hello Ed_,

    feeding the IOR through http://catior.org/(thanks, Jak, for the reference) gives:

    Type ID: "IDL:SophosMessaging/MessageRouter:1.0"
    Profiles:
    1. IIOP 1.2 192.168.1.242 8193 "....NUP...!........RootPOA.RouterPersistent.........MessageRouter"
                TAG_ORB_TYPE 0x54414f00
                TAG_CODE_SETS char native code set: ISO-8859-1
                              char conversion code set: 
                              wchar native code set: UTF-16
                              wchar conversion code set: 
                
                TAG_SSL_SEC_TRANS port = 8194 supports = 166 requires = 134

     that is, the response instructs the client to connect to 192.168.1.242 port 8194. Is this the correct address for WIN

    -C3IG4ZGDGFD (i.e. ? If you telnet 192.168.1.242 8194 you should get a blank screen, wait about 10 seconds, press enter - this should quietly return you to the command prompt.

    Christian

    :42430
Reply
  • Hello Ed_,

    feeding the IOR through http://catior.org/(thanks, Jak, for the reference) gives:

    Type ID: "IDL:SophosMessaging/MessageRouter:1.0"
    Profiles:
    1. IIOP 1.2 192.168.1.242 8193 "....NUP...!........RootPOA.RouterPersistent.........MessageRouter"
                TAG_ORB_TYPE 0x54414f00
                TAG_CODE_SETS char native code set: ISO-8859-1
                              char conversion code set: 
                              wchar native code set: UTF-16
                              wchar conversion code set: 
                
                TAG_SSL_SEC_TRANS port = 8194 supports = 166 requires = 134

     that is, the response instructs the client to connect to 192.168.1.242 port 8194. Is this the correct address for WIN

    -C3IG4ZGDGFD (i.e. ? If you telnet 192.168.1.242 8194 you should get a blank screen, wait about 10 seconds, press enter - this should quietly return you to the command prompt.

    Christian

    :42430
Children
No Data