W2K drive mapping

Post #96,683

4/15/03 1:45:40 PM

W2K drive mapping

We recently had a windows 2000 server transferred from one location to another. In the process, the ip address got changed. For the most part everything works. From the outside, I can ping it, hit the web pages via http, hook up to it via terminal services, map the shared drives... IOW, everything that's been done in the past.

From within the server, I can ping my own address as well as other servers in the network; http and ftp work both inside and outside the server; I can even hook up terminal services to myself within the server.

I can do everything accept one thing - map network drives. I can't map any other drives in the network or even map the shared drives of the server itself:

net use k: \\myserver\\datadrive mypassword /user:myname /persistent:no

System error 1231 has occurred.

The network location cannot be reached. For information about network
troubleshooting, see Windows Help.

That command works fine from a Workstation, but fails on the server itself.

Not knowing much about how Windows maps disk resources, I am wondering where I should be looking for the problem?

Thanks.

Post #96,685

by boxley

4/15/03 2:08:31 PM

netbios and naming try ipaddress instead of name

will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]

questions, help? [link|mailto:pappas@catholic.org|email pappas at catholic.org]

Carpe Dieu

Post #96,690

by ChrisR

4/15/03 2:24:51 PM

Same result with the ip address

I can map to the server drive from the WorkStation via the ip address. Can't do it from the server - same error message as when using the server name.

Post #96,689

by folkert

4/15/03 2:21:17 PM

Are you using AD?

If you are, you need to change the IP Addy in the Directory.

If not, are you using a WINS server anywhere? If you are have the W2K report there and then you also refer it... then all should be well.

At least that is what I do in these cases. Ask Peter too...

b4k4^2

[link\|mailto:curley95@attbi.com\|greg] - IT Grand-Master for President
[link\|http://www.iwethey.org/ed_curry/\|REMEMBER ED CURRY!]
[link\|http://www.eweek.com/article2/0,3959,857673,00.asp\|2004, the year Microsoft develops for Linux ]
Heimatland Geheime Staatspolizei reminds: The DHS [link\|http://www.whitehouse.gov/pcipb/cyberspace_strategy.pdf\|Cyberer-Stratergery]. The ultimate in Cyber.

Post #96,706

by pwhysall

4/15/03 4:14:47 PM

Name resolution

Check for stale DNS and WINS records.

Post #96,707

by pwhysall

4/15/03 4:18:16 PM

Re: W2K drive mapping

Check that in changing the IP address, someone hasn't inadvertently disabled NetBIOS Over TCP/IP.

Post #97,089

by ChrisR

4/17/03 3:50:59 PM

Still cogitating.

I've got workarounds for most of the problems that it presents, so none of the Network people are giving me much time at the moment (they're too busy with moving the company over to Oracle financials at the moment).

Anyhow, I would think that if it were a DNS problem, that it would be inaccessible by name from other boxen as well. Looking at the 'Directory', I can see that the server shows up in the Domain and can be managed from there. But looking under the 'Microsoft Windows Network' for the same domain, the server doesn't show up.

Post #97,102

by Silverlock

4/17/03 4:20:33 PM

Check event viewer for more details

From MS Technet article 325122

When a packet is undeliverable, a Destination Unreachable ICMP Type 3 message is generated. Type 3 ICMP packets can have a code value of 0 to 15.

The following ICMP Type 3 codes values are defined in RFC 1812:

Hexadecimal Decimal Description
---------------------------------------------------------------------------
0x00 0 Network Unreachable - generated by a router if a forwarding path
(route) to the destination network is not available;

0x01 1 Host Unreachable - generated by a router if a forwarding path
(route) to the destination host on a directly connected network
is not available (does not respond to ARP);

0x02 2 Protocol Unreachable - generated if the transport protocol
designated in a datagram is not supported in the transport layer
of the final destination;

0x03 3 Port Unreachable - generated if the designated transport protocol
(e.g., UDP) is unable to demultiplex the datagram in the
transport layer of the final destination but has no protocol
mechanism to inform the sender;

0x04 4 Fragmentation Needed and DF Set - generated if a router needs to
fragment a datagram but cannot since the DF flag is set;

0x05 5 Source Route Failed - generated if a router cannot forward a
packet to the next hop in a source route option;

0x06 6 Destination Network Unknown - This code SHOULD NOT be generated
since it would imply on the part of the router that the
destination network does not exist (net unreachable code 0
SHOULD be used in place of code 6);

0x07 7 Destination Host Unknown - generated only when a router can
determine (from link layer advice) that the destination host
does not exist;

0x0B 11 Network Unreachable For Type Of Service - generated by a router
if a forwarding path (route) to the destination network with the
requested or default TOS is not available;

0x0C 12 Host Unreachable For Type Of Service - generated if a router
cannot forward a packet because its route(s) to the destination
do not match either the TOS requested in the datagram or the
default TOS (0).

0x0D 13 Communication Administratively Prohibited - generated if a
router cannot forward a packet due to administrative filtering;

0x0E 14 Host Precedence Violation. Sent by the first hop router to a
host to indicate that a requested precedence is not permitted
for the particular combination of source/destination host or
network, upper layer protocol, and source/destination port;

0x0F 15 Precedence cutoff in effect. The network operators have imposed
a minimum level of precedence required for operation, the
datagram was sent with a precedence below this level;

The world is only a simple place to the simple.

Welcome to IWETHEY!