XP clients loses connection- local and internet

Hi


sinds last friday it happens that users loses their internet connection but
still can access local resources ( networkdrives/exchange/printers etc..),
and sometime
both of them are unavailable.
it also happens that when everybody is out , still one clientcomputer is
working fine.
Ipconfig looks fine during that time
when doing a ipconfig /release/renew everything works again having the same
ip/gateway/dhcpserver, but on a irregular time clients can lose their
connection again.
when the clientscomputers are out their is still internet on the server.



allready done=

reboot server
releasing/renewing all ip's in the dhcp server
installing Server sp2
reset mainswitch
reset modem
reset security gateway
checking the eventviewer ( looks fine)
checking dns services ( look also fine)


gonna do =
see if the server can access clients with ping or a shared map during timeout
nslookup, see if i can call google by Ip adress
......


what has changed last week =
i've added a sitecom accespoint
wpa2 secured with macfilter


can someone help me out ?

the workaround is a batchfile on every client his desktop to release/renew
the ip.



1 X windows server 2003 SBS SP2
exchangeserver 2003 sp2
Backup exec 11d 7071
15 X windows xp sp2 fully updated

What DNS server do these clients point to for their Alternate DNS server?

hth
DDS

"maxime" <(E-Mail Removed)> wrote in message
news:329BC21A-0825-49A0-A176-(E-Mail Removed)...
> Hi
>
>
> sinds last friday it happens that users loses their internet connection
> but
> still can access local resources ( networkdrives/exchange/printers etc..),
> and sometime
> both of them are unavailable.
> it also happens that when everybody is out , still one clientcomputer is
> working fine.
> Ipconfig looks fine during that time
> when doing a ipconfig /release/renew everything works again having the
> same
> ip/gateway/dhcpserver, but on a irregular time clients can lose their
> connection again.
> when the clientscomputers are out their is still internet on the server.
>
>
>
> allready done=
>
> reboot server
> releasing/renewing all ip's in the dhcp server
> installing Server sp2
> reset mainswitch
> reset modem
> reset security gateway
> checking the eventviewer ( looks fine)
> checking dns services ( look also fine)
>
>
> gonna do =
> see if the server can access clients with ping or a shared map during
> timeout
> nslookup, see if i can call google by Ip adress
> .....
>
>
> what has changed last week =
> i've added a sitecom accespoint
> wpa2 secured with macfilter
>
>
> can someone help me out ?
>
> the workaround is a batchfile on every client his desktop to release/renew
> the ip.
>
>
>
> 1 X windows server 2003 SBS SP2
> exchangeserver 2003 sp2
> Backup exec 11d 7071
> 15 X windows xp sp2 fully updated
>
>
>
>

hi,
thnx for your reply

Primary DNS is the server itself
Secondary is the DNS of the Internet Provider
the problem can jump from one computer to another.

i know they encountered multiple powershutdowns last week.
is it possible that the mainswitch is doing weird after that.
only the server and firewall is on UPS

this switch is a 3COM 24-ports 10mb/100mb/1G
4 years old.

thank you

maxime

"Danny Sanders" wrote:

> What DNS server do these clients point to for their Alternate DNS server?
>
> hth
> DDS
>
> "maxime" <(E-Mail Removed)> wrote in message
> news:329BC21A-0825-49A0-A176-(E-Mail Removed)...
> > Hi
> >
> >
> > sinds last friday it happens that users loses their internet connection
> > but
> > still can access local resources ( networkdrives/exchange/printers etc..),
> > and sometime
> > both of them are unavailable.
> > it also happens that when everybody is out , still one clientcomputer is
> > working fine.
> > Ipconfig looks fine during that time
> > when doing a ipconfig /release/renew everything works again having the
> > same
> > ip/gateway/dhcpserver, but on a irregular time clients can lose their
> > connection again.
> > when the clientscomputers are out their is still internet on the server.
> >
> >
> >
> > allready done=
> >
> > reboot server
> > releasing/renewing all ip's in the dhcp server
> > installing Server sp2
> > reset mainswitch
> > reset modem
> > reset security gateway
> > checking the eventviewer ( looks fine)
> > checking dns services ( look also fine)
> >
> >
> > gonna do =
> > see if the server can access clients with ping or a shared map during
> > timeout
> > nslookup, see if i can call google by Ip adress
> > .....
> >
> >
> > what has changed last week =
> > i've added a sitecom accespoint
> > wpa2 secured with macfilter
> >
> >
> > can someone help me out ?
> >
> > the workaround is a batchfile on every client his desktop to release/renew
> > the ip.
> >
> >
> >
> > 1 X windows server 2003 SBS SP2
> > exchangeserver 2003 sp2
> > Backup exec 11d 7071
> > 15 X windows xp sp2 fully updated
> >
> >
> >
> >
>
>
>

> Secondary is the DNS of the Internet Provider

That is your problem. AD clients should point to the DNS server setup for
the AD domain ONLY.
For Internet access set up forwarders on the DNS server, see:

How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default...b;en-us;323380

The ONLY place on an AD domain your ISP's DNS server(s) should be listed is
as forwarders.

hth
DDS

"maxime" <(E-Mail Removed)> wrote in message
news:17AB6462-61C5-443B-8FE7-(E-Mail Removed)...
> hi,
> thnx for your reply
>
> Primary DNS is the server itself
> Secondary is the DNS of the Internet Provider
> the problem can jump from one computer to another.
>
> i know they encountered multiple powershutdowns last week.
> is it possible that the mainswitch is doing weird after that.
> only the server and firewall is on UPS
>
> this switch is a 3COM 24-ports 10mb/100mb/1G
> 4 years old.
>
> thank you
>
> maxime
>
> "Danny Sanders" wrote:
>
>> What DNS server do these clients point to for their Alternate DNS
>> server?
>>
>> hth
>> DDS
>>
>> "maxime" <(E-Mail Removed)> wrote in message
>> news:329BC21A-0825-49A0-A176-(E-Mail Removed)...
>> > Hi
>> >
>> >
>> > sinds last friday it happens that users loses their internet connection
>> > but
>> > still can access local resources ( networkdrives/exchange/printers
>> > etc..),
>> > and sometime
>> > both of them are unavailable.
>> > it also happens that when everybody is out , still one clientcomputer
>> > is
>> > working fine.
>> > Ipconfig looks fine during that time
>> > when doing a ipconfig /release/renew everything works again having the
>> > same
>> > ip/gateway/dhcpserver, but on a irregular time clients can lose their
>> > connection again.
>> > when the clientscomputers are out their is still internet on the
>> > server.
>> >
>> >
>> >
>> > allready done=
>> >
>> > reboot server
>> > releasing/renewing all ip's in the dhcp server
>> > installing Server sp2
>> > reset mainswitch
>> > reset modem
>> > reset security gateway
>> > checking the eventviewer ( looks fine)
>> > checking dns services ( look also fine)
>> >
>> >
>> > gonna do =
>> > see if the server can access clients with ping or a shared map during
>> > timeout
>> > nslookup, see if i can call google by Ip adress
>> > .....
>> >
>> >
>> > what has changed last week =
>> > i've added a sitecom accespoint
>> > wpa2 secured with macfilter
>> >
>> >
>> > can someone help me out ?
>> >
>> > the workaround is a batchfile on every client his desktop to
>> > release/renew
>> > the ip.
>> >
>> >
>> >
>> > 1 X windows server 2003 SBS SP2
>> > exchangeserver 2003 sp2
>> > Backup exec 11d 7071
>> > 15 X windows xp sp2 fully updated
>> >
>> >
>> >
>> >
>>
>>
>>

Hi Danny

I found the problem
There is also one AccessPoint on this network which has being there for a
long time.
During the troubleshooting i replaced the main switch with a 3com manageable
switch. It has all kinds of monitoring tools. That way I found out that the
access point was acting weird
When I disabled the access point, everything was solved.

Many thanks for your reply

best regards
maxime



"Danny Sanders" wrote:

> > Secondary is the DNS of the Internet Provider
>
> That is your problem. AD clients should point to the DNS server setup for
> the AD domain ONLY.
> For Internet access set up forwarders on the DNS server, see:
>
> How to configure DNS for Internet access in Windows Server 2003
>
> http://support.microsoft.com/default...b;en-us;323380
>
> The ONLY place on an AD domain your ISP's DNS server(s) should be listed is
> as forwarders.
>
> hth
> DDS
>
> "maxime" <(E-Mail Removed)> wrote in message
> news:17AB6462-61C5-443B-8FE7-(E-Mail Removed)...
> > hi,
> > thnx for your reply
> >
> > Primary DNS is the server itself
> > Secondary is the DNS of the Internet Provider
> > the problem can jump from one computer to another.
> >
> > i know they encountered multiple powershutdowns last week.
> > is it possible that the mainswitch is doing weird after that.
> > only the server and firewall is on UPS
> >
> > this switch is a 3COM 24-ports 10mb/100mb/1G
> > 4 years old.
> >
> > thank you
> >
> > maxime
> >
> > "Danny Sanders" wrote:
> >
> >> What DNS server do these clients point to for their Alternate DNS
> >> server?
> >>
> >> hth
> >> DDS
> >>
> >> "maxime" <(E-Mail Removed)> wrote in message
> >> news:329BC21A-0825-49A0-A176-(E-Mail Removed)...
> >> > Hi
> >> >
> >> >
> >> > sinds last friday it happens that users loses their internet connection
> >> > but
> >> > still can access local resources ( networkdrives/exchange/printers
> >> > etc..),
> >> > and sometime
> >> > both of them are unavailable.
> >> > it also happens that when everybody is out , still one clientcomputer
> >> > is
> >> > working fine.
> >> > Ipconfig looks fine during that time
> >> > when doing a ipconfig /release/renew everything works again having the
> >> > same
> >> > ip/gateway/dhcpserver, but on a irregular time clients can lose their
> >> > connection again.
> >> > when the clientscomputers are out their is still internet on the
> >> > server.
> >> >
> >> >
> >> >
> >> > allready done=
> >> >
> >> > reboot server
> >> > releasing/renewing all ip's in the dhcp server
> >> > installing Server sp2
> >> > reset mainswitch
> >> > reset modem
> >> > reset security gateway
> >> > checking the eventviewer ( looks fine)
> >> > checking dns services ( look also fine)
> >> >
> >> >
> >> > gonna do =
> >> > see if the server can access clients with ping or a shared map during
> >> > timeout
> >> > nslookup, see if i can call google by Ip adress
> >> > .....
> >> >
> >> >
> >> > what has changed last week =
> >> > i've added a sitecom accespoint
> >> > wpa2 secured with macfilter
> >> >
> >> >
> >> > can someone help me out ?
> >> >
> >> > the workaround is a batchfile on every client his desktop to
> >> > release/renew
> >> > the ip.
> >> >
> >> >
> >> >
> >> > 1 X windows server 2003 SBS SP2
> >> > exchangeserver 2003 sp2
> >> > Backup exec 11d 7071
> >> > 15 X windows xp sp2 fully updated
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
>
>

>> > Primary DNS is the server itself
>> > Secondary is the DNS of the Internet Provider
>> > the problem can jump from one computer to another.

You still can not have your AD clients pointing to a DNS server not setup
for the AD domain. Pointing them to your ISP as the alternate DNS server is
not the proper setup for an AD domain.


hth
DDS

"maxime" <(E-Mail Removed)> wrote in message
news144C9E5-B192-4AE7-BE7D-(E-Mail Removed)...
> Hi Danny
>
> I found the problem
> There is also one AccessPoint on this network which has being there for a
> long time.
> During the troubleshooting i replaced the main switch with a 3com
> manageable
> switch. It has all kinds of monitoring tools. That way I found out that
> the
> access point was acting weird
> When I disabled the access point, everything was solved.
>
> Many thanks for your reply
>
> best regards
> maxime
>
>
>
> "Danny Sanders" wrote:
>
>> > Secondary is the DNS of the Internet Provider
>>
>> That is your problem. AD clients should point to the DNS server setup for
>> the AD domain ONLY.
>> For Internet access set up forwarders on the DNS server, see:
>>
>> How to configure DNS for Internet access in Windows Server 2003
>>
>> http://support.microsoft.com/default...b;en-us;323380
>>
>> The ONLY place on an AD domain your ISP's DNS server(s) should be listed
>> is
>> as forwarders.
>>
>> hth
>> DDS
>>
>> "maxime" <(E-Mail Removed)> wrote in message
>> news:17AB6462-61C5-443B-8FE7-(E-Mail Removed)...
>> > hi,
>> > thnx for your reply
>> >
>> > Primary DNS is the server itself
>> > Secondary is the DNS of the Internet Provider
>> > the problem can jump from one computer to another.
>> >
>> > i know they encountered multiple powershutdowns last week.
>> > is it possible that the mainswitch is doing weird after that.
>> > only the server and firewall is on UPS
>> >
>> > this switch is a 3COM 24-ports 10mb/100mb/1G
>> > 4 years old.
>> >
>> > thank you
>> >
>> > maxime
>> >
>> > "Danny Sanders" wrote:
>> >
>> >> What DNS server do these clients point to for their Alternate DNS
>> >> server?
>> >>
>> >> hth
>> >> DDS
>> >>
>> >> "maxime" <(E-Mail Removed)> wrote in message
>> >> news:329BC21A-0825-49A0-A176-(E-Mail Removed)...
>> >> > Hi
>> >> >
>> >> >
>> >> > sinds last friday it happens that users loses their internet
>> >> > connection
>> >> > but
>> >> > still can access local resources ( networkdrives/exchange/printers
>> >> > etc..),
>> >> > and sometime
>> >> > both of them are unavailable.
>> >> > it also happens that when everybody is out , still one
>> >> > clientcomputer
>> >> > is
>> >> > working fine.
>> >> > Ipconfig looks fine during that time
>> >> > when doing a ipconfig /release/renew everything works again having
>> >> > the
>> >> > same
>> >> > ip/gateway/dhcpserver, but on a irregular time clients can lose
>> >> > their
>> >> > connection again.
>> >> > when the clientscomputers are out their is still internet on the
>> >> > server.
>> >> >
>> >> >
>> >> >
>> >> > allready done=
>> >> >
>> >> > reboot server
>> >> > releasing/renewing all ip's in the dhcp server
>> >> > installing Server sp2
>> >> > reset mainswitch
>> >> > reset modem
>> >> > reset security gateway
>> >> > checking the eventviewer ( looks fine)
>> >> > checking dns services ( look also fine)
>> >> >
>> >> >
>> >> > gonna do =
>> >> > see if the server can access clients with ping or a shared map
>> >> > during
>> >> > timeout
>> >> > nslookup, see if i can call google by Ip adress
>> >> > .....
>> >> >
>> >> >
>> >> > what has changed last week =
>> >> > i've added a sitecom accespoint
>> >> > wpa2 secured with macfilter
>> >> >
>> >> >
>> >> > can someone help me out ?
>> >> >
>> >> > the workaround is a batchfile on every client his desktop to
>> >> > release/renew
>> >> > the ip.
>> >> >
>> >> >
>> >> >
>> >> > 1 X windows server 2003 SBS SP2
>> >> > exchangeserver 2003 sp2
>> >> > Backup exec 11d 7071
>> >> > 15 X windows xp sp2 fully updated
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>