Connections hang after inactivity

Microsoft Windows server 2008 standard
January 7, 2010 at 12:39:12
Specs: Windows XP
I'm running a dual-DC 2008 AD domain, with a
third 2008 server as the main file/print server.
Connections to this server from workstations
seem to time out after fifteen minutes or so of
inactivity. Any new activity will initiate a
reconnection, but the shell freezes for 45-60
seconds while this happens.

net config server /autodisconnect:-1 did not
change anything.

Also, all the workstations are on a different
vlan/subnet than the server. Initially, I thought
this may be causing the problems, but the
problem persists when a machine is moved to
the server vlan.

Any help would be greatly appreciated.

Thanks.


See More: Connections hang after inactivity

Report •

#1
January 7, 2010 at 14:02:33
Workstations can't access any server that is in a different vlan or a different subnet if there is not a router between the two subnets.

As a rule it is best to check the nic cards power management settings. Make sure they are not set for the system to manage the power ie. put them to sleep.


Report •

#2
January 7, 2010 at 16:30:04
Well, not a full-on router, but a layer-3 switch (Cisco 3750)
configured for inter-vlan routing. And I've never seen an option in
XP power config to sleep a NIC. Where's that?

Report •

#3
January 8, 2010 at 12:55:11
It is in all nics.

Go to local area connection properties
next to the nic is a button Configure
go to the power management tab

Depending on model you can have
check box for "allow this computer to turn off this device to save power" *make sure unchecked
or
power savings - enable/disable *set to disabled.

How many hosts per vlan?


Report •

Related Solutions

#4
January 19, 2010 at 06:52:26
Wow... can't believe I've never seen that before. I've turned it off
on my machine... we'll see what happens.

If this fixes it, is that a scriptable setting? In the registry or
something?

As far as hosts per vlan, it varies. Each vlan has a class C
subnetted for it, and one or two are pretty full, but most are not,
and a few only have a handful of clients.


Report •

#5
January 19, 2010 at 08:22:12
Turning off power management on my NIC did not resolve the
problem.

Report •

#6
January 19, 2010 at 10:50:20
Did you set this on the server nics also? You should.

This is happening on all pcs regardless of vlan, correct?

Please post a ipconfig /all from a workstation and a DC.


Report •

#7
January 20, 2010 at 06:14:09
From my workstation:
C:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : IS-FRUCHEY-01
        Primary Dns Suffix  . . . . . . . : lsd.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : lsd.local
                                            lsd.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : lsd.local
        Description . . . . . . . . . . . : Broadcom NetXtreme 57xx 
Gigabit Cont
roller
        Physical Address. . . . . . . . . : 00-1E-C9-35-22-27
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.1.38.57
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.1.38.1
        DHCP Server . . . . . . . . . . . : 10.1.1.10
        DNS Servers . . . . . . . . . . . : 10.1.1.10
                                            10.1.1.22
        Lease Obtained. . . . . . . . . . : Monday, January 18, 
2010 3:21:49 AM
        Lease Expires . . . . . . . . . . : Tuesday, January 26, 
2010 3:21:49 AM


Report •

#8
January 20, 2010 at 06:17:14
From the domain controller:
C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LSDDC01
   Primary Dns Suffix  . . . . . . . : lsd.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lsd.local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit 
Ethernet #2
   Physical Address. . . . . . . . . : 00-1E-4F-2D-11-27
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 90.1.1.22(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.0.0.0
   Default Gateway . . . . . . . . . : 90.0.0.1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit 
Ethernet
   Physical Address. . . . . . . . . : 00-1E-4F-2D-11-26
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.1.1.10(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.1.1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{03F8D5F8-2905-428F-
B4C9-818E95072
AE3}
   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 . . . . . . . . . . . : isatap.{62256781-D6AC-4808-
A94B-C345DE4D6
67B}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : 6TO4 Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 
2002:5a01:116::5a01:116(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled


And from the file server in question:

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LSDFS02
   Primary Dns Suffix  . . . . . . . : lsd.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lsd.local

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit 
Ethernet #2
   Physical Address. . . . . . . . . : 00-1E-4F-2D-43-3A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit 
Ethernet
   Physical Address. . . . . . . . . : 00-1E-4F-2D-43-39
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.1.1.15(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.1.1
   DNS Servers . . . . . . . . . . . : 10.1.1.10
                                       10.1.1.22
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet 
Adapter for VMnet
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : 
fe80::f19b:f60f:af1e:940c%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.220.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 4:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet 
Adapter for VMnet
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : 
fe80::d883:f95d:6101:ef5%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.106.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{CB48C993-7EC6-4305-
BD5D-CC4E8E314
2BF}
   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 . . . . . . . . . . . : isatap.{310AE227-B573-495D-
BC7A-91288935A
3B9}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{D18860E9-D5F0-418F-
A894-F7C096B96
C6F}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{3C35EB01-8FD6-48A2-
BC5A-1FC8181CF
892}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


Report •

#9
January 20, 2010 at 10:19:14
kind of a mess.

Microsoft dns servers should point to their ips not the loopback.

LSDDC01 is multihomed [its unclear why with the completely foreign subnet 90.1.1.22

Mixture of ipv4 and ipv6. I would recommend just do ipv4 across the board for internal lan. Otherwise you get into binding priorites which can get confusing as to which is primary.

You can see this on the vmware server with ipv6 ip and dns but ipv4 for ip and subnet mask with no gateway or dns.

I suspect the connection lags are due to workstations not getting a response from the dns servers and defaulting to broadcasts to get name resolution information.

Why all the different subnets?
Why server multihomed?
How many pcs/devices in the network?


Report •

#10
January 20, 2010 at 10:59:42
I suppose I should mention that I inherited all this from the
previous guy. The major change I made was to get rid of
Novell and move all the files to the Win2008 server.

As for the bizarre 90.x network, that's been in place for over
12 years, and no one knows who started it. Over last
Christmas break, we finally moved to 10.x, but none of us
knew enough about Novell admin to mess with those servers.
So the 90.1.1.22 is the secondary DNS for the Novell servers.
(We're still using Groupwise for mail)

The previous guy set up all the VLANs because apparently
there was a lot of broadcast traffic causing a lot of congestion.

We have roughly 300 PCs on the network and 30 network
printers.

As for the loopback DNS... I never noticed that. Strange
indeed.


Report •

#11
January 20, 2010 at 11:04:02
Also, I've noticed that the same problem exists when accessing
a share on an XP workstation. So it's not a server thing after all.

Report •

#12
January 20, 2010 at 12:00:42
It would appear to be a dns thing.

how are the workstaitons getting to the groupwise subnet?
there does not appear to be a path.

from a workstation do a tracert to the groupwise server and post the results please.

Cisco vlan/routing training, in my opinion, promotes this vlan/subnet confusion. They train you on a super large network but don't explain that you can do vlans and don't have to do subnetting.

Ideally the entire network would have been you could have supernetted two class c's for 510 hosts
192.168.0.0 subnet mask 255.255.254.0 would have given you 192.168.0.0 - 192.168.1.255

Or a class b subnet. For example
172.16.0.1 subnet mask 255.255.0.0 would have provided a ip range of 172.16.0.1 - 172.16.255.254 [65534 hosts]

You would do no vlan routing. Server nics would be in all vlans whereas pcs would be divided up to smaller broadcast vlan domains. Everything would have been in a common subnet.

This way the servers are seen by all vlans but the pc vlans themselves don't talk ot each other.

The immediate solution to the issue is the correct DNS configuration. Servers should have host and ptr records as well as the workstations also. I would also suggest in Active Directory your present subnets should be listed under Sites and Services so AD knows about them.


Report •

#13
January 20, 2010 at 12:04:40
Before I read anything that you replied with... I did some more
testing, and the problem does not appear to occur with a file
server that is not joined to the domain.

Report •

#14
January 20, 2010 at 13:22:55
Ok... the correct DNS config... which would be? Pointing the
servers' DNS to themselves (instead of loopback)? If so, Done.

Also, when I did that, Windows warned me that I had gateways
pointing to different networks, so I removed the gateway from the
90.x address. I guess we'll see if that does anything.


Report •

#15
January 20, 2010 at 14:04:45
Did you check the host and ptr records for all servers/workstation? do they exist?

After posting the tracert also post a nslookup from a workstation to each server.


Report •

#16
January 21, 2010 at 06:21:27
Not sure that this is really helpful...
C:\>tracert lsddc01

Tracing route to LSDDC01.lsd.local [10.1.1.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.38.1
  2    <1 ms    <1 ms    <1 ms  lsddc01.lsd.local [10.1.1.10]

Trace complete.

C:\>nslookup lsddc01
Server:  lsddc01.lsd.local
Address:  10.1.1.10

Name:    lsddc01.lsd.local
Addresses:  10.1.1.10, 90.1.1.22


C:\>tracert lsdfs02

Tracing route to lsdfs02.lsd.local [10.1.1.15]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.38.1
  2    <1 ms    <1 ms    <1 ms  lsdfs02.lsd.local [10.1.1.15]

Trace complete.

C:\>nslookup lsdfs02
Server:  lsddc01.lsd.local
Address:  10.1.1.10

Name:    lsdfs02.lsd.local
Address:  10.1.1.15

Now... as for host and ptr records, DNS is really not my
strong suit.

On lsddc01, there is NO host record for lsddc02. Should I
create one? These should be created automatically, right?
And I don't see any PTR records, but I may not be looking in
the right place.


Report •

#17
January 21, 2010 at 15:06:41
Results look good.

Every server should be listed in dns with a host and ptr record. You manually have to add them after the first server. It is not automatic. It is automatic if using dhcp and enabled to auto update dns. Servers should never be dhcp clients.

Ptr records are under Reverse lookup zones and then under the subnet they belong to.

I am not clear on why you have lsddc01 with ip 90.1.1.22
You don't use groupwise at the server do you? Even if you did your router should have a route to the netware network and not need the nic or the dns entry.

Is netware also acting as a dns server?

I am beginning to think this aspect of your config is causing a network loop. After all you have a direct connect from the server as well as a route thru the network. It could very well be that MS DNS is responding but sending out the wrong interface.

It should do no harm to disable the 90.x.x.x. nic then see what happens. If you startup mmc and load the dns module you will see the dns event viewer. Review the errors here and report back.

Thanks


Report •

Ask Question