PDA

View Full Version : Network not working as non-admin (WinXP SP2)


Jan Woulfenberg
December 28th 04, 05:32 PM
Hello,
since a few days, all non-admin accounts on my WinXP SP2 box are
unable to access any network related ressources.

I think, it is the same problem as in KB32945
(http://support.microsoft.com/default.aspx?scid=kb;en-us;329405
Cause: The DNS resolver library uses Local Procedure Calls (LPCs) to
the DNS Client service. The default security was changed in SP3for LPC
ports. In some cases, this can prevent LPC calls to the DNS client for
users who are not members of the Administrators group.) but thats just
for Win2k SP3 and was fixed in SP4.

The symptons are the same:

- a DNS request always results in "No response from server"
- Pings are possible if the IP adress is known, but after entering the
command, the PC beeps and the output looks like the following (sorry
for the german text):

---snip-------------------------------------
C:\ping 192.168.178.1

Ping wird ausgeführt für °˙ mit 32 Bytes Daten:

Antwort von 192.168.178.1: Bytes=32 Zeit=7ms TTL=255
Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255

Ping-Statistik für :
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 2ms, Maximum = 7ms, Mittelwert = 3ms
---snap-------------------------------------

there is this strange string "°˙" and the blanks after "Ping-Statistik
für" *?*
(192.168.178.1 is my router and DNS server)

all this is happening even if i am logged in with an admin account
where the network is fully working (fast user switching-feature).

I didn't install anything unregular and switching the firewall
(Sygate) off has no effect. All updates are applied through the
windows update.

If i grant the affected user admin rights, the problem is gone, but
thats a very odd solution.

Any help is appreciated.

Thank you.

Jan Woulfenberg, Germany
IT Professional

Chuck
December 28th 04, 06:03 PM
On 28 Dec 2004 08:32:47 -0800, *email_address_deleted* (Jan Woulfenberg) wrote:

>Hello,
>since a few days, all non-admin accounts on my WinXP SP2 box are
>unable to access any network related ressources.
>
>I think, it is the same problem as in KB32945
>(http://support.microsoft.com/default.aspx?scid=kb;en-us;329405
>Cause: The DNS resolver library uses Local Procedure Calls (LPCs) to
>the DNS Client service. The default security was changed in SP3for LPC
>ports. In some cases, this can prevent LPC calls to the DNS client for
>users who are not members of the Administrators group.) but thats just
>for Win2k SP3 and was fixed in SP4.
>
>The symptons are the same:
>
>- a DNS request always results in "No response from server"
>- Pings are possible if the IP adress is known, but after entering the
>command, the PC beeps and the output looks like the following (sorry
>for the german text):
>
>---snip-------------------------------------
>C:\ping 192.168.178.1
>
>Ping wird ausgeführt für °˙ mit 32 Bytes Daten:
>
>Antwort von 192.168.178.1: Bytes=32 Zeit=7ms TTL=255
>Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>
>Ping-Statistik für :
> Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
>Ca. Zeitangaben in Millisek.:
> Minimum = 2ms, Maximum = 7ms, Mittelwert = 3ms
>---snap-------------------------------------
>
>there is this strange string "°˙" and the blanks after "Ping-Statistik
>für" *?*
>(192.168.178.1 is my router and DNS server)
>
>all this is happening even if i am logged in with an admin account
>where the network is fully working (fast user switching-feature).
>
>I didn't install anything unregular and switching the firewall
>(Sygate) off has no effect. All updates are applied through the
>windows update.
>
>If i grant the affected user admin rights, the problem is gone, but
>thats a very odd solution.
>
>Any help is appreciated.
>
>Thank you.
>
>Jan Woulfenberg, Germany
>IT Professional

Jan,

Your problem has the symptoms of LSP / Winsock or TCP/IP corruption. DNS
resolution is affected by the LSP / Winsock subsystem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

With XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog" into the
command window.

Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html> a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

woulfenberg@gmx.net
December 29th 04, 01:01 AM
Chuck wrote:
> On 28 Dec 2004 08:32:47 -0800, *email_address_deleted* (Jan
Woulfenberg) wrote:
>
> >Hello,
> >since a few days, all non-admin accounts on my WinXP SP2 box are
> >unable to access any network related ressources.
> >
> >I think, it is the same problem as in KB32945
> >(http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;329405
> >Cause: The DNS resolver library uses Local Procedure Calls (LPCs) to
> >the DNS Client service. The default security was changed in SP3for
LPC
> >ports. In some cases, this can prevent LPC calls to the DNS client
for
> >users who are not members of the Administrators group.) but thats
just
> >for Win2k SP3 and was fixed in SP4.
> >
> >The symptons are the same:
> >
> >- a DNS request always results in "No response from server"
> >- Pings are possible if the IP adress is known, but after entering
the
> >command, the PC beeps and the output looks like the following (sorry
> >for the german text):
> >
> >---snip-------------------------------------
> >C:\ping 192.168.178.1
> >
> >Ping wird ausgef=FChrt f=FCr =B0=FF mit 32 Bytes Daten:
> >
> >Antwort von 192.168.178.1: Bytes=3D32 Zeit=3D7ms TTL=3D255
> >Antwort von 192.168.178.1: Bytes=3D32 Zeit=3D2ms TTL=3D255
> >Antwort von 192.168.178.1: Bytes=3D32 Zeit=3D2ms TTL=3D255
> >Antwort von 192.168.178.1: Bytes=3D32 Zeit=3D2ms TTL=3D255
> >
> >Ping-Statistik f=FCr :
> > Pakete: Gesendet =3D 4, Empfangen =3D 4, Verloren =3D 0 (0% Verlust),
> >Ca. Zeitangaben in Millisek.:
> > Minimum =3D 2ms, Maximum =3D 7ms, Mittelwert =3D 3ms
> >---snap-------------------------------------
> >
> >there is this strange string "=B0=FF" and the blanks after
"Ping-Statistik
> >f=FCr" *?*
> >(192.168.178.1 is my router and DNS server)
> >
> >all this is happening even if i am logged in with an admin account
> >where the network is fully working (fast user switching-feature).
> >
> >I didn't install anything unregular and switching the firewall
> >(Sygate) off has no effect. All updates are applied through the
> >windows update.
> >
> >If i grant the affected user admin rights, the problem is gone, but
> >thats a very odd solution.
> >
> >Any help is appreciated.
> >
> >Thank you.
> >
> >Jan Woulfenberg, Germany
> >IT Professional
>
> Jan,
>
> Your problem has the symptoms of LSP / Winsock or TCP/IP corruption.
DNS
> resolution is affected by the LSP / Winsock subsystem.
> http://support.microsoft.com/?id=3D318584
> http://support.microsoft.com/?id=3D811259
>
> With XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog"
into the
> command window.
>
> Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
> <http://www.tacktech.com/display.cfm?ttid=3D257>, or WinsockXPFix
> <http://www.spychecker.com/program/winsockxpfix.html> a shot.
>
> If no help yet, reset TCP/IP.
> http://support.microsoft.com/?id=3D299357
>
> Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the
command
> window.
>
> --
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.


Thank you very much, Chuck, my problem is solved!

I run the program "WinSock XP Fix 1.2"
(http://www.spychecker.com/program/winsockxpfix.html) and after
rebooting the machine the problem was gone :)

The backup function from "WinSock XP Fix 1.2" didn't work, but I
already had a backup.

Bye
Jan Woulfenberg

Chuck
December 29th 04, 05:28 AM
On 28 Dec 2004 16:01:28 -0800, wrote:

>Chuck wrote:
>> On 28 Dec 2004 08:32:47 -0800, *email_address_deleted* (Jan
>Woulfenberg) wrote:
>>
>> >Hello,
>> >since a few days, all non-admin accounts on my WinXP SP2 box are
>> >unable to access any network related ressources.
>> >
>> >I think, it is the same problem as in KB32945
>> >(http://support.microsoft.com/default.aspx?scid=kb;en-us;329405
>> >Cause: The DNS resolver library uses Local Procedure Calls (LPCs) to
>> >the DNS Client service. The default security was changed in SP3for
>LPC
>> >ports. In some cases, this can prevent LPC calls to the DNS client
>for
>> >users who are not members of the Administrators group.) but thats
>just
>> >for Win2k SP3 and was fixed in SP4.
>> >
>> >The symptons are the same:
>> >
>> >- a DNS request always results in "No response from server"
>> >- Pings are possible if the IP adress is known, but after entering
>the
>> >command, the PC beeps and the output looks like the following (sorry
>> >for the german text):
>> >
>> >---snip-------------------------------------
>> >C:\ping 192.168.178.1
>> >
>> >Ping wird ausgeführt für °˙ mit 32 Bytes Daten:
>> >
>> >Antwort von 192.168.178.1: Bytes=32 Zeit=7ms TTL=255
>> >Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>> >Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>> >Antwort von 192.168.178.1: Bytes=32 Zeit=2ms TTL=255
>> >
>> >Ping-Statistik für :
>> > Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
>> >Ca. Zeitangaben in Millisek.:
>> > Minimum = 2ms, Maximum = 7ms, Mittelwert = 3ms
>> >---snap-------------------------------------
>> >
>> >there is this strange string "°˙" and the blanks after
>"Ping-Statistik
>> >für" *?*
>> >(192.168.178.1 is my router and DNS server)
>> >
>> >all this is happening even if i am logged in with an admin account
>> >where the network is fully working (fast user switching-feature).
>> >
>> >I didn't install anything unregular and switching the firewall
>> >(Sygate) off has no effect. All updates are applied through the
>> >windows update.
>> >
>> >If i grant the affected user admin rights, the problem is gone, but
>> >thats a very odd solution.
>> >
>> >Any help is appreciated.
>> >
>> >Thank you.
>> >
>> >Jan Woulfenberg, Germany
>> >IT Professional
>>
>> Jan,
>>
>> Your problem has the symptoms of LSP / Winsock or TCP/IP corruption.
>DNS
>> resolution is affected by the LSP / Winsock subsystem.
>> http://support.microsoft.com/?id=318584
>> http://support.microsoft.com/?id=811259
>>
>> With XP SP2, Start - Run - "cmd". Type "netsh winsock reset catalog"
>into the
>> command window.
>>
>> Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
>> <http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
>> <http://www.spychecker.com/program/winsockxpfix.html> a shot.
>>
>> If no help yet, reset TCP/IP.
>> http://support.microsoft.com/?id=299357
>>
>> Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the
>command
>> window.
>>
>> --
>> Cheers,
>> Chuck
>> Paranoia comes from experience - and is not necessarily a bad thing.
>
>
>Thank you very much, Chuck, my problem is solved!
>
>I run the program "WinSock XP Fix 1.2"
>(http://www.spychecker.com/program/winsockxpfix.html) and after
>rebooting the machine the problem was gone :)
>
>The backup function from "WinSock XP Fix 1.2" didn't work, but I
>already had a backup.
>
>Bye
>Jan Woulfenberg

Excellent, Jan! Thanks for the feedback!

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Google