Limited or no connectivity... apparently

[Rick Rogers]

Hi Simon,

Just opening it from an admin account is not sufficient, you will not have
root privileges necessary to read/write/alter system files (this in part is
what uac is about), a process necessary for those commands to work. You
still need to self-elevate by right clicking the command prompt and choosing
the 'run as admin..' option.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

 

[Simon]

Just opening it from an admin account is not sufficient, you will not have
root privileges necessary to read/write/alter system files (this in part
is what uac is about), a process necessary for those commands to work. You
still need to self-elevate by right clicking the command prompt and
choosing the 'run as admin..' option.

Unless the user, (in that case me), has disabled the UAC, in that case the
run-> cmd runs as Admin by default.
I just could not take been asked to confirm one thing or another every 2
minutes.

Simon

 

[Rick Rogers]

If you were getting prompted that often, Simon, then you were using
incompatible programs or drivers. Once a system is set up, you should
encounter UAC prompts rather infrequently. Elevated privileges should not be
required for normal day to day operation.

Consider too that the use of incompatible software and drivers can often be
the cause of a host of inexplicable issues. Some compatible programs as well
will not respond properly when UAC is disabled as they expect it to be there
and can cause additional issues. This could include the network card driver
files. I generally recommend that a user disable UAC initially to setup the
system and install desired software, then re-eanble it for normal runtime.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

 

[Simon]

If you were getting prompted that often, Simon, then you were using

incompatible programs or drivers. Once a system is set up, you should
encounter UAC prompts rather infrequently. Elevated privileges should not
be required for normal day to day operation.

Well, maybe I over-exagerated a bit , maybe I don't get warned that often.
I guess I will re-enable it now that the network seems to be working.

Having said that, I still think that the problem is with VISTA.

I know you probably will not believe me but that machine has hardly any
third party software installed.
I have go to great length to keep it as 'clean' as I can.
If I have anything to install, (for work, fun or for testing), I first run
it on the XP machine and if it is something I like I will install in on the
VISTA box.

This is why I am sure that the problem must be with VISTA.

Simon

 

[Scott Roberts]

Well in the end I had to do it the dirty way and set a static address.
DHCP is obviously broken with some new updates of VISTA.

So now I have my VISTA machine as 192.168.0.1 and the other machine can
see me properly.

A bit of a hack, but at least it works.

Simon.

What's "broken", and what others have tried to tell you, is that when you
just wire 2 computers directly together and neither one is set up to be a
DHCP *Server* then no IP addresses are going to be assigned to either one.
The DHCP *Server* is typically your router, so when you remove it from your
"LAN" then of course the "LAN" is "broken". Setting static IPs is not a
"hack", it's a necessity when you don't have a DHCP Server set up.

The DHCP *Client* did change in Vista. You need to be sure your DHCP
*Server* is "Vista Compatible". Look here:
http://support.microsoft.com/kb/932134

This might be helpful too:
http://www.helpwithwindows.com/WindowsVista/troubleshooting-01.html