keep getting kicked out

Hi,
We have a Microsoft Server 2003 with 3 computers (XP Pro) connecting via a
LAN to synchronise files in the shared folders. There is also a Draytek
Vigor 2800 router for internet access with a static IP and DHCP disabled.
The server is giving out the IP's for the client computers but about twice a
day the clients are going 'Off Line', they loose their IP address (it
reverts to 169.xxx....) and are unable to access the server or get onto the
internet or print (The printer is set up through the server). I have tried
giving the clients static IP's but the same thing happens anyway. I have
also tried disabling and enabling the LAN connection on the clients. I can
log on to the router from outside the LAN which has it's own static WAN and
LAN IP but the server is not pingable (timed out). I reboot the server and
the clients are then given an IP and we are back up and running. I have
checked the Event Viewer but there doesn't seem to be anything relevant and
there certainly isn't anything that relates to the times the connection is
lost. 2 of the clients that are always on loose the connection about 5
minutes apart. One computer will say it is off line and 5 minutes later the
other one will loose it too.

First, I would like any advice about what might cause this on the server
because I am sure rebooting it twice a day isn't normal. Also, could I take
DHCP away from the server and give it to the Router instead? Why do they
loose connection even when they have a static IP? Because of this I don't
think getting the IP from the Router will make any difference. When the
server decides it wants to close it's connection it will.

Any advice greatly appreciated.
Cheers
Lenny

Lanwench
Tue Aug 12 17:04:32 PDT 2008

lenny <lenny@thetakeout.com> wrote:
> Hi,
> We have a Microsoft Server 2003 with 3 computers (XP Pro) connecting
> via a LAN to synchronise files in the shared folders.

Are you using AD or are you in a workgroup config?

>? There is also a
> Draytek Vigor 2800 router for internet access with a static IP and
> DHCP disabled. The server is giving out the IP's for the client
> computers but about twice a day the clients are going 'Off Line',
> they loose their IP address (it reverts to 169.xxx....) and are
> unable to access the server or get onto the internet or print (The
> printer is set up through the server).

Does the server lose connectivity to the clients/internet at the same time?
What do you see in the workstation event logs?


> I have tried giving the
> clients static IP's but the same thing happens anyway. I have also
> tried disabling and enabling the LAN connection on the clients.

What about repairing it?

> I can
> log on to the router from outside the LAN which has it's own static
> WAN and LAN IP but the server is not pingable (timed out).

Well, you probably don't want to allow inbound ICMP anyway, but that's
another story. At the time can the server ping *out* ?

> I reboot
> the server and the clients are then given an IP and we are back up
> and running. I have checked the Event Viewer but there doesn't seem
> to be anything relevant and there certainly isn't anything that
> relates to the times the connection is lost. 2 of the clients that
> are always on loose the connection about 5 minutes apart. One
> computer will say it is off line and 5 minutes later the other one
> will loose it too.

Are the clients all up to date with patches?
What about the server?
What kind of NICs - and have you updated the drivers from the mfr?
Do you use a switch or a hub - and have you tried replacing it/cables/to
rule out the physical?
>
> First, I would like any advice about what might cause this on the
> server because I am sure rebooting it twice a day isn't normal.

Definitely not.

> Also,
> could I take DHCP away from the server and give it to the Router
> instead?

Don't do that, esp if you run AD & DNS. Your dynamic DNS updates will work
better if you use your W2003 server for DHCP services. Anyway, from what
you've written it wouldn't make any difference.

> Why do they loose connection even when they have a static
> IP? Because of this I don't think getting the IP from the Router will
> make any difference.

Exactly.

> When the server decides it wants to close it's
> connection it will.

You haven't demonstrated it's the server kicking them out, though.
>
> Any advice greatly appreciated.
> Cheers
> Lenny

Also try posting an unedited ipconfig /all from the server & one of the
clients.

lenny
Wed Aug 13 14:06:40 PDT 2008


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>
> Are you using AD or are you in a workgroup config?

AD
>
> Does the server lose connectivity to the clients/internet at the same
> time?
> What do you see in the workstation event logs?

No it seems to be between 20 and thirty minutes difference. Sometimes twice
a day and other times only every 2 or 3 days

> What about repairing it?

I have tried this but with no difference. It repairs OK.
>
> Well, you probably don't want to allow inbound ICMP anyway, but that's
> another story. At the time can the server ping *out* ?

I haven't been in the office when this occures so I am not sure but I
certainly can't ping the server. (I have logged in to the network via a Dial
in User setting on the Router.)
>

> Are the clients all up to date with patches?

Yes
> What about the server?

Yes
> What kind of NICs - and have you updated the drivers from the mfr?

No
> Do you use a switch or a hub - and have you tried replacing it/cables/to
It is only a small network so I am using an 8 port hub. Many of the cables
are new and the server to hub cable is relativally new. I have checked them
with a cable tester and they are all A1
> rule out the physical?
>
>
>
> You haven't demonstrated it's the server kicking them out, though.

