A machine came in with an empty Network Connections window - not even an "add a new connection" object. After some google searches, most of the time this goes along with the empty device manager issue. Not this time. Device manager was fine & showed two devices.
Solution: After trying a number of things on the web (reinstall sp3, netsh winsock reset & registering those three net dll's) what fixed it was simply uninstalling the network devices from device manager & letting it find them again. Then they showed up in network connections with the other expected objects.
Tuesday, May 18, 2010
Monday, May 10, 2010
The Same Machine Security Identifier SID
We were provided a number of Server 2008 boxes. They were able to join a domain, but you couldn't authenticate using domain credentials into the server.
The log contained this message:
The computer or domain SERVERNAME-APP trusts domain DEV. (This may be an indirect trust.) However, SERVERNAME-APP and SERVERNAME have the same machine security identifier (SID). NT should be re-installed on either SERVERNAME-APP or SERVERNAME.
Assess - obtain psgetsid from the sys internals sites then run it on both servers. This should confirm both systems have the same SID.
Resolve - http://www.brajkovic.info/windows-server-2008/windows-server-2008-r2/how-to-change-sid-on-windows-7-and-windows-server-2008-r2-using-sysprep/ has very clear instructions on how to run SYSPREP (included in 2008).
After sysprep I had to:
The log contained this message:
The computer or domain SERVERNAME-APP trusts domain DEV. (This may be an indirect trust.) However, SERVERNAME-APP and SERVERNAME have the same machine security identifier (SID). NT should be re-installed on either SERVERNAME-APP or SERVERNAME.
Assess - obtain psgetsid from the sys internals sites then run it on both servers. This should confirm both systems have the same SID.
Resolve - http://www.brajkovic.info/windows-server-2008/windows-server-2008-r2/how-to-change-sid-on-windows-7-and-windows-server-2008-r2-using-sysprep/ has very clear instructions on how to run SYSPREP (included in 2008).
After sysprep I had to:
- connect via console
- click US
- provide host name
- activate it
- take it out of the domain it was in, reboot
- re-join to the domain, reboot
Tuesday, May 4, 2010
Zip compress or tar on linux or checkpoint secure os
Question: How can you compress many date named log files on a checkpoint server to archive them?
Answer: tar -cf 2009-04-fw.tar 2009-04* --remove-files
We've been zipping & izarc'ing for years and never interacted with something like tar on SecureOS. We thought we didn't run the command right when it came right back, but sure enough, it was done that quickly.
Tried zip, gzip and finally ended up trying tar. Worked like a charm.
Answer: tar -cf 2009-04-fw.tar 2009-04* --remove-files
We've been zipping & izarc'ing for years and never interacted with something like tar on SecureOS. We thought we didn't run the command right when it came right back, but sure enough, it was done that quickly.
Tried zip, gzip and finally ended up trying tar. Worked like a charm.
Subscribe to:
Posts (Atom)