Lenniey's questions

We built some servers running Windows Server 2016 out of some "spare" parts with the following specs:

• Supermicro X10DRH-iT
• Dual E5-2620 v3
• 256GB Registered ECC DDR4 RAM
• 1x Adaptec 71685 RAID controller
• 8x Intel DC S3500 80GB SSDs
• 4x Intel DC S3500 240GB SSDs
• 4x 300GB 15k SAS HDDs
• 2x OCZ RevoDrive 350 480GB
• 1x OCZ RevoDrive 350 960GB

We use these servers for high performance Oracle DB testing environments.

The problem is, that after some time (really quite random) and not under heavy load or anything, the OCZ 350 drives start to act up, flooding the Windows event logs with ocz10xx Adapter \Device\RaidPort2 received srs interrupt. and Request failed on \Device\0000004a, physical disk 2. warnings and ultimately destroying parts of the Oracle tablespace files.

In this state, the Toshiba SSD Utility tool only reports the first 480GB drive as OK, the other two are missing.

These "warnings" won't cease until we completely power off the servers, unplug the power cords, wait some time, and power them up again. The tablespace files are still corrupt then, so we have to recreate them and flash back (or reimport) the database.

All drivers and firmware etc. are up to date.

We tried setting possibly every imaginable combination regarding power, interrupts, timings, PCIe, etc. in BIOS, switching the cards to different slots, but to no avail.

Anyone got any clue what we could try? Other than dumping the hardware, if possible!

UPDATE: not solved...

The issue persists, I also tried the hardened UNC paths approach, still no luck. I'll keep updating this thread if I encounter something new.

UPDATE and solved (hopefully)

Seems like the problem was triggered by the "fast boot" option in Windows 10 (and 8.1). There even is a TechNet article describing something like it. I went and deactivated fast boot for all clients via a registry GPO (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled, REG_DWORD 0x0 (0))

Right now the network shares are mapped upon boot and reboot. I hope it stays that way.

In my environment (Server 2012 R2 domain with three DCs, all GCs) there are some issues with mapped drives via GPPs, but only with Windows 8.1 and Windows 10 clients (all updates installed).

The GPPs map 7 drives, 4 of them are on the main DC and fileserver, the other 3 on DFS shares.

If the Win8.1 / Win10 clients connect, sometimes the drives appear, but most of the time they don't. If I run a gpupdate /force via commandline all of them connect. When after some time idle the user wants to browse a share (doesn't matter if DFS or fileserver), an error pops up:

Error 0x80090006: Invalid Signature

But if they click on the drive again, all is well. I tried every possible fix I can imagine, setting the GPPs to wait for network before starting, setting the autodisconnect time on the servers to infinite via net config server /autodisconnect:-1, deleting the GPPs and starting from scratch, checking and rechecking sysvol permissions, but all to no avail.

The clients also sometimes display an error in the eventlog that no DC can be accessed, which is nonsense because all other GPOs and GPPs (printers, for example) are processed every time, only mapped drives are faulty.

Did someone encounter anything like that, too? Any tip will be highly appreciated.

UPDATE

Right after starting the client, sometimes this error appears in eventlogs (on the client), too:

Event ID 1058, GroupPolicy (Microsoft-Windows-GroupPolicy)

The processing of Group Policy failed. Windows attempted to read the file \domain.local\SysVol\domain.local\Policies{5898270F-33D0-41E8-A516-56B3E6D2DBAB}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled.

I will try and look at that.

EDIT: I tested some more...If I copy nslookup from the Windows directory to my mapped network drive, it cant' resolve hostnames:

H:\nslookup dbserver
(null)   UnKnown
Address:  192.168.0.195

If I use the default nslookup from C::

C:\>nslookup dbserver

Server:  dnsserver.dom.local
Address:  192.168.0.195

Name:    dbserver.dom.local
Address:  192.168.0.231

So it doesn't have anything to do with oracle, I'll change title and tags.

My colleagues create applications which use the installed Oracle-client to connect to remote Oracle-DBs. Running these applications from a mapped drive on DFS (on two servers) results in a successful connection. Running them from a mapped drive on another server (standalone fileserver) results in NO connection whatsoever. I traced it via Wireshark and observed that there is not even a try to establish a connection (no oracle-packets at all are exiting the client).

I disabled firewalls on the DB server, the filserver and the clients, but to no avail. All the mapped network drives (DFS and standard fileserver) have been put into the intranet zone.

If I use tnsping from my local Oracle-client installation, I can resolve the host:

OK (20 ms)

If i use tnsping placed into the mapped network drive on the fileserver, I cant:

TNS-12545: Connect failed because target host or object does not exist

To the SAME Oracle-DB.

I am at a loss here, see the failed attempt log excerpt below:

nfun2awanm: Getting the path of sqlnet.ora
nnfun2awanm: Getting the adapter name
nnfun2awanm: exit
nsmal: 216 bytes at 0x75e228
nscall: connecting...
snlinGetAddrInfo: entry
snlinGetAddrInfo: getaddrinfo() failed with error 11003
snlinGetAddrInfo: exit
nlad_expand_hst: GetAddrInfo call failed
nladini: entry
nladini: exit
nladget: entry
nladget: exit
nsmal: 89 bytes at 0x7b2c48
nsc2addr: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbserver)(PORT=1521))(CONNECT_DATA=(SID=instance)))
nttbnd2addr: entry
snlinGetAddrInfo: entry
snlinGetAddrInfo: getaddrinfo() failed with error 11001
snlinGetAddrInfo: exit
nttbnd2addr: looking up IP addr for host: dbserver
snlinGetAddrInfo: entry
snlinGetAddrInfo: getaddrinfo() failed with error 11003
snlinGetAddrInfo: exit
nttbnd2addr:  *** hostname lookup failure! ***
nttbnd2addr: exit
nserror: nsres: id=0, op=77, ns=12545, ns2=12560; nt[0]=515, nt[1]=1003, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
nsmfr: 89 bytes at 0x7b2c48
nscall: connecting...
nladget: entry
nladget: exit

In comparison to the succesful tnsping:

nnfun2awanm: Getting the path of sqlnet.ora
nnfun2awanm: Getting the adapter name
nnfun2awanm: exit
nsmal: 216 bytes at 0x31426e8
nscall: connecting...
snlinGetAddrInfo: entry
snlinGetAddrInfo: exit
snlinGetNameInfo: entry
snlinGetNameInfo: exit
snlinFreeAddrInfo: entry
snlinFreeAddrInfo: exit
nladini: entry
nladini: exit
nladget: entry
nladget: exit
nsmal: 95 bytes at 0x30f3158
nsc2addr: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.231)(PORT=1521))(CONNECT_DATA=(SID=instance)))
nttbnd2addr: entry
snlinGetAddrInfo: entry
snlinGetAddrInfo: exit
nttbnd2addr: using host IP address: 192.168.0.231
snlinFreeAddrInfo: entry
snlinFreeAddrInfo: exit
nttbnd2addr: exit
nsmal: 996 bytes at 0x3142bc8
nsmal: 2120 bytes at 0x3142fb8
nsmal: 84 bytes at 0x3143948
nsopen: opening transport...
nttcon: entry
nttcon: toc = 1
nttcnp: entry
nttcnp: exit
nttcni: entry
nttcni: Tcp conn timeout = 60000 (ms)
nttctl: entry
nttctl: Setting connection into non-blocking mode
nttcni: trying to connect to socket 564.
ntt2err: entry
ntt2err: exit
ntctst: size of NTTEST list is 1 - not calling poll
nttctl: entry
nttctl: Clearing non-blocking mode
snlinGetNameInfo: entry
snlinGetNameInfo: exit
nttcni: connected on ipaddr 192.168.0.99
nttcni: exit
nttcon: set TCP_NODELAY on 564
nttcon: exit
nsopen: transport is open

By pasting these results into serverfault, I just realized that the successful attempt can resolve the hostname via DNS, the failed one can't. So it seems it's not even Oracle-related?

This is a follow up to this question of me. (Still on Debian 7.8)

The problem isn't really IPSec related or anything, because I can't even ping the remote host with the "correct" source IP (through ping -I eth1:ipsec).

Here are the necessary infos:

inet xxx.xxx.xxx.94/24 brd xxx.xxx.xxx.255 scope global eth1
inet xxx.xxx.xxx.92/29 brd xxx.xxx.xxx.95 scope global secondary eth1:ipsec

I want my connections to use the default gw and standard IP of eth1: .94 but one connection to a remote host to use eth1:ipsec: .92.

I believe this is a routing problem, so I added a routing rule table:

0:      from all lookup local
2:      from all to xxx.xxx.xxx.21 lookup 17
32766:  from all lookup main
32767:  from all lookup default

and 17 has:

xxx.xxx.xxx.21 via xxx.xxx.xxx.91 dev eth1  src xxx.xxx.xxx.92

But even now, if I ping the packets got the source IP of .94 (even with ping -I eth1:ipsec or -I xxx.xxx.xxx.92):

xxx.xxx.xxx.94 > xxx.xxx.xxx.21: ICMP echo request, id 20865, seq 9, length 64
IP xxx.xxx.xxx.21 > xxx.xxx.xxx.94: ICMP echo reply, id 20865, seq 9, length 64

Also SNATting the packets via iptables doesn't do anything, still wrong source IP.

...I'm completely lost here.

I have 2 Windows Server 2008 R2 DNS Servers which share the domain xyz.wan and reside in the 192.168.50.0/24 subnet of my network. Connected via IPSec VPN site-to-site are some other subnets (192.168.51.0/24, .52.0/24, etc.) which have their own reverse-lookup zones in Microsoft DNS.

Recently my servers began behaving strangely by resolving ALL addresses NOT in DNS (e.g. some static client on a remote site with no DNS record) to the own name, server1.xyz.wan, instead of showing the IP in Windows-perfmon.

Now I found out, that if I do a nslookup on either one of the 2 servers and enter some IP I don't even use, like 192.168.111.111, the other server responds with "localhost".

The DNS resolving works like a charm for everything in the domain. I also traced the packets with Wireshark:

192.168.50.161  192.168.50.163  DNS 88  Standard query PTR 111.111.168.192.in-addr.arpa
192.168.50.163  192.168.50.161  DNS 111 Standard query response PTR localhost

Can someone point me in the right direction of what is going on here? I just can't figure it out.