TechTalkz.com Logo

Go Back   TechTalkz.com Technology & Computer Troubleshooting Forums > Tech Support Archives > Linux & Opensource > Ubuntu Linux

Reply
 
Thread Tools Display Modes
Old 01-12-2007, 03:29 PM   #21
Moog
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

Fokke Nauta illuminated alt.os.linux.ubuntu by typing:

> <...>
> Hi Moog
>
> Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
> They don't have the options you mentioned.
>
> Fokke


OK. Worth a try I suppose.

If you fancy posting the contents of your samba.conf file here, I will
ceertainly have a look. There could well be a rogue setting knocking
around in there.

--
Moog

"Some mornings it just doesn't seem worth it to gnaw through the
leather straps."
  Reply With Quote
Old 01-12-2007, 03:30 PM   #22
Fokke Nauta
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

"Moog" <efcmoog@gmail.com> schreef in bericht
news:5r845bF13hn3rU1@mid.individual.net...
> Fokke Nauta illuminated alt.os.linux.ubuntu by typing:
>
>> <...>
>> I thought I had configured Samba correctly and looking into the smb.conf
>> file I did not see anything wrong. Of course I have defined the workgroup
>> name.
>> Samba works OK as I am able to connect to a shared directory from a
>> Windows
>> PC. I have to hut Run and then the IP address of the Ubuntu PC. That
>> works
>> fine. But I would have liked the Ubunto PC to turn up as a PC in the
>> network
>> just like the other PC's, as seen from a Windows PC. And that doesn't
>> seem
>> to happen.

>
> Hi Fokke,
>
> You may have the same issue I had. If you are talking about a Vista box.
>
> You need to go to "networking and sharing centre"
> select "view status" of the network your windows boxes connect with
> Select properties....
> Click the UAC "continue" popup.
> Make sure there is in a tick in the box titled
> "Link Layer Topology Discovery Mapper I/O"
> Click OK. OK.
>
> This is the MS piece of technology that shows network icons. If it
> isn't selected you won't see any. I had exactly this issue and it
> stumped me for months.
>
> Long shot, but as you've stated Samba is configured correctly it's
> worth a look.
>
> --
> Moog
>
> "Some mornings it just doesn't seem worth it to gnaw through the
> leather straps."
>


Hi Moog

Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
They don't have the options you mentioned.

Fokke


  Reply With Quote
Old 01-12-2007, 03:30 PM   #23
Moog
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

Fokke Nauta illuminated alt.os.linux.ubuntu by typing:

> <...>
> Hi Moog
>
> Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
> They don't have the options you mentioned.
>
> Fokke


OK. Worth a try I suppose.

If you fancy posting the contents of your samba.conf file here, I will
ceertainly have a look. There could well be a rogue setting knocking
around in there.

--
Moog

"Some mornings it just doesn't seem worth it to gnaw through the
leather straps."
  Reply With Quote
Old 01-12-2007, 03:32 PM   #24
Fokke Nauta
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

"Moog" <efcmoog@gmail.com> schreef in bericht
news:5r845bF13hn3rU1@mid.individual.net...
> Fokke Nauta illuminated alt.os.linux.ubuntu by typing:
>
>> <...>
>> I thought I had configured Samba correctly and looking into the smb.conf
>> file I did not see anything wrong. Of course I have defined the workgroup
>> name.
>> Samba works OK as I am able to connect to a shared directory from a
>> Windows
>> PC. I have to hut Run and then the IP address of the Ubuntu PC. That
>> works
>> fine. But I would have liked the Ubunto PC to turn up as a PC in the
>> network
>> just like the other PC's, as seen from a Windows PC. And that doesn't
>> seem
>> to happen.

>
> Hi Fokke,
>
> You may have the same issue I had. If you are talking about a Vista box.
>
> You need to go to "networking and sharing centre"
> select "view status" of the network your windows boxes connect with
> Select properties....
> Click the UAC "continue" popup.
> Make sure there is in a tick in the box titled
> "Link Layer Topology Discovery Mapper I/O"
> Click OK. OK.
>
> This is the MS piece of technology that shows network icons. If it
> isn't selected you won't see any. I had exactly this issue and it
> stumped me for months.
>
> Long shot, but as you've stated Samba is configured correctly it's
> worth a look.
>
> --
> Moog
>
> "Some mornings it just doesn't seem worth it to gnaw through the
> leather straps."
>


Hi Moog

Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
They don't have the options you mentioned.

Fokke


  Reply With Quote
Old 01-12-2007, 03:33 PM   #25
Moog
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

Fokke Nauta illuminated alt.os.linux.ubuntu by typing:

> <...>
> Hi Moog
>
> Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
> They don't have the options you mentioned.
>
> Fokke


OK. Worth a try I suppose.

If you fancy posting the contents of your samba.conf file here, I will
ceertainly have a look. There could well be a rogue setting knocking
around in there.

--
Moog

"Some mornings it just doesn't seem worth it to gnaw through the
leather straps."
  Reply With Quote
Old 01-12-2007, 08:46 PM   #26
Fokke Nauta
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

Moog wrote:
> Fokke Nauta illuminated alt.os.linux.ubuntu by typing:
>
>> <...>
>> Hi Moog
>>
>> Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
>> They don't have the options you mentioned.
>>
>> Fokke

>
> OK. Worth a try I suppose.
>
> If you fancy posting the contents of your samba.conf file here, I will
> ceertainly have a look. There could well be a rogue setting knocking
> around in there.
>


Hi,

Underneath is the file.
Perhaps you can find something!

Rgs,
Fokke

-------------------------------------------------

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = LAN

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
; wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
; security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

; guest account = nobody
invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
; unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan
<<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n
*passwd:*password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
; pam password change = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password
--gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
; printer admin = @lpadmin


############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and
/usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
;
; The following was the default behaviour in sarge
; but samba upstream reverted the default because it might induce
; performance issues in large organizations
; See #368251 for some of the consequences of *not* having
; this setting and smb.conf(5) for all details
;
; winbind enum groups = yes
; winbind enum users = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
; writable = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you
want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# Un-comment the following and create the netlogon directory for Domain
Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
public = no
writable = no
create mode = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; writable = no
; locking = no
; path = /cdrom
; public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

  Reply With Quote
Old 02-12-2007, 09:52 AM   #27
Gordon
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

On 2007-11-28, William Colls <william@procomsys.com> wrote:
> Fokke Nauta wrote:
>> Hi all,
>>
>> I recently installed Ubuntu 7.10 on a PC. This PC is connected in a Windows
>> network. All Windows PC's can see eachother when browsing the network but
>> they can't see the Ubuntu box. I shared a directory on this Ubuntu PC. From
>> a Windows machine I can access this map by "Run as 10.0.0.157" (the IP
>> adress from the Ubuntu machine). But I still can't see the machine when
>> browsing the Windows network.
>> The Windows PC's use Netbeui for internal communication and TCP/IP for the
>> outside world. The Ubuntu box works fine and can even print over a Windows
>> printserver.
>> How can I make this Ubuntu PC appear in the network for the Windows PC's,
>> just like the other Windows PC's?
>>
>> Thanks in advance for your help.
>>
>> With best regards,
>> Fokke Nauta
>>
>>

>
> Have you installed, and configured, samba?
>

Both the client and server parts?

  Reply With Quote
Old 02-12-2007, 04:37 PM   #28
NoStop
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

Gordon wrote:

> On 2007-11-28, William Colls <william@procomsys.com> wrote:
>> Fokke Nauta wrote:
>>> Hi all,
>>>
>>> I recently installed Ubuntu 7.10 on a PC. This PC is connected in a
>>> Windows network. All Windows PC's can see eachother when browsing the
>>> network but they can't see the Ubuntu box. I shared a directory on this
>>> Ubuntu PC. From a Windows machine I can access this map by "Run as
>>> 10.0.0.157" (the IP adress from the Ubuntu machine). But I still can't
>>> see the machine when browsing the Windows network.
>>> The Windows PC's use Netbeui for internal communication and TCP/IP for
>>> the outside world. The Ubuntu box works fine and can even print over a
>>> Windows printserver.
>>> How can I make this Ubuntu PC appear in the network for the Windows
>>> PC's, just like the other Windows PC's?
>>>
>>> Thanks in advance for your help.
>>>
>>> With best regards,
>>> Fokke Nauta
>>>
>>>

>>
>> Have you installed, and configured, samba?
>>

> Both the client and server parts?


The client part is installed, hence you can print to a Windoze printer
share. What you need to install is the server part, ie. samba on the Linux
box.

sudo apt-get install samba

Cheers.

--
Ubuntu 7.10 ... wow!
http;//www.ubuntu.com
  Reply With Quote
Old 02-12-2007, 05:43 PM   #29
jane doa
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

On 2007-12-01, Fokke Nauta <fnautaNO@SPAMiae.nl> wrote:
> Moog wrote:
>> Fokke Nauta illuminated alt.os.linux.ubuntu by typing:
>>
>>> <...>
>>> Hi Moog
>>>
>>> Thanks. But it wasn't a Vista box, it was XP Home and XP Pro.
>>> They don't have the options you mentioned.
>>>
>>> Fokke

>>
>> OK. Worth a try I suppose.
>>
>> If you fancy posting the contents of your samba.conf file here, I will
>> ceertainly have a look. There could well be a rogue setting knocking
>> around in there.
>>

>
> Hi,
>
> Underneath is the file.
> Perhaps you can find something!
>
> Rgs,
> Fokke


you don't appear to be sharing any part of your Ubuntu file system so I would
think that there is nothing to display to the windows machines (just printers)

I think a stanza in the smb.conf == Share Definitions == section
along the lines of;
[Ubuntu_Share]
path = /some/file/path
comment = Ubuntu shared files
available = yes
browseable = yes
public = yes
writeable = yes

should show up on a windows machine with a path (that you can map to a drive)
something like;
\\ubuntumachinename\Ubuntu_Share or maybe \\ubuntu IP address\Ubuntu_Share

I don't really know what was happening when you typed run: ubuntu ip address ...
maybe it was putting you into a home folder of the user you logged in as?
Not sure.

I think you should also uncomment the line in the == Global Settings == section;
name resolve order = lmhosts host wins bcast

cheers

>
> -------------------------------------------------
>


< sniped your smb.conf down to the share section >

> #======================= Share Definitions =======================
>
> # Un-comment the following (and tweak the other settings below to suit)
> # to enable the default home directory shares. This will share each
> # user's home directory as \\server\username
> ;[homes]
> ; comment = Home Directories
> ; browseable = no
>
> # By default, \\server\username shares can be connected to by anyone
> # with access to the samba server. Un-comment the following parameter
> # to make sure that only "username" can connect to \\server\username
> # This might need tweaking when using external authentication schemes
> ; valid users = %S
>
> # By default, the home directories are exported read-only. Change next
> # parameter to 'yes' if you want to be able to write to them.
> ; writable = no
>
> # File creation mask is set to 0700 for security reasons. If you want to
> # create files with group=rw permissions, set next parameter to 0775.
> ; create mask = 0700
>
> # Directory creation mask is set to 0700 for security reasons. If you
> want to
> # create dirs. with group=rw permissions, set next parameter to 0775.
> ; directory mask = 0700
>
> # Un-comment the following and create the netlogon directory for Domain
> Logons
> # (you need to configure Samba to act as a domain controller too.)
> ;[netlogon]
> ; comment = Network Logon Service
> ; path = /home/samba/netlogon
> ; guest ok = yes
> ; writable = no
> ; share modes = no
>
> # Un-comment the following and create the profiles directory to store
> # users profiles (see the "logon path" option above)
> # (you need to configure Samba to act as a domain controller too.)
> # The path below should be writable by all users so that their
> # profile directory may be created the first time they log on
> ;[profiles]
> ; comment = Users profiles
> ; path = /home/samba/profiles
> ; guest ok = no
> ; browseable = no
> ; create mask = 0600
> ; directory mask = 0700
>
> [printers]
> comment = All Printers
> browseable = no
> path = /var/spool/samba
> printable = yes
> public = no
> writable = no
> create mode = 0700
>
> # Windows clients look for this share name as a source of downloadable
> # printer drivers
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/printers
> browseable = yes
> read only = yes
> guest ok = no
> # Uncomment to allow remote administration of Windows print drivers.
> # Replace 'ntadmin' with the name of the group your admin users are
> # members of.
> ; write list = root, @ntadmin
>
> # A sample share for sharing your CD-ROM with others.
> ;[cdrom]
> ; comment = Samba server's CD-ROM
> ; writable = no
> ; locking = no
> ; path = /cdrom
> ; public = yes
>
> # The next two parameters show how to auto-mount a CD-ROM when the
> # cdrom share is accesed. For this to work /etc/fstab must contain
> # an entry like this:
> #
> # /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
> #
> # The CD-ROM gets unmounted automatically after the connection to the
> #
> # If you don't want to use auto-mounting/unmounting make sure the CD
> # is mounted on /cdrom
> #
> ; preexec = /bin/mount /cdrom
> ; postexec = /bin/umount /cdrom
>


  Reply With Quote
Old 02-12-2007, 10:58 PM   #30
Fokke Nauta
Guest
 
Posts: n/a
Re: Can't see Linux PC in Windows network

NoStop wrote:
> Gordon wrote:
>
>> On 2007-11-28, William Colls <william@procomsys.com> wrote:
>>> Fokke Nauta wrote:
>>>> Hi all,
>>>>
>>>> I recently installed Ubuntu 7.10 on a PC. This PC is connected in a
>>>> Windows network. All Windows PC's can see eachother when browsing the
>>>> network but they can't see the Ubuntu box. I shared a directory on this
>>>> Ubuntu PC. From a Windows machine I can access this map by "Run as
>>>> 10.0.0.157" (the IP adress from the Ubuntu machine). But I still can't
>>>> see the machine when browsing the Windows network.
>>>> The Windows PC's use Netbeui for internal communication and TCP/IP for
>>>> the outside world. The Ubuntu box works fine and can even print over a
>>>> Windows printserver.
>>>> How can I make this Ubuntu PC appear in the network for the Windows
>>>> PC's, just like the other Windows PC's?
>>>>
>>>> Thanks in advance for your help.
>>>>
>>>> With best regards,
>>>> Fokke Nauta
>>>>
>>>>
>>> Have you installed, and configured, samba?
>>>

>> Both the client and server parts?

>
> The client part is installed, hence you can print to a Windoze printer
> share. What you need to install is the server part, ie. samba on the Linux
> box.
>
> sudo apt-get install samba
>
> Cheers.
>


Hi,

I can use a Windows printer server indeed, and I am able to connect from
a Windows PC to a shared directory on the Ubuntu system, so I thought
that Samba was installed. But I never realized that there was a client
and a server part separately. Anyway, the client is installed. I tried
your "sudo apt-get install samba" but this gives the following result:
"Reading package lists... Done
Building dependency tree
Reading state information... Done
samba is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded."
So - now I got lost.
What's next?

Cheers,
Fokke

  Reply With Quote
Reply

Thread Tools
Display Modes


Google
 


All times are GMT +5.5. The time now is 02:46 AM.


vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO
Copyright © 2005-2008, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional