Jim R's questions

I have been unsuccessfully trying to get NSClient to work on my 64 bit Windows 7 machine with Windows Firewall turned off.

I have tried with the service started and also tried running 'NSClient++ /test'. No difference. I have run Microsoft Network Monitor 3.4 and did a capture on port 12489. Each time I run the check_nt command from the Nagios computer, I get a "connection refused" "could not fetch information from server" response on the command line.

The network monitor shows a packed received on the NSClient machine that was sent from the Nagios machine. There is also a repsonse packet returned. Unfortunately, I do not know how to interpret the response.

For those so inclined, here are the contents of the return packet:

 0000 00 27 0E 0D 41 BF 14 DA E9 15 36 7C 08 00 45 00
 0010 00 28 0A DB 40 00 80 06 58 18 C0 A8 0B 16 C0 A8
 0020 0B 76 30 C9 83 A4 00 00 00 00 59 FE 4B C0 50 14
 0030 00 00 97 F7 00 00

At first glance this may same a duplicate of Installing both SQL Server 2000 and SQL Server 2008 on the same machine, but it is not.

I have SQL Server 2000 and SQL Server 2008 R2 installed on the same machine and working fine.

My problem lies with connecting to the 2008 R2 server from a remote machine. My connectivity needs to be TCP. The legacy installation or SQL 2000 uses the default port of 1433. The named instance is by default configured to use 'Shared Memory' and is working fine. When I configured the 2008 R2 server to use 1433 (I did not think that thru) the service refused to start becasue 1433 was already in use by the legacy SQL 2000 default instance. Doh!

What I want to do is have both servers available simultaneously via TCP. both servers need not be on the same port, put if I cannot run them on the same port, then how do I configure the clients?

Is there not some kind of proxy available that can monitor the 1433 port and pass the request thru to the correct SQL instance by name? Is this capability built into SQL server already?

Thanks,

Jim

I cannot reach one of my vendors web sites. I can access the site from home, my boss can access from his home. But, from the office it does not work using the domain name. Using the IP address in place of the domain name does work. From these facts, it seems that I have a DNS problem at my work location. The DNS is obviously not completely dysfunctional as I am able to get to any other domain name that I have tried including some that could not possibly be locally cached. My environment is a windows network with a Server 2003 Standard server acting as the domain controller and hosting the DNS for my intranet. The problem has been going on for two days.

As a developer, I understand the basic concepts of DNS, but am not well versed in the specifics. Nor am I much of an administrator, but unfortunately, I am all we have.

Where do I start?

Jim

I have a Windows Server 2003 running IIS. I have created an application pool specifically for a web service application. The identity of that application pool is a domain account. The domain account is needed for SQL Server access via windows authentication.

When I run the application in the Default Application Pool with the NETWORK SERVICE account it work fine as long as I do not execute any function that accesses the SQL Server. SQL Server access fails as expected becasue the NETWORK SERVICE account does not have permissions on any of the SQL Server machines.

When change the application to use the application pool that is running under a domain account I get "Service Unavailable" when I attempt to run any web service. If I make that domain account a domain administrator the it does work. For obvious reasons, making the account an administrator is not a viable solution. Specifically, what permissions or local security policy settings are needed on a domain account to run a .NET application in IIS?

Thanks, Jim

I have an application that I am migrating from SQL 2000 to 2008. This has gone mostly smoothly. The local machines running Win XP and the VB6 application are working. One machine (only one I can get to directly) runs Win Server 2003 and it works OK. However, the workstations at the remote location are running the VB6 app on Windows 2000. Those do not work.

My question is: what might be missing or out-of-date on the Win 2000 machines, if anything, that would prevent them from working with SQL Server 2008.

Windows Server 2008 hangs up while booting after Windows update applied several updates. The server is a virtual instance on a Server 2008 Hyper-V host. Other virtual servers are fine, but have not been updated.

The normal boot shows the horizontal barber poll forever. When I do a safe boot it also hangs up. With a "Please Wait..." after loading many '.sys' files.

The last successfully loaded file listed is: '\Windows\system32\drivers\crcdisk.sys'

That is the extent of what I have been able to determine.

When I ran defrag on my development workstation today I discovered an enormous file that I was unaware of that cannot be defraged.

I want to get rid of it or at least shrink it and prevent it from growing so large. Unfortunately, my IT department is clueless.

Filename: c:\Documents and Settings\All Users\Application Data\Kaspersky Lab\AVP6\Report\eventlog.rpt

The file has 31,148 fragments and is 1.65 GB in size.

I am unable to delete the file and I do not have admin rights to stop the Kapersky process. Without these rights I doubt that I will be able to apply any suggestions you may have. But, I would gladly pass them on to my IT folks.

Jim

My problem is showing on a Hyper-V setup, but is not strictly a Hyper-V problem. Hyper0V is exposing the symptom.

I created a fixed size file on a drive in the host that almost fills the physical volume. This is causing "Low Disk Space" messages. Which, in turn, appears to be causing the guest VM to go to "Pause-Critical" status.

How can I make Server 2008 and/or Hyper-V stop doing this check? Or, will I have to reduce the size of my fixed size files(s)?

When I try to join my new server to my existing domain I get the following error:

"An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resove DNS names in the target domain."

I have tried all of the following already:

Successfully pinged the domain controller. Ping the new server from the domain controller by IP address and by DNS name. Ping the DC server from the new server by IP address and by DNS name. Changed the network to DHCP (it was originally static). No joy as static or DHCP. Turned off all firewall settings. Added the domain name to 'hosts' file. Added the server name of the primary domain controller to the 'hosts' file in the new server.

Any ideas? Thanks in advance for any help! Jim

Update: With help from J. Brian Kelly (Thanks) I have managed to narrow down the problem to a DNS issue. Specifically, UDP/53 packets are being sent (they are seen in Network Monitor), but are not getting to the DNS server. But, I do not yet know why.

Update: The quested output from IPCONFIG for the HyperV host and the virtual machine.

IPCONFIG from HyperV Server

 Windows IP Configuration
 Host Name . . . . . . . . . . . . : HYPER
 Primary Dns Suffix  . . . . . . . : sfi-wfc.com
 Node Type . . . . . . . . . . . . : Hybrid
 IP Routing Enabled. . . . . . . . : No
 WINS Proxy Enabled. . . . . . . . : No
 DNS Suffix Search List. . . . . . : sfi-wfc.com

 Ethernet adapter Local Area Connection 4:

 Connection-specific DNS Suffix  . :
 Description . . . . . . . . . . . : Primary Network
 Physical Address. . . . . . . . . : 00-30-48-CA-CC-7A
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes
 Link-local IPv6 Address . . . . . : fe80::cd16:3ac2:3d4f:e275%679(Preferred)
 IPv4 Address. . . . . . . . . . . : 192.168.100.1(Preferred)
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . : 192.168.100.10
 DHCPv6 IAID . . . . . . . . . . . : -1476382648
 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-10-20-E9-00-30-48-CA-CC-7A
 DNS Servers . . . . . . . . . . . : 192.168.100.5
 NetBIOS over Tcpip. . . . . . . . : Enabled

 Ethernet adapter Local Area Connection 3:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : sfi
 Description . . . . . . . . . . . : Intel(R) 82576 Gigabit Dual Port Network Connection #2
 Physical Address. . . . . . . . . : 00-30-48-CA-CC-7B
 DHCP Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes

IPCONFIG from Virtual Machine

 Windows IP Configuration
 Host Name . . . . . . . . . . . . : DB
 Primary Dns Suffix  . . . . . . . :
 Node Type . . . . . . . . . . . . : Hybrid
 IP Routing Enabled. . . . . . . . : No
 WINS Proxy Enabled. . . . . . . . : No
 DNS Suffix Search List. . . . . . : sfi

 Ethernet adapter Local Area Connection 2:

 Connection-specific DNS Suffix  . : sfi
 Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
 Physical Address. . . . . . . . . : 00-15-5D-66-03-02
 DHCP Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes
 IPv4 Address. . . . . . . . . . . : 192.168.100.128(Preferred)
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Lease Obtained. . . . . . . . . . : Saturday, August 29, 2009 10:44:45 AM
 Lease Expires . . . . . . . . . . : Tuesday, September 01, 2009 3:08:33 PM
 Default Gateway . . . . . . . . . : 192.168.100.10
 DHCP Server . . . . . . . . . . . : 192.168.100.5
 DNS Servers . . . . . . . . . . . : 192.168.102.5
 Primary WINS Server . . . . . . . : 192.168.100.5
 NetBIOS over Tcpip. . . . . . . . : Enabled

 Tunnel adapter Local Area Connection* 8:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : sfi
 Description . . . . . . . . . . . : isatap.sfi
 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes

 Tunnel adapter Local Area Connection* 9:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . :
 Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
 Physical Address. . . . . . . . . : 02-00-54-55-4E-01
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes