odd ad problem

Hi,
Got a weird one for you.

We have an AD domain which we have set up trusts with our other AD domains (each remote office has it's own and this domain is seperate to our main one, don't ask me why cause I didn't set them up, I got brought into the network team after the big AD migration from NT took place :/ ) so that they can log onto the citrix servers (with win2k terminal services running behind them) using their own logon in their own domain.

Now, the logons work fine and we can log onto this domain from any of our other ones, however while testing this I noticed that we seem to be getting errors on accounts which have logon scripts associated with their OU cause it can't find the file from the domain (as it will try to follow the path \\domainname.com\sysvol... etc).

Upon looking into it it seems that if you type in \\otherdomainname.com it will bring up the error
"Filename, directory name or volume syntax invalid"

You can however ping the domain name sucessfully and you can enter the full dns name of the DC to which DNS points the domain name to as it's SOA (so \\domaincontroller.domainname.com will work). But try the domain name and you'll be told where to get off so to speak :/

Any ideas as to why it doesn't like the use of the domain name (but will still ping it without problem) but is happy to use the full dns name of the dc running the domain name??

Thread moved.

well.. I think I might have lead on trying to resolve the problem.
I've checked thru all sorts of settings and configs.. I then decided to try it on the one server in that domain which isn't dual ip'ed and it worked.. even tho it will ping ok and even nslookup picks it up ok, it still won't browse to it from the other servers which are dual ip'ed.

I need to test it out with having only a single ip on one of the servers to test and see if it's ok.