This is true but both the server and the clients don't show anything in the
event logs for these times. What makes me think it is the server kicking
them out is that when they are kicked out I am unable to access the server
from anywhere on the network or outside the network. Also if I reboot the
server the clients are then given a fresh IP address and all is well.
>
> Also try posting an unedited ipconfig /all from the server & one of the
> clients.

Here are the IP Configs when all is well.

CLIENT
C:\Documents and Settings\adminR>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WORK-Office-2
Primary Dns Suffix . . . . . . . : Ourcompany.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Ourcompany.local
Ourcompany.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Ourcompany.local
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 192.168.1.5
Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

C:\Documents and Settings\adminR>


SERVER

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
#2
Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.5

Lanwench
Thu Aug 14 07:01:45 PDT 2008

lenny <lenny@thetakeout.com> wrote:
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>
>> Are you using AD or are you in a workgroup config?
>
> AD
>>
>> Does the server lose connectivity to the clients/internet at the same
>> time?
>> What do you see in the workstation event logs?
>
> No it seems to be between 20 and thirty minutes difference. Sometimes
> twice a day and other times only every 2 or 3 days
>
>> What about repairing it?
>
> I have tried this but with no difference. It repairs OK.
>>
>> Well, you probably don't want to allow inbound ICMP anyway, but
>> that's another story. At the time can the server ping *out* ?
>
> I haven't been in the office when this occures so I am not sure but I
> certainly can't ping the server. (I have logged in to the network via
> a Dial in User setting on the Router.)
>>
>
>> Are the clients all up to date with patches?
>
> Yes
>> What about the server?
>
> Yes
>> What kind of NICs - and have you updated the drivers from the mfr?
>
> No
>> Do you use a switch or a hub - and have you tried replacing
>> it/cables/to
> It is only a small network so I am using an 8 port hub. Many of the
> cables are new and the server to hub cable is relativally new. I have
> checked them with a cable tester and they are all A1
>> rule out the physical?
>>
>>
>>
>> You haven't demonstrated it's the server kicking them out, though.
>
> This is true but both the server and the clients don't show anything
> in the event logs for these times. What makes me think it is the
> server kicking them out is that when they are kicked out I am unable
> to access the server from anywhere on the network or outside the
> network.

OK, that's a good call, then.

> Also if I reboot the server the clients are then given a
> fresh IP address and all is well.

I would update the NIC driver on the server or replace the NIC as a test.
>>
>> Also try posting an unedited ipconfig /all from the server & one of
>> the clients.
>
> Here are the IP Configs when all is well.
>
> CLIENT
> C:\Documents and Settings\adminR>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : WORK-Office-2
> Primary Dns Suffix . . . . . . . : Ourcompany.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Ourcompany.local
> Ourcompany.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : Ourcompany.local
> Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
> Connecti
> on
> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.12
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.5
> DNS Servers . . . . . . . . . . . : 192.168.1.5
> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
> Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07
>
> C:\Documents and Settings\adminR>
>
>
> SERVER
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : server
> Primary Dns Suffix . . . . . . . : Ourcompany.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Ourcompany.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet #2
> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.5
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.5

That all looks good.

lenny
Fri Aug 15 04:42:40 PDT 2008

I have changed the DHCP to unlimited time now so will see what happens. If
it happens again shortly I will update the LAN Card driver. If it still
carries on I will replace the card.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:%23NTlDfh$IHA.4780@TK2MSFTNGP05.phx.gbl...
> lenny <lenny@thetakeout.com> wrote:
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>> message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>>
>>> Are you using AD or are you in a workgroup config?
>>
>> AD
>>>
>>> Does the server lose connectivity to the clients/internet at the same
>>> time?
>>> What do you see in the workstation event logs?
>>
>> No it seems to be between 20 and thirty minutes difference. Sometimes
>> twice a day and other times only every 2 or 3 days
>>
>>> What about repairing it?
>>
>> I have tried this but with no difference. It repairs OK.
>>>
>>> Well, you probably don't want to allow inbound ICMP anyway, but
>>> that's another story. At the time can the server ping *out* ?
>>
>> I haven't been in the office when this occures so I am not sure but I
>> certainly can't ping the server. (I have logged in to the network via
>> a Dial in User setting on the Router.)
>>>
>>
>>> Are the clients all up to date with patches?
>>
>> Yes
>>> What about the server?
>>
>> Yes
>>> What kind of NICs - and have you updated the drivers from the mfr?
>>
>> No
>>> Do you use a switch or a hub - and have you tried replacing
>>> it/cables/to
>> It is only a small network so I am using an 8 port hub. Many of the
>> cables are new and the server to hub cable is relativally new. I have
>> checked them with a cable tester and they are all A1
>>> rule out the physical?
>>>
>>>
>>>
>>> You haven't demonstrated it's the server kicking them out, though.
>>
>> This is true but both the server and the clients don't show anything
>> in the event logs for these times. What makes me think it is the
>> server kicking them out is that when they are kicked out I am unable
>> to access the server from anywhere on the network or outside the
>> network.
>
> OK, that's a good call, then.
>
>> Also if I reboot the server the clients are then given a
>> fresh IP address and all is well.
>
> I would update the NIC driver on the server or replace the NIC as a test.
>>>
>>> Also try posting an unedited ipconfig /all from the server & one of
>>> the clients.
>>
>> Here are the IP Configs when all is well.
>>
>> CLIENT
>> C:\Documents and Settings\adminR>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : WORK-Office-2
>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : Ourcompany.local
>> Ourcompany.local
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . : Ourcompany.local
>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
>> Connecti
>> on
>> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
>> Dhcp Enabled. . . . . . . . . . . : Yes
>> Autoconfiguration Enabled . . . . : Yes
>> IP Address. . . . . . . . . . . . : 192.168.1.12
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DHCP Server . . . . . . . . . . . : 192.168.1.5
>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
>> Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07
>>
>> C:\Documents and Settings\adminR>
>>
>>
>> SERVER
>>
>> Microsoft Windows [Version 5.2.3790]
>> (C) Copyright 1985-2003 Microsoft Corp.
>>
>> C:\Documents and Settings\Administrator>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : server
>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>> Ethernet #2
>> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.5
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>
> That all looks good.
>
>

