Problem connecting to fileserver after new install of XP Pro SP1

From: Steve Grosz (boise_bound_at_hotmail.com)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 14:30:08 -0700

I have just built up a new AMD64, and put XP Pro SP1 on it. I installed
the built in networking card drivers, and verified I am getting a IP
address. I can connect to the internet fine, but when I'm trying to
reach \\web2\temp for example, I am unable to. I'm not prompted for my
username,password, etc. I can't ping it either.

Any ideas what might be causing this? I set this machine up to have the
WORKGROUP domain since I'm not using AD.

Thanks!
Steve

Relevant Pages

  • Problem connecting to fileserver after new install of XP Pro SP1
    ... I have just built up a new AMD64, and put XP Pro SP1 on it. ... the built in networking card drivers, and verified I am getting a IP ...
    (microsoft.public.windowsxp.general)
  • if_ed on !i386
    ... It works on in amd64 under qemu (about the only time you're likely to find ... If there is no reason it isn't built by default can someone commit this patch? ... _cpufreq= cpufreq ...
    (freebsd-current)
  • Re: acpi.ko not being built?
    ... I'm attempting to upgrade a server to amd64 CURRENT from an older snapshot. ... On amd64 acpi is compiled in the the kernel rather than built ...
    (freebsd-current)
  • Re: acpi.ko not being built?
    ... I'm attempting to upgrade a server to amd64 CURRENT from an older snapshot. ... acpi_*.ko files are being built, ... Since ACPI is mandatory on amd64, ...
    (freebsd-current)
  • Re: acpi.ko not being built?
    ... I'm attempting to upgrade a server to amd64 CURRENT from an older ... built as a module. ... It turns out freq is a sysctl provided by cpufreq and has nothing to do with acpi. ...
    (freebsd-current)