Woops, made a mistake in my server list table.
It should have been:
EXXB35 - 2003 - XX.207.42.198
EXX582 - 2003 - XX.207.42.19
EXX581 - 2000 - XX.207.42.18
EXX2DC - 2000 - XX.207.42.145
Only one machine with the 581 name! :)
The 2003 machines are unable to map to the 2000 machines, but...
If you already have the 2000 server book, start reading and look for the 2003 book. There are some very big changes in how 2000 and 2003 work, but very few of them for the most part.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
It should be there, are you sure the computer is a member of the domain and are you signed on with a domain admin account? If their is no GPO then the local settings ARE the effective settings, check if the GPO has been applied or not.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
I am going to bet that it is a problem with the source and not the destination. Are you reading from a CD/DVD-ROM or from a network share that you only have READ rights to?
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
Check the secure channel for the workstation member, does it report the primary domain and a valid DC as it's connection?
From another workstation perform: NBTSTAT -a COMPUTER
and report the results.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
OK guys,
The client has multiple Windows 2003 Servers that are unable to connect via UNC to multiple Windows 2000 Servers in the same domain. I have been trying to isolate the problem using 4 servers. 2 of them Windows 2000 and 2 Windows 2003. All 4 of these servers are at the same data...
Have you looked at using ROBOCOPY? It can traverse deep paths, log all output and even delete source files as it goes. Hopefully you have a copy of this utility somewhere. :)
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
By default it is likely blocking all ports. You will need to set up forwarding of 80 (and 443 if you want to use SSL) to the system running IIS.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
Sounds like a firewall issue. Looks like Port 80 isn't being allowed to pass in to the site from the outside world.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
Could be just a DNS issue.
Try adding an entry into your HOSTS file to force local resolution of the IP address.
pugetsound.office.local 192.168.200.192
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
Wow, I had to dig all the way to the bottom of page 6 to find this thread again. I'm just glad I support the servers and not the workstations, but SP2 is going to make my work day busy once implimented here.
Installing on a machine to find out what will and won't work so I'm better prepared...
from the command prompt "AT" can add scheduled tasks that run in the background (or interactively).
"at /?" for complete syntax.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
bofh,
No, no offense here. I look at MS with a bit of love and hate. It's anoying to be locked into not being able to use a tool that COULD work on a given platform just because Microsoft doesn't want to release it for that platform. On the other side you have to appreciate that they are in...
Bill,
Again, good catch. Local group for that user needs to be administrators in order to map LPT1 with net use, that totally slipped my mind and I was thinking of access on the remote system. :)
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
It is definately a driver problem. What kind of hardware are you installing to?
Try removing any extra hardware you can before the install. Replace any USB input devices with PS2 (keyboard and mouse). Remove the network cards and sound cards if you can. Install each component individually...
Sounds like the links were deleted, copy from another machine.
I manage a lot of servers with terminal services sessions and I find that some of the machines have had their tools made "invisible" through recycling of bits. I copied the links to a path and just \\server\me\admintools\ to get...
This is default behavior for windows clients (and servers) when you login to them. Sounds like you fixed your roaming problem though.
Nathan aka: zaz (zaznet)
zaz@zaz.net
http://www.zaz.net/
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.