Netapp & Vista

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Ok, my problem is like this:
MY machines are Vista Ent. 5384 X86\x64
I have a Netapp machines, lets assign an ip to it of 10.10.10.10 (Example)
I have a Production Domain with it's own DNS\DHCP and a TestLab domain with
it's own DNS\DHCP

On both the Netapp is registered on the DNS as Host A
1. On my production netowork, when i'm on a Wrokgroup i can access the
netapp OK using \\10.10.10.10 or \\Netapp

2. When i'm on The Testlab and within the domain everything is ok too

3. The problem is when i join my production domain i suddenly can't access
netapp through the UNC (\\Netapp), IP is still connectable, and i can ping &
Resolve the Netapp name OK but CANNOT access it. (The Production DNS is
configured with the same Host A record as the Lab's DNS, although, on the
production there's Two DNS servers)
 
I noticed also that I'm unable to connect to my netapp box from my Vista
workstation.

I did not troubleshoot yet but I guess Vista upgrade something in the
network stack that netapp don't understand.

-Sylvain
 
I suspect it's something to do with DNS, because as i said before, this
worked on my Testlab domain but only after i've manually registered a Host A
record of the Netapp. and also, on the production network, it worked when i
was on a WORKGROUP, and stopped working when i've joined the domain
 
I'm also seeing this problem in our production domain. My Vista Beta 2 that
I joined to our production domain cannot access our NetApp with the \\<name>
designation. After inputting the user-id and password the window just
dissappears. Only by using the \\<ip> does mapping shares from our Netapp
works. We also use 2 DNS servers too.
 
Ah, the roaming profiles were using NetBios names for the NetApps. Used the
dfs name/shares for the NetApp shares and everything is good.
 
So, what excatly did you change to make it work?
Disable Netbios on "Network Connections"?
 
Back
Top