Win2k networking oddity
 

Anybody know why win2k would refuse to allow any traffic with the LAN beyond pings and tracrets for a non-admin user? If I log in as administrator, everything works fine. As a regular user, I can ping and tracert to google.com, yahoo.com, etc., but I can not visit anything in a browser, connect with IM clients, etc. I can't even get to router or modem config pages, nothing on the LAN at all.

Re: Win2k networking oddity
 

Stand alone? Or domain member? If stand alone, was it ever a domain member or a client on a managed network?

Sounds like a proxy or gp issue, but it depends on what may have been done to it in the past. If it is a domain system, then YMBF. Also, it could be a DNS issue. UnkyS's boys have been doing some simms the last day or so. Try pinging your DNS servers, and perhaps add some of the big public servers to your list.

Re: Win2k networking oddity
 

I ran into this problem a while back. I recall posting about it and receiving a lot of advice. I was never able to fix it. I think it had to do with a recent MS update in my case that made, or rather as a side effect, caused changes thus causing my problem.

MS has been doing some strange things lately. Perhaps it is something they are now doing. Have you updated recently?

Re: Win2k networking oddity
 

The last update I did for WinME (yeah I know, shut up...) completely screwed my system. I had to uninstall it to get my display drivers working f.f.s.

~T~

Re: Win2k networking oddity
 

Never has been part of a domain. What is a "managed network?"

I have no idea what my DNS servers would be. Know what SBC uses? If it is a DNS problem, why would it only be a problem in regular user mode and not admin? Also, if it were DNS related, I should still be able to visit network locations, such as router config via IP address, right?

There have been no updates to the computer in at least a month.

Re: Win2k networking oddity
 

Managed network is a network that requires specific hard coded proxy settings and may apply gp settings to the system to control access. Used to be the big thing in some universities that were anti MS/ADDS.

DNS cache could have issues related to user accounts.

Log on as local admin
Run a SET from the console then an IPCONFIG /ALL then IPCONFIG /DISPLAYDNS PM me the results. (all have a space before the /)

Then type IPCONFIG /FLUSHDNS, now try it with both accounts.

As to your ISP’s DNS servers, I don’t have a clue. Email them. For now, bind these.
68.15.165.12
63.226.12.96
64.151.103.120
216.87.84.209

Try both accounts again.

Don’t worry if I don’t get right back to you right away. AM here I’m sitting with a hose in my arm, rest of the time I home, have yet to find out when I’ll be sleeping ;( but doubt it will happen tonight. At any rate, I will get back to you, promise http://forum.shrapnelgames.com/images/smilies/wink.gif

Re: Win2k networking oddity
 

PS: just for grins, turn off the fire wall if you are running one. Then see what you can ping.

Re: Win2k networking oddity
 

There is too much to capture in the ipconfig /displaydns output. Any way I can get it to dump to a file, some DOS equivalent to > operator?

Re: Win2k networking oddity
 

Its easy, just took me a while to remember it. Brain just is not quite ready for work yet.

Run your cmd line entry
Right click the comand window header-select edit- then l/c on select all
Repeat above but this time l/c on copy

Open note pad and use the paste option

Write this one in your cheat notes. I have yet to see it in a text book.

Re: Win2k networking oddity
 

You should be able to pipe it to a file with ">> filename"
Adding "| more" should send it through a little dos utility which pauses after each screenfull of text.