FQDN\path... There are other emails that went out to the rest of the
campus after I sent mine to the listserv so I believe it is probably a
routing issue.
Z.V.
Al Mulnick wrote:
When you say that they cannot see the shares, how are you checking?
FQDN\path or Computer Browser or some variation of that?
On 1/12/07, *Za Vue * <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Win23 AD:
From workstations in subnet A:
I can not map to server shares in subnet B. But if I log in to the
DC-1
in subnet A I have no problem mapping to all shares on my subnets.
And I
can also see all admin shares on workstations.
The same goes for subnet B when I log in to a workstation. I
cannot see
server shares in subnet A. I can log into DC-2 in subnet B and access
all shares. Both DCs are DNS servers. Both servers replicate
fine and
no strange log. Internet access is fine. Firewalls have been
turned off.
WTF!!
So in other words, only the domain controllers can see and map to all
the nodes in the LAN. Ping fails from DC-1 subnet A to machines in
subnet B. DCs have been restarted. No problem with user logon because
both DCs are working properly and replicating fine.
I am convince it is a switch issue.
-Z.V.
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
<http://www.activedir.org/ma/default.aspx>
