alleyesable

C:\Windows\system32>nslookup tower Server: cellspot.router Address: 192.168.29.1 *** cellspot.router can't find tower: Non-existent domain C:\Windows\system32>ping tower Pinging tower [192.168.1.2] with 32 bytes of data: Reply from 192.168.1.2: bytes=32 time=10ms TTL=63 Reply from 192.168.1.2: bytes=32 time<1ms TTL=63 Reply from 192.168.1.2: bytes=32 time=1ms TTL=63 Reply from 192.168.1.2: bytes=32 time=1ms TTL=63 Ping statistics for 192.168.1.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 10ms, Average = 3ms C:\Windows\system32> Strange to get the two different results. I updated the windows hosts file so to at least be able to effectively ping tower.

I have a properly running version of 5.05. I recently changed my wireless router with which I access the server. The server I might add is hardwired to the router. I just access the server with a WiFi connected laptop. I cannot access it now using http://tower/. Instead I have to access it using its ip address. The same condition exists if I try to log on to it using Putty. Using a Linux box (Linux Mint on another partition on the same laptop), there is no problem. I guess something happened that Windows cannot access it. Any ideas how to fix the access via Windows?

Anybody?

I'm performing a first time setup with two SATA drives. I'm in the process of the Configuration Tutorial.I've performed pre-clear and at the step: "Verifying SATA Hard Drives are Detected". The command "dmesg|grep SATA|grep link" returns blank. Backing up a bit I ran "dmesg|grep SATA" and it returned: root@Tower:~# dmesg|grep SATA ata1: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 19 ata2: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 19 It doesn't look as if the drives are up although they were both fully recognizable by preclear_drive.sh Appreciate any help here. Thanks in advance