Lanwench
Fri Aug 15 08:49:02 PDT 2008

lenny <lenny@thetakeout.com> wrote:
> I have changed the DHCP to unlimited time now so will see what
> happens. If it happens again shortly I will update the LAN Card
> driver. If it still carries on I will replace the card.

Change the driver first (e.g., now). I wouldn't leave it with an unlimited
lease - it will make it impossible to manage these workstations if you need
to change anything.
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:%23NTlDfh$IHA.4780@TK2MSFTNGP05.phx.gbl...
>> lenny <lenny@thetakeout.com> wrote:
>>> "Lanwench [MVP - Exchange]"
>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>>> message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>>>
>>>> Are you using AD or are you in a workgroup config?
>>>
>>> AD
>>>>
>>>> Does the server lose connectivity to the clients/internet at the
>>>> same time?
>>>> What do you see in the workstation event logs?
>>>
>>> No it seems to be between 20 and thirty minutes difference.
>>> Sometimes twice a day and other times only every 2 or 3 days
>>>
>>>> What about repairing it?
>>>
>>> I have tried this but with no difference. It repairs OK.
>>>>
>>>> Well, you probably don't want to allow inbound ICMP anyway, but
>>>> that's another story. At the time can the server ping *out* ?
>>>
>>> I haven't been in the office when this occures so I am not sure but
>>> I certainly can't ping the server. (I have logged in to the network
>>> via a Dial in User setting on the Router.)
>>>>
>>>
>>>> Are the clients all up to date with patches?
>>>
>>> Yes
>>>> What about the server?
>>>
>>> Yes
>>>> What kind of NICs - and have you updated the drivers from the mfr?
>>>
>>> No
>>>> Do you use a switch or a hub - and have you tried replacing
>>>> it/cables/to
>>> It is only a small network so I am using an 8 port hub. Many of the
>>> cables are new and the server to hub cable is relativally new. I
>>> have checked them with a cable tester and they are all A1
>>>> rule out the physical?
>>>>
>>>>
>>>>
>>>> You haven't demonstrated it's the server kicking them out, though.
>>>
>>> This is true but both the server and the clients don't show anything
>>> in the event logs for these times. What makes me think it is the
>>> server kicking them out is that when they are kicked out I am unable
>>> to access the server from anywhere on the network or outside the
>>> network.
>>
>> OK, that's a good call, then.
>>
>>> Also if I reboot the server the clients are then given a
>>> fresh IP address and all is well.
>>
>> I would update the NIC driver on the server or replace the NIC as a
>> test.
>>>>
>>>> Also try posting an unedited ipconfig /all from the server & one of
>>>> the clients.
>>>
>>> Here are the IP Configs when all is well.
>>>
>>> CLIENT
>>> C:\Documents and Settings\adminR>ipconfig /all
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : WORK-Office-2
>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>> Ourcompany.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . : Ourcompany.local
>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>>> Network Connecti
>>> on
>>> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>> Autoconfiguration Enabled . . . . : Yes
>>> IP Address. . . . . . . . . . . . : 192.168.1.12
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DHCP Server . . . . . . . . . . . : 192.168.1.5
>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
>>> Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07
>>>
>>> C:\Documents and Settings\adminR>
>>>
>>>
>>> SERVER
>>>
>>> Microsoft Windows [Version 5.2.3790]
>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>
>>> C:\Documents and Settings\Administrator>ipconfig /all
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : server
>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>> Ethernet #2
>>> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.5
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>
>> That all looks good.

lenny
Thu Aug 21 01:42:14 PDT 2008

What about giving the workstations their own IP address and leaving the
server on unlimited lease?

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:eHMtv1v$IHA.4148@TK2MSFTNGP05.phx.gbl...
> lenny <lenny@thetakeout.com> wrote:
>> I have changed the DHCP to unlimited time now so will see what
>> happens. If it happens again shortly I will update the LAN Card
>> driver. If it still carries on I will replace the card.
>
> Change the driver first (e.g., now). I wouldn't leave it with an unlimited
> lease - it will make it impossible to manage these workstations if you
> need to change anything.
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>> message news:%23NTlDfh$IHA.4780@TK2MSFTNGP05.phx.gbl...
>>> lenny <lenny@thetakeout.com> wrote:
>>>> "Lanwench [MVP - Exchange]"
>>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>>>> message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>>>>
>>>>> Are you using AD or are you in a workgroup config?
>>>>
>>>> AD
>>>>>
>>>>> Does the server lose connectivity to the clients/internet at the
>>>>> same time?
>>>>> What do you see in the workstation event logs?
>>>>
>>>> No it seems to be between 20 and thirty minutes difference.
>>>> Sometimes twice a day and other times only every 2 or 3 days
>>>>
>>>>> What about repairing it?
>>>>
>>>> I have tried this but with no difference. It repairs OK.
>>>>>
>>>>> Well, you probably don't want to allow inbound ICMP anyway, but
>>>>> that's another story. At the time can the server ping *out* ?
>>>>
>>>> I haven't been in the office when this occures so I am not sure but
>>>> I certainly can't ping the server. (I have logged in to the network
>>>> via a Dial in User setting on the Router.)
>>>>>
>>>>
>>>>> Are the clients all up to date with patches?
>>>>
>>>> Yes
>>>>> What about the server?
>>>>
>>>> Yes
>>>>> What kind of NICs - and have you updated the drivers from the mfr?
>>>>
>>>> No
>>>>> Do you use a switch or a hub - and have you tried replacing
>>>>> it/cables/to
>>>> It is only a small network so I am using an 8 port hub. Many of the
>>>> cables are new and the server to hub cable is relativally new. I
>>>> have checked them with a cable tester and they are all A1
>>>>> rule out the physical?
>>>>>
>>>>>
>>>>>
>>>>> You haven't demonstrated it's the server kicking them out, though.
>>>>
>>>> This is true but both the server and the clients don't show anything
>>>> in the event logs for these times. What makes me think it is the
>>>> server kicking them out is that when they are kicked out I am unable
>>>> to access the server from anywhere on the network or outside the
>>>> network.
>>>
>>> OK, that's a good call, then.
>>>
>>>> Also if I reboot the server the clients are then given a
>>>> fresh IP address and all is well.
>>>
>>> I would update the NIC driver on the server or replace the NIC as a
>>> test.
>>>>>
>>>>> Also try posting an unedited ipconfig /all from the server & one of
>>>>> the clients.
>>>>
>>>> Here are the IP Configs when all is well.
>>>>
>>>> CLIENT
>>>> C:\Documents and Settings\adminR>ipconfig /all
>>>>
>>>> Windows IP Configuration
>>>>
>>>> Host Name . . . . . . . . . . . . : WORK-Office-2
>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>> Ourcompany.local
>>>>
>>>> Ethernet adapter Local Area Connection:
>>>>
>>>> Connection-specific DNS Suffix . : Ourcompany.local
>>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>>>> Network Connecti
>>>> on
>>>> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> IP Address. . . . . . . . . . . . : 192.168.1.12
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DHCP Server . . . . . . . . . . . : 192.168.1.5
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
>>>> Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07
>>>>
>>>> C:\Documents and Settings\adminR>
>>>>
>>>>
>>>> SERVER
>>>>
>>>> Microsoft Windows [Version 5.2.3790]
>>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>>
>>>> C:\Documents and Settings\Administrator>ipconfig /all
>>>>
>>>> Windows IP Configuration
>>>>
>>>> Host Name . . . . . . . . . . . . : server
>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>>
>>>> Ethernet adapter Local Area Connection:
>>>>
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>>> Ethernet #2
>>>> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> IP Address. . . . . . . . . . . . : 192.168.1.5
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>
>>> That all looks good.
>
>
>

Lanwench
Thu Aug 21 06:27:28 PDT 2008

lenny <lenny@thetakeout.com> wrote:
> What about giving the workstations their own IP address

You mean statics? I wouldn't recommend that. Too much management overhead.
DHCP is the way to go.

> and leaving
> the server on unlimited lease?

Servers should not be using DHCP anyway. Servers and network devices should
have statics - printers should have DHCP reservations or statics - and
workstations should be using DHCP.

You can't set up a DHCP server to have a DHCP-assigned IP address, either,
note.


>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:eHMtv1v$IHA.4148@TK2MSFTNGP05.phx.gbl...
>> lenny <lenny@thetakeout.com> wrote:
>>> I have changed the DHCP to unlimited time now so will see what
>>> happens. If it happens again shortly I will update the LAN Card
>>> driver. If it still carries on I will replace the card.
>>
>> Change the driver first (e.g., now). I wouldn't leave it with an
>> unlimited lease - it will make it impossible to manage these
>> workstations if you need to change anything.
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>>> message news:%23NTlDfh$IHA.4780@TK2MSFTNGP05.phx.gbl...
>>>> lenny <lenny@thetakeout.com> wrote:
>>>>> "Lanwench [MVP - Exchange]"
>>>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote
>>>>> in message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>>>>>
>>>>>> Are you using AD or are you in a workgroup config?
>>>>>
>>>>> AD
>>>>>>
>>>>>> Does the server lose connectivity to the clients/internet at the
>>>>>> same time?
>>>>>> What do you see in the workstation event logs?
>>>>>
>>>>> No it seems to be between 20 and thirty minutes difference.
>>>>> Sometimes twice a day and other times only every 2 or 3 days
>>>>>
>>>>>> What about repairing it?
>>>>>
>>>>> I have tried this but with no difference. It repairs OK.
>>>>>>
>>>>>> Well, you probably don't want to allow inbound ICMP anyway, but
>>>>>> that's another story. At the time can the server ping *out* ?
>>>>>
>>>>> I haven't been in the office when this occures so I am not sure
>>>>> but I certainly can't ping the server. (I have logged in to the
>>>>> network via a Dial in User setting on the Router.)
>>>>>>
>>>>>
>>>>>> Are the clients all up to date with patches?
>>>>>
>>>>> Yes
>>>>>> What about the server?
>>>>>
>>>>> Yes
>>>>>> What kind of NICs - and have you updated the drivers from the
>>>>>> mfr?
>>>>>
>>>>> No
>>>>>> Do you use a switch or a hub - and have you tried replacing
>>>>>> it/cables/to
>>>>> It is only a small network so I am using an 8 port hub. Many of
>>>>> the cables are new and the server to hub cable is relativally
>>>>> new. I have checked them with a cable tester and they are all A1
>>>>>> rule out the physical?
>>>>>>
>>>>>>
>>>>>>
>>>>>> You haven't demonstrated it's the server kicking them out,
>>>>>> though.
>>>>>
>>>>> This is true but both the server and the clients don't show
>>>>> anything in the event logs for these times. What makes me think
>>>>> it is the server kicking them out is that when they are kicked
>>>>> out I am unable to access the server from anywhere on the network
>>>>> or outside the network.
>>>>
>>>> OK, that's a good call, then.
>>>>
>>>>> Also if I reboot the server the clients are then given a
>>>>> fresh IP address and all is well.
>>>>
>>>> I would update the NIC driver on the server or replace the NIC as a
>>>> test.
>>>>>>
>>>>>> Also try posting an unedited ipconfig /all from the server & one
>>>>>> of the clients.
>>>>>
>>>>> Here are the IP Configs when all is well.
>>>>>
>>>>> CLIENT
>>>>> C:\Documents and Settings\adminR>ipconfig /all
>>>>>
>>>>> Windows IP Configuration
>>>>>
>>>>> Host Name . . . . . . . . . . . . : WORK-Office-2
>>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>> IP Routing Enabled. . . . . . . . : No
>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>>> Ourcompany.local
>>>>>
>>>>> Ethernet adapter Local Area Connection:
>>>>>
>>>>> Connection-specific DNS Suffix . : Ourcompany.local
>>>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>>>>> Network Connecti
>>>>> on
>>>>> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
>>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>> IP Address. . . . . . . . . . . . : 192.168.1.12
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>> DHCP Server . . . . . . . . . . . : 192.168.1.5
>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>>> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
>>>>> Lease Expires . . . . . . . . . . : 19 January 2038
>>>>> 04:14:07 C:\Documents and Settings\adminR>
>>>>>
>>>>>
>>>>> SERVER
>>>>>
>>>>> Microsoft Windows [Version 5.2.3790]
>>>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>>>
>>>>> C:\Documents and Settings\Administrator>ipconfig /all
>>>>>
>>>>> Windows IP Configuration
>>>>>
>>>>> Host Name . . . . . . . . . . . . : server
>>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>> IP Routing Enabled. . . . . . . . : No
>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>>>
>>>>> Ethernet adapter Local Area Connection:
>>>>>
>>>>> Connection-specific DNS Suffix . :
>>>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>>>> Ethernet #2
>>>>> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>> IP Address. . . . . . . . . . . . : 192.168.1.5
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>>
>>>> That all looks good.

lenny
Thu Aug 21 13:29:03 PDT 2008

Off course. The server has a static IP (192.168.1.5), there are only 2 PC's
and 2 Laptops on the network plus a couple of printers and a router. The
router already has a static as do the printers. Since setting the PC's to
static IP's there hasn't been a problem, but it might just be a coincidence.
I will be updating the drivers as recommended at the earliest opportunity.
Cheers

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:%23WIwzV5AJHA.3348@TK2MSFTNGP04.phx.gbl...
> lenny <lenny@thetakeout.com> wrote:
>> What about giving the workstations their own IP address
>
> You mean statics? I wouldn't recommend that. Too much management overhead.
> DHCP is the way to go.
>
>> and leaving
>> the server on unlimited lease?
>
> Servers should not be using DHCP anyway. Servers and network devices
> should have statics - printers should have DHCP reservations or statics -
> and workstations should be using DHCP.
>
> You can't set up a DHCP server to have a DHCP-assigned IP address, either,
> note.
>
>
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>> message news:eHMtv1v$IHA.4148@TK2MSFTNGP05.phx.gbl...
>>> lenny <lenny@thetakeout.com> wrote:
>>>> I have changed the DHCP to unlimited time now so will see what
>>>> happens. If it happens again shortly I will update the LAN Card
>>>> driver. If it still carries on I will replace the card.
>>>
>>> Change the driver first (e.g., now). I wouldn't leave it with an
>>> unlimited lease - it will make it impossible to manage these
>>> workstations if you need to change anything.
>>>>
>>>> "Lanwench [MVP - Exchange]"
>>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>>>> message news:%23NTlDfh$IHA.4780@TK2MSFTNGP05.phx.gbl...
>>>>> lenny <lenny@thetakeout.com> wrote:
>>>>>> "Lanwench [MVP - Exchange]"
>>>>>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote
>>>>>> in message news:e5hythN$IHA.3696@TK2MSFTNGP06.phx.gbl...
>>>>>>>
>>>>>>> Are you using AD or are you in a workgroup config?
>>>>>>
>>>>>> AD
>>>>>>>
>>>>>>> Does the server lose connectivity to the clients/internet at the
>>>>>>> same time?
>>>>>>> What do you see in the workstation event logs?
>>>>>>
>>>>>> No it seems to be between 20 and thirty minutes difference.
>>>>>> Sometimes twice a day and other times only every 2 or 3 days
>>>>>>
>>>>>>> What about repairing it?
>>>>>>
>>>>>> I have tried this but with no difference. It repairs OK.
>>>>>>>
>>>>>>> Well, you probably don't want to allow inbound ICMP anyway, but
>>>>>>> that's another story. At the time can the server ping *out* ?
>>>>>>
>>>>>> I haven't been in the office when this occures so I am not sure
>>>>>> but I certainly can't ping the server. (I have logged in to the
>>>>>> network via a Dial in User setting on the Router.)
>>>>>>>
>>>>>>
>>>>>>> Are the clients all up to date with patches?
>>>>>>
>>>>>> Yes
>>>>>>> What about the server?
>>>>>>
>>>>>> Yes
>>>>>>> What kind of NICs - and have you updated the drivers from the
>>>>>>> mfr?
>>>>>>
>>>>>> No
>>>>>>> Do you use a switch or a hub - and have you tried replacing
>>>>>>> it/cables/to
>>>>>> It is only a small network so I am using an 8 port hub. Many of
>>>>>> the cables are new and the server to hub cable is relativally
>>>>>> new. I have checked them with a cable tester and they are all A1
>>>>>>> rule out the physical?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> You haven't demonstrated it's the server kicking them out,
>>>>>>> though.
>>>>>>
>>>>>> This is true but both the server and the clients don't show
>>>>>> anything in the event logs for these times. What makes me think
>>>>>> it is the server kicking them out is that when they are kicked
>>>>>> out I am unable to access the server from anywhere on the network
>>>>>> or outside the network.
>>>>>
>>>>> OK, that's a good call, then.
>>>>>
>>>>>> Also if I reboot the server the clients are then given a
>>>>>> fresh IP address and all is well.
>>>>>
>>>>> I would update the NIC driver on the server or replace the NIC as a
>>>>> test.
>>>>>>>
>>>>>>> Also try posting an unedited ipconfig /all from the server & one
>>>>>>> of the clients.
>>>>>>
>>>>>> Here are the IP Configs when all is well.
>>>>>>
>>>>>> CLIENT
>>>>>> C:\Documents and Settings\adminR>ipconfig /all
>>>>>>
>>>>>> Windows IP Configuration
>>>>>>
>>>>>> Host Name . . . . . . . . . . . . : WORK-Office-2
>>>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>>>> Ourcompany.local
>>>>>>
>>>>>> Ethernet adapter Local Area Connection:
>>>>>>
>>>>>> Connection-specific DNS Suffix . : Ourcompany.local
>>>>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE
>>>>>> Network Connecti
>>>>>> on
>>>>>> Physical Address. . . . . . . . . : 00-11-11-D2-2A-7D
>>>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.12
>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>> DHCP Server . . . . . . . . . . . : 192.168.1.5
>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>>>> Lease Obtained. . . . . . . . . . : 13 August 2008 10:32:52
>>>>>> Lease Expires . . . . . . . . . . : 19 January 2038
>>>>>> 04:14:07 C:\Documents and Settings\adminR>
>>>>>>
>>>>>>
>>>>>> SERVER
>>>>>>
>>>>>> Microsoft Windows [Version 5.2.3790]
>>>>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>>>>
>>>>>> C:\Documents and Settings\Administrator>ipconfig /all
>>>>>>
>>>>>> Windows IP Configuration
>>>>>>
>>>>>> Host Name . . . . . . . . . . . . : server
>>>>>> Primary Dns Suffix . . . . . . . : Ourcompany.local
>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>> DNS Suffix Search List. . . . . . : Ourcompany.local
>>>>>>
>>>>>> Ethernet adapter Local Area Connection:
>>>>>>
>>>>>> Connection-specific DNS Suffix . :
>>>>>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>>>>>> Ethernet #2
>>>>>> Physical Address. . . . . . . . . : 00-1A-A0-0F-B3-07
>>>>>> DHCP Enabled. . . . . . . . . . . : No
>>>>>> IP Address. . . . . . . . . . . . : 192.168.1.5
>>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>>>> DNS Servers . . . . . . . . . . . : 192.168.1.5
>>>>>
>>>>> That all looks good.
>
>
>

Hank
Mon Aug 25 02:27:54 PDT 2008

I'd still go with Lanwench's recommendation. Set up DHCP and then assign
workstations IP addresses via DHCP.

BTW, if you do install DHCP, be sure to exclude all the fixed IP
addresses you have assigned. Also, add an exclusion range that you can
use later if you want to add more devices needing a fixed IP...

BTW, I disagree with Lanwench on one thing: I would *never* assign a
printer to DHCP. It can only cause problems if the printer is turned off
for some reason....

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

lenny wrote:
> Off course. The server has a static IP (192.168.1.5), there are only 2 PC's
> and 2 Laptops on the network plus a couple of printers and a router. The
> router already has a static as do the printers. Since setting the PC's to
> static IP's there hasn't been a problem, but it might just be a coincidence.
> I will be updating the drivers as recommended at the earliest opportunity.
> Cheers
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
> news:%23WIwzV5AJHA.3348@TK2MSFTNGP04.phx.gbl...
>> lenny <lenny@thetakeout.com> wrote:
>>> What about giving the workstations their own IP address
>> You mean statics? I wouldn't recommend that. Too much management overhead.
>> DHCP is the way to go.
>>
>>> and leaving
>>> the server on unlimited lease?
>> Servers should not be using DHCP anyway. Servers and network devices
>> should have statics - printers should have DHCP reservations or statics -
>> and workstations should be using DHCP.
>>
>> You can't set up a DHCP server to have a DHCP-assigned IP address, either,
>> note.

Lanwench
Tue Aug 26 16:06:36 PDT 2008

Hank Arnold (MVP) <rasilon@aol.com> wrote:
> I'd still go with Lanwench's recommendation.

<curtseys>

> Set up DHCP and then
> assign workstations IP addresses via DHCP.
>
> BTW, if you do install DHCP, be sure to exclude all the fixed IP
> addresses you have assigned. Also, add an exclusion range that you can
> use later if you want to add more devices needing a fixed IP...
>
> BTW, I disagree with Lanwench on one thing: I would *never* assign a
> printer to DHCP. It can only cause problems if the printer is turned
> off for some reason....

DHCP *reservations* ...not DHCP alone. That way if you move a printer to
another network, you don't have to scurry around looking for the manual so
you can reset it to factory defaults. So you end up with nonchanging IP
addresses for printers, but you don't have to worry about keeping track of
yet more static IPs. The fewer the better, in my book. Just my $.02.
>
>
> lenny wrote:
>> Off course. The server has a static IP (192.168.1.5), there are only
>> 2 PC's and 2 Laptops on the network plus a couple of printers and a
>> router. The router already has a static as do the printers. Since
>> setting the PC's to static IP's there hasn't been a problem, but it
>> might just be a coincidence. I will be updating the drivers as
>> recommended at the earliest opportunity. Cheers
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
>> message news:%23WIwzV5AJHA.3348@TK2MSFTNGP04.phx.gbl...
>>> lenny <lenny@thetakeout.com> wrote:
>>>> What about giving the workstations their own IP address
>>> You mean statics? I wouldn't recommend that. Too much management
>>> overhead. DHCP is the way to go.
>>>
>>>> and leaving
>>>> the server on unlimited lease?
>>> Servers should not be using DHCP anyway. Servers and network devices
>>> should have statics - printers should have DHCP reservations or
>>> statics - and workstations should be using DHCP.
>>>
>>> You can't set up a DHCP server to have a DHCP-assigned IP address,
>>> either, note.

lenny
Thu Aug 28 09:00:53 PDT 2008

Hi,
We have had about 5 days without any problems then today we were booted out
so I have updated the LAN Card driver to the latest version and 2 hours
later we are all kicked out again. There is still nothing showing in the
eventlogs.

Should I change the LAN card? It doesn't show up faulty in any way.

"lenny" <lenny@thetakeout.com> wrote in message
news:BoSdndC3Ur3-cTzVRVnyhAA@pipex.net...
> Hi,
> We have a Microsoft Server 2003 with 3 computers (XP Pro) connecting via a
> LAN to synchronise files in the shared folders. There is also a Draytek
> Vigor 2800 router for internet access with a static IP and DHCP disabled.
> The server is giving out the IP's for the client computers but about twice
> a day the clients are going 'Off Line', they loose their IP address (it
> reverts to 169.xxx....) and are unable to access the server or get onto
> the internet or print (The printer is set up through the server). I have
> tried giving the clients static IP's but the same thing happens anyway. I
> have also tried disabling and enabling the LAN connection on the clients.
> I can log on to the router from outside the LAN which has it's own static
> WAN and LAN IP but the server is not pingable (timed out). I reboot the
> server and the clients are then given an IP and we are back up and
> running. I have checked the Event Viewer but there doesn't seem to be
> anything relevant and there certainly isn't anything that relates to the
> times the connection is lost. 2 of the clients that are always on loose
> the connection about 5 minutes apart. One computer will say it is off line
> and 5 minutes later the other one will loose it too.
>
> First, I would like any advice about what might cause this on the server
> because I am sure rebooting it twice a day isn't normal. Also, could I
> take DHCP away from the server and give it to the Router instead? Why do
> they loose connection even when they have a static IP? Because of this I
> don't think getting the IP from the Router will make any difference. When
> the server decides it wants to close it's connection it will.
>
> Any advice greatly appreciated.
> Cheers
> Lenny
>

Lanwench
Fri Aug 29 18:49:45 PDT 2008

lenny <lenny@thetakeout.com> wrote:
> Hi,
> We have had about 5 days without any problems then today we were
> booted out

All at the same time?

> so I have updated the LAN Card driver to the latest
> version and 2 hours later we are all kicked out again. There is still
> nothing showing in the eventlogs.
>
> Should I change the LAN card? It doesn't show up faulty in any way.

Yes, I'd try an Intel. I don't much like Broadcoms. That isn't to say that
the Broadcom is the issue, mind you.

Also, what kind of switch?
>
> "lenny" <lenny@thetakeout.com> wrote in message
> news:BoSdndC3Ur3-cTzVRVnyhAA@pipex.net...
>> Hi,
>> We have a Microsoft Server 2003 with 3 computers (XP Pro) connecting
>> via a LAN to synchronise files in the shared folders. There is also
>> a Draytek Vigor 2800 router for internet access with a static IP and
>> DHCP disabled. The server is giving out the IP's for the client
>> computers but about twice a day the clients are going 'Off Line',
>> they loose their IP address (it reverts to 169.xxx....) and are
>> unable to access the server or get onto the internet or print (The
>> printer is set up through the server). I have tried giving the
>> clients static IP's but the same thing happens anyway. I have also
>> tried disabling and enabling the LAN connection on the clients. I
>> can log on to the router from outside the LAN which has it's own
>> static WAN and LAN IP but the server is not pingable (timed out). I
>> reboot the server and the clients are then given an IP and we are
>> back up and running. I have checked the Event Viewer but there
>> doesn't seem to be anything relevant and there certainly isn't
>> anything that relates to the times the connection is lost. 2 of the
>> clients that are always on loose the connection about 5 minutes
>> apart. One computer will say it is off line and 5 minutes later the
>> other one will loose it too. First, I would like any advice about what
>> might cause this on the
>> server because I am sure rebooting it twice a day isn't normal.
>> Also, could I take DHCP away from the server and give it to the
>> Router instead? Why do they loose connection even when they have a
>> static IP? Because of this I don't think getting the IP from the
>> Router will make any difference. When the server decides it wants to
>> close it's connection it will. Any advice greatly appreciated.
>> Cheers
>> Lenny

lenny
Sun Aug 31 11:51:47 PDT 2008

All at the same time within a few minutes of each other. The problem is that
the staff only notice that they are not working online when the sync icon in
the system tray pops up and tells them that they are working off line. This
could be when it try's to do a sync with the server instead of the actual
moment when the system is kicked out. We are just using a basic unmanaged 8
port belkin Ethernet switch/hub.


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:%23XVZmPkCJHA.4700@TK2MSFTNGP03.phx.gbl...
> lenny <lenny@thetakeout.com> wrote:
>> Hi,
>> We have had about 5 days without any problems then today we were
>> booted out
>
> All at the same time?
>
>> so I have updated the LAN Card driver to the latest
>> version and 2 hours later we are all kicked out again. There is still
>> nothing showing in the eventlogs.
>>
>> Should I change the LAN card? It doesn't show up faulty in any way.
>
> Yes, I'd try an Intel. I don't much like Broadcoms. That isn't to say that
> the Broadcom is the issue, mind you.
>
> Also, what kind of switch?
>>
>> "lenny" <lenny@thetakeout.com> wrote in message
>> news:BoSdndC3Ur3-cTzVRVnyhAA@pipex.net...
>>> Hi,
>>> We have a Microsoft Server 2003 with 3 computers (XP Pro) connecting
>>> via a LAN to synchronise files in the shared folders. There is also
>>> a Draytek Vigor 2800 router for internet access with a static IP and
>>> DHCP disabled. The server is giving out the IP's for the client
>>> computers but about twice a day the clients are going 'Off Line',
>>> they loose their IP address (it reverts to 169.xxx....) and are
>>> unable to access the server or get onto the internet or print (The
>>> printer is set up through the server). I have tried giving the
>>> clients static IP's but the same thing happens anyway. I have also
>>> tried disabling and enabling the LAN connection on the clients. I
>>> can log on to the router from outside the LAN which has it's own
>>> static WAN and LAN IP but the server is not pingable (timed out). I
>>> reboot the server and the clients are then given an IP and we are
>>> back up and running. I have checked the Event Viewer but there
>>> doesn't seem to be anything relevant and there certainly isn't
>>> anything that relates to the times the connection is lost. 2 of the
>>> clients that are always on loose the connection about 5 minutes
>>> apart. One computer will say it is off line and 5 minutes later the
>>> other one will loose it too. First, I would like any advice about what
>>> might cause this on the
>>> server because I am sure rebooti