Troubleshooting WiFi in HTC

On By // No comments:

Troubleshooting WiFi in HTC

WiFi was detected but unable to browse the internet.

I was connected  to the CNet ADSL Wireless Router and able to browse the internet using the wifi in HTC Touch P3452.

However in the new network with InfoSmart Router this device even didn't detected the wireless access point. But the HTC Touch Diamond was able to detect this access point and was also able to connect to this access point. But it was also failing to browse the internet through it. Always said the page could not be found. I then installed the task manager from fdcsoft from http://www.gsmhacks.com/forums/pocket-pc-windows-smartphone-applications/47860-fdcsoft-task-manager-ppc-app.html Through its ping test I was not even able to ping the wireless router. So after little searching I found out the solution of it. Just change a small setting
Go Start -> Settings -> Connections -> Wireless LAN -> Power Mode -> and slide all the way to Best Performance.
That just solved the problem in both the HTC Touch P3452 and the Diamond.
Read More

Deploying Active Directory with DNS (linux) in Mixed Environment

On By // No comments:

Deploying Active Directory with DNS (Linux) in Mixed Environment

Integrating Active Directory with the Linux as primary DNS Server Lately I was working on integrating the newly configuring Windows 2003 Active Directory with the old running DNS server which was running on Linux. After a day or two searching on the internet I finally found a way to integrate the windows and Linux together.

Generally we install DNS server into an Active Directory. The separation might have been far easier if the DNS server had been the Windows Server itself, but some tweaks were required when the server was Linux.

The Linux DNS server was far old running and the new Active Directory was to integrate to it. So the active directory was installed in the windows 2003 server with the domain name adtest.dipes.com.np and the full name of this computer being dc.adtest.dipes.com.np

The preferred dns of the server itself was like that of others and the clients, e.g. 192.168.40.2 (the ip of Linux DNS server)
The windows server (domain controller) ip was 192.168.40.13

Then inspecting the netlogon.dns file, the following lines of codes of database were written in the dns database file of Linux (dipes.com.np zone file)


dc.adtest IN A 192.168.40.13

_ldap._tcp.adtest.dipes.com.np. SRV 0 0 389 dc.adtest.dipes.com.np.
_kerberos._tcp.adtest.dipes.com.np. SRV 0 0 88 dc.adtest.dipes.com.np.
_ldap._tcp.dc._msdcs.adtest.dipes.com.np. SRV 0 0 389 dc.adtest.dipes.com.np.
_kerberos._tcp.dc._msdcs.adtest.dipes.com.np. SRV 0 0 88 dc.adtest.dipes.com.np.

And this was what looked in the netlogon.dns file in windows server
adtest.dipes.com.np. 600 IN A 192.168.40.13
_ldap._tcp.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.Default-First-Site-Name._sites.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.pdc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.gc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 3268 dc.adtest.dipes.com.np.
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 3268 dc.adtest.dipes.com.np.
_ldap._tcp.359ce6bb-ad7c-46c9-8cb3-ee36d2c72f5c.domains._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
gc._msdcs.adtest.dipes.com.np. 600 IN A 192.168.40.13
fc3d8251-738c-402d-9ba1-33f2402923eb._msdcs.adtest.dipes.com.np. 600 IN CNAME dc.adtest.dipes.com.np.
_kerberos._tcp.dc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 88 dc.adtest.dipes.com.np.
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 88 dc.adtest.dipes.com.np.
_ldap._tcp.dc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_kerberos._tcp.adtest.dipes.com.np. 600 IN SRV 0 100 88 dc.adtest.dipes.com.np.
_kerberos._tcp.Default-First-Site-Name._sites.adtest.dipes.com.np. 600 IN SRV 0 100 88 dc.adtest.dipes.com.np.
_gc._tcp.adtest.dipes.com.np. 600 IN SRV 0 100 3268 dc.adtest.dipes.com.np.
_gc._tcp.Default-First-Site-Name._sites.adtest.dipes.com.np. 600 IN SRV 0 100 3268 dc.adtest.dipes.com.np.
_kerberos._udp.adtest.dipes.com.np. 600 IN SRV 0 100 88 dc.adtest.dipes.com.np.
_kpasswd._tcp.adtest.dipes.com.np. 600 IN SRV 0 100 464 dc.adtest.dipes.com.np.
_kpasswd._udp.adtest.dipes.com.np. 600 IN SRV 0 100 464 dc.adtest.dipes.com.np.
ForestDnsZones.adtest.dipes.com.np. 600 IN A 192.168.40.13
_ldap._tcp.ForestDnsZones.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
DomainDnsZones.adtest.dipes.com.np. 600 IN A 192.168.40.13
_ldap._tcp.DomainDnsZones.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
_ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.adtest.dipes.com.np. 600 IN SRV 0 100 389 dc.adtest.dipes.com.np.
The next step was the finally joining the client with the domain controller with its previous old settings of preferred dns being same (i.e. 192.168.40.2)
Read More