Buffalo Forums

I joined my Terastation to the domain, and I am now unable to browse by IP address (\\192.168.10.1) I have to use the name instead (\\terastation) This is a problem for me for people who are trying to access it over VPN

Can anyone tell me why this is happening and how to fix it?

\\192.168.10.1 sounds like a default gateway.  Is that the IP that you gave the TS?  If so I would suggest changing it to 192.168.10.150 and see if that might clear up a network conflict of some kind.

it was just an example. actually IP is \\192.168.10.252

Okay but that doesn't completely escape the possibility of a network conflict as some DHCP tables are setup backwards.  Any possibility of a DHCP conflict with a static IP?

No, there is no network conflict.

I even tried changing the IP several times.

***UPDATE***

I bought a BRAND new terrastation TX-RXL

Firmware is 1.32

I joined it to the domain, and i added 3 shared folders. 1 of the 3 have NO access restrictions. Whats odd is that i can do \\terastation, and use it completely fine, but if i do \\192.168.10.252 the ones with access restrictions ask for my password and it never lets me log in. I tried changing my password to something extremely simple with no special symbols and that didn't work either. but if i use \\terrastation, it works fine.

can ANYONE recommend something? I also change the default domain policy NTLM settings on my 2008 server to

 Lan Manager - "send LM & NTLMv2 session security if negotiated.

In my honest opinion that is weird.  I'd have to look at some of our lab units and see if I can replicate the issue but chances are it's something to do with the network.  Only reason I say this is because I've dealt with problems like this day in and out with incidents like this turning out to be network related.  I'll continue looking into it.

IM sure it has something to do with the windows 2008 upgrade we did. The question really is what is this terrastation not compatible with? Are there any sort of logs we can look at to see?

I can't believe I didn't ask before, is the unit pingable by IP address?  If not try nslookup and enter the name of the NAS and see if it finds the IP.  Also, did you successfully join the NAS to AD?

yes its pingable.. and i was able to do an nslookup without issues..

It did successfully add to AD without any errors.

Could you relay the GMT setting on the NAS and the time zone location of your server?  I note you're on the western seaboard and was curious about this.

Date/Time Source: Automatic
Date: 08/12/2010
Time: 13:05:29
Time Zone: (UTC-08:00) Pacific Time (US & Canada)
Primary NTP IP Address: ntp.jst.mfeed.ad.jp
NTP Synchronization Frequency: Daily

The server's time is exactly the same.. nad the time zone is the same as well.

Right, but as stated in the General FAQ the NAS doesn't account for DST.  So, since your server is at UTC -8 and the NAS the same but your server accounts for DST setting it at -7 you're having a time skew issue.  NTP doesn't help the NAS sync for DST.

so what should i set the NAS to?

GMT or UTC -7 to compensate for the daylight savings time if that is the case.  If your time skew is too great then you'll have all sorts of problems with AD.

I returned this item in the end, because tech support sucks, active directory integration sucks, and there are just way too many problems with it..

I bought a Netgear NAS and it works like charm.

Buffalo - you need a new updated firmware and a better support team.

Of course it does! People like you assume everyone elses clock is out of sync but yours is correct.

Teamaamaster: You've expressed an opinion of the support team (call center) - when did you call the support team? I'd like to check the records and review their support for you.

please email me at drmemory@buffalotech.com and send me your name/phone number used to call in.

We're always reviewing our support team in case-by-case basis in order to improve.