Forum Discussion
JasonNall_44907
Nimbostratus
NimbostratusSMB and Microsoft File Share Fun
I started a posting before on this topic and it eventually ended up in another direction.
To sum up my topology, I have a BigIP virtual IP address pointing to a pool of 2 physical servers, with an SMB monitor on port 445 for each.
All is working well for me from an access standpoint when I connect to the share via \\10.X.X.X (ip address).
The problem I am having is the transition from IP access to named access. \\SERVERNAME
If I use a name that does not exist in WINS, DNS, or active directory everything seems to be fine and the connection works.
Unfortunately, I need to reassign an existing name and assign it to the virtual IP address.
Has anyone done this yet, and if so what steps did you take. I am not sure if this is some sort of WINS resolution issue, and Netbios issue or what. Perhaps the machine can no longer exist in Active directory...etc.
Please help. This is the last step preventing me from rolling this out to my production floor.
The F5 appears to be functioning correctly, so I can't really contact support for this issue.
Thanks in advance
JasonNall_44907Well it seems I did finally figure this one out. I ended up actually having to remove the machine name I was trying to use from Active Directory. Once this was removed, and the changes replicated, I was able to access the \\SERVERNAME with no issue.
hoolioCirrostratus
Thanks for following up. Out of curiosity, if you remove the server from the domain, doesn't that prevent you from using domain authentication to log into the unit or accessing the share?
If you need to have the server in the domain for authentication, I think it might be helpful to look to Microsoft resources on the issue. I imagine other people have run into this issue before.
Aaron- JasonNall_44907Well if the server was in the domain, you would basically be saying that you had the machine name associated with the virtual ip address, as well as the physical ip address of the server.
In my instance, I needed to use the name of a server that I was planning on rebuilding..but that all my clients currently point at. Once it is rebuilt, I will name it something new, and make it the 2nd server in the file share pair...if that makes sense.