|
I am a windows xp user, i wanted to know if it is possible to disable / enable the windows xp firewall by editing some settings in the registry. I think it is impossible but if somebody knows please reply.
Also if the above is possible, then is it also possible to say i want to enable incomming connections to access port 80 using registry setting.
i am very curious if it is possible.
|
|
|
|
|
Is there a command that I can use to make my ISP's DNS server spit out the hostname of a computer on his network when all I know about it is the IP address?
The usual data from ARIN, ICANN, etc is useless, as all it will tell me is that the address block is assigned to the ISP. Tracert would do it most of the time, but by the time I see the logs the clown that is scanning me has logged off, and tracert returns nothing but a timeout. I know that Win2K Server ships with a lot of tools, but I'm not familiar with one that will do this for me. Suggestions?
Barring this, can I set up my DNS server to steal a copy of the ISP's cache? That should contain the info I need, though it will be tedious to sort through it manually.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
It depends on what kind of problem you have. If it is
just somebody scanning your computers ports I would
not worry as long as the firewall does it's work
and blocks him out. I think Sygate is configured
to block for 10 min.
jhaga
|
|
|
|
|
|
Nslookup is great for getting an address from a nameserver, but it's useless for getting a name from an address. Ping -a [IPaddr] will return a host name only if the host is active, and it is enabled to respond to ping. I want to identify the bugger whether he's on or not!
There is a new chapter to this event. My ISP reports that a hacker was in the area trying to find all the unused IP addresses in this subnet. The owner of the address that was scanning me is known to the ISP, and has not been using scanning software, so the hacker may have gotten hold of this IP while the legitimate user was offline. The problem hasn't come up again since.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
nslookup will get a name from an IP address if the DNS server has an entry. Unfortunately most Adress to hostname translations are useless for ip addresses assigned to customers.
As far as getting the information contained in the ISP's DNS server, it all depends on how their DNS server is configured. If the ISP allows DNS zone transfers to "unauthorized" servers then you could run a DNS server of your own and configure it as a backup DNS server for thier domain. This would download the primary database into your server where you could then examine it.
Not much point in doing this though. If nslookup does not provide the info your pretty much out of luck. That means they don't have an entry for it. Most DNS servers these days also are configured to allow zone transfers only for sites that are on an "authorized" list.
|
|
|
|
|
Bummer... The evil doer was back last night, this time hijacking my IP address. Since that wiped out my connection, I can at least take some consolation in knowing that he probably couldn't use it either. I got the mac address, though, and the ISP can block users from that info.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
Probably could have titled this post Hey Roger! again, but then again some of you other gurus may not have answered.
I reinstalled an ancient HP Pavillion a few months ago for the unemployed parents of a kid that goes to my sons school. During the installation of Windows 98 SE everything went along fine if not a bit slow. I installed all known updates for things like Internet Explorer, Windows Installer, DirectX etc. With no problems, I then performed all Windows Updates (yes Roger, all of them) and once again found no problems.
A few weeks later (a couple of months ago now) I took over a not so old scanner and printer I found in the garage. When I tried to install the drivers for either device Windows would give me a Blue Screen Of Death claiming it couldn't read the CD.
I knew the CD was OK as I tested it at home. I then tried to copy the contents of the CD to HDD using Windows Explorer, same problem. So I booted off a Windows 98 SE boot disk and used xcopy from the command line and all was good.
So now I have a problem with Windows where it is refusing to read all CD's except some very old stuff they have. Audio, Norton, SystemWorks, CD-R's all fail.
Any idea what I could try to get this to work?
Michael Martin
Australia
mjm68@tpg.com.au
"I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end."
- Chris Maunder 15/07/2002
|
|
|
|
|
This sounds like a bad CD-ROM drive (and I've had experience with those!). Buy a new one. They only cost $25 these days.
I installed Windows 98 with a certain CD-ROM drive, and it did fine. But when I got into Windows for the first time, it wouldn't even finish booting up, ever. So I tested the CD-ROM drive on a different computer that had no history of boot problems, and it stopped booting up whenever the CD-ROM was attached. Then I switched to another old CD-ROM. It let windows boot up, but it had the annoying habit you mentioned - the blue screen telling you it can't read from the CD-ROM. It also would sometimes go "nuts" and not stop reading from the drive when it was told to, continuing until the computer was turned off.
Only one other thing - there can be problems if the CD-ROM drive is in DOS compatibility mode.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
jdunlap wrote:
This sounds like a bad CD-ROM drive (and I've had experience with those!). Buy a new one. They only cost $25 these days.
Could be. I bought 2 new 52x speed CD-ROM at the same time, put them in 2 identical old HP computers and both have the same symptoms. I'm just surprised that they both worked to install Windows and only had problems after all updates and other software was installed. Also why they both still work in DOS.
jdunlap wrote:
I installed Windows 98 with a certain CD-ROM drive ..... continuing until the computer was turned off.
I never thought to try it in another machine, or another CD-ROM in that machine. I'm amazed I can breathe involuntary some days.
jdunlap wrote:
Only one other thing - there can be problems if the CD-ROM drive is in DOS compatibility mode.
Are you talking about the settings in the Advanced section of System from the Control Panel?
Michael Martin
Australia
mjm68@tpg.com.au
"I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end."
- Chris Maunder 15/07/2002
|
|
|
|
|
Michael Martin wrote:
Are you talking about the settings in the Advanced section of System from the Control Panel?
Yes.
Michael Martin wrote:
I bought 2 new 52x speed CD-ROM at the same time, put them in 2 identical old HP computers and both have the same symptoms. I'm just surprised that they both worked to install Windows and only had problems after all updates and other software was installed. Also why they both still work in DOS.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Modern CDs use ISO Mode 1 format for the track layout on the CD, but there are older CD drives still out there that can only read Mode 2 (XA-Format) CDs. Perhaps the newer installation CDs are in a format that the old CD drive can't understand. Try copying the drivers to your hard drive, then burning a CD in the Mode 2 format from them.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
They'd have to be pretty old, but I guess he did say "ancient"...
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
I don't know what 'ancient' means to Michael, but I know that there's some really old hardware out there still working. I spent last weekend repairing a network for a local business, and two of their machines are Pentium 100s! Somehow they managed to get Win98SE to run on them, using NetBEUI as a transport protocol. Then they built a 'server' from scratch (a pet project of a manager who knows just enough to be a problem for everyone) with Windows 2000 Pro on it, but no one could figure out how to use Win2KP. So they reformatted and installed WinMe on it!!! I reconfigured everything to use TCP/IP, cleaned up the tiny disk drives, and enabled ICS on their one machine with a modem that still works (a winmodem, no less), rebuilt one machine competely because the thing became psychotic at odd moments, and reconfigured their proprietary sales programs to work properly. I don't know what I'll do next time they call - it's like trying to refloat the Titanic each time I visit!
My suggestion to Michael is a long shot, but worth a try. I'm sure he's already checked the cables and jumpers - there's not much else that can be wrong physically other than a bad controller on the MB, and there's nothing he can do about that short of replacing it. A machine that old is hardly worth the cost.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
Roger Wright wrote:
I don't know what 'ancient' means to Michael, but I know that there's some really old hardware out there still working.
These are running Pentium 166 (can't remeber if MMX or not) and I think they were made in 1996. Forgot to mention that in the last reply.
Michael Martin
Australia
mjm68@tpg.com.au
"I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end."
- Chris Maunder 15/07/2002
|
|
|
|
|
Roger Wright wrote:
Modern CDs use ISO Mode 1 format for the track layout on the CD, but there are older CD drives still out there that can only read Mode 2 (XA-Format) CDs. Perhaps the newer installation CDs are in a format that the old CD drive can't understand. Try copying the drivers to your hard drive, then burning a CD in the Mode 2 format from them.
The CD-ROM drive in question was a brand new 52x speed Samsung (I believe) that I bought for them in January. I find it hard to believe that the drive worked well enough to install Windows, all updates I had on CD. Then worked throught the Windows Update and also throught the installation of applications. It was only after I delivered it to them the problem started. No they didn't cause it and all cables etc. look right. It also still works when I boot to DOS mode.
I think it has to be something with Windows itself or a driver but I don't know which if any.
Michael Martin
Australia
mjm68@tpg.com.au
"I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end."
- Chris Maunder 15/07/2002
|
|
|
|
|
Michael Martin wrote:
It also still works when I boot to DOS mode.
I had one just like this. Any decent CD-ROM will do the basic thing with the basic drivers.
However, as I said, you can sometimes have problems if a drive is in DOS compatibility mode.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
A trick you might want to try is to delete the drive in Device Manager, shut down the PC, disconnect the drive cable, then restart the box. After it settles down, shut it down again, reconnect the drive, and power up. Win98 will 'discover' the drive and should reinstall the drivers for it. I say 'should' because, in theory, when it reboots without the drive it should remove the driver vxd from the configuration, then install a fresh copy when it discovers the new drive. In practice, it seems that it often reports that you already have the driver installed and skips the reinstallation step - not very useful if the driver is corrupted. Still, it's worth a try.
"Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
|
|
|
|
|
Good point Roger, will give it a try when I next visit the machine.
Michael Martin
Australia
mjm68@tpg.com.au
"I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end."
- Chris Maunder 15/07/2002
|
|
|
|
|
Hi
I have a Win2000 Server which is a domain controller.
I have installed a win2003 Server (olddomain.kg) on another computer and installed Active Directory on it (newdomain.kg) .
I have users on old domain,
How can I get the user profiles from old domain to the new one?
thanx.
|
|
|
|
|
Hi all!
I`ve been searching for VC++ 6.0 code/application that preventing our Windows from suspending but I haven`t found it yet. What I have found is a code in VB language that works perfectly.
Any helps, please?
Thank you so very much!
|
|
|
|
|
[quote]
What I have found is a code in VB language that works perfectly.
[/quote]
If you were to point us at the VB code we could probably translate it. Probably it works by replying to the WM_POWER message where wParam is APM_QUERYSUSPEND or something?
'--8<------------------------
Ex Datis:
Duncan Jones
Merrion Computing Ltd
|
|
|
|
|
Hi! It`s a very good luck, coz I got the code from your site (www.merrioncomputing.com)! Nice code guys!
Here`s the code:
'IN A MODULE<br />
Option Explicit<br />
<br />
Public oldProcAddress As Long<br />
<br />
Public Enum enPowerBroadcastType<br />
PBT_APMQUERYSUSPEND = &H0<br />
PBT_APMQUERYSTANDBY = &H1<br />
PBT_APMQUERYSUSPENDFAILED = &H2<br />
PBT_APMQUERYSTANDBYFAILED = &H3<br />
PBT_APMSUSPEND = &H4<br />
PBT_APMSTANDBY = &H5<br />
PBT_APMRESUMECRITICAL = &H6<br />
PBT_APMRESUMESUSPEND = &H7<br />
PBT_APMRESUMESTANDBY = &H8<br />
End Enum<br />
<br />
Public Const BROADCAST_QUERY_DENY = &H424D5144<br />
Public Const WM_POWER = &H48<br />
Public Const WM_POWERBROADCAST = &H218<br />
Public Const PWR_SUSPENDREQUEST = 1<br />
Public Const GWL_WNDPROC = (-4)<br />
Public Const PWR_FAIL = (-1)<br />
<br />
Public Declare Function SetWindowLong Lib "user32" Alias "SetWindowLongA" (ByVal hWnd As Long, ByVal nIndex As Long, ByVal dwNewLong As Long) As Long<br />
Public Declare Function CallWindowProc Lib "user32" Alias "CallWindowProcA" (ByVal lpPrevWndFunc As Long, ByVal hWnd As Long, ByVal Msg As Long, ByVal wParam As Long, ByVal lParam As Long) As Long<br />
<br />
'\\ In a .BAS file:<br />
'\\ --[VB_WindowProc]--------------------------------------------<br />
'\\ 'typedef LRESULT (CALLBACK* WNDPROC)(HWND, UINT, WPARAM,<br />
'\\ LPARAM);<br />
'\\ Parameters:<br />
'\\ hwnd - window handle receiving message<br />
'\\ wMsg - The window message (WM_..etc.)<br />
'\\ wParam - First message parameter<br />
'\\ lParam - Second message parameter<br />
'\\ Note:<br />
'\\ When subclassing a window proc using this, set the<br />
'\\ eventhandlerhOldWndProc property to the window's previous<br />
'\\ window proc address.<br />
'\\ -------------------------------------------------------------'\\ You have a royalty free right to use, reproduce, modify,<br />
'\\ publish and mess with this code<br />
'\\ I'd like you to visit http://www.merrioncomputing.com for<br />
'\\ updates, but won't force you<br />
'\\ ----------------------------------------------------------<br />
<br />
Public Function VB_WindowProc(ByVal hWnd As Long, ByVal wMsg As _<br />
Long, ByVal wParam As Long, ByVal lParam As Long) As Long<br />
<br />
On Local Error Resume Next<br />
Dim lRet As Long<br />
<br />
<br />
'\\ If its a power suspending broadcast, kill it...<br />
If wMsg = WM_POWER And wParam = PWR_SUSPENDREQUEST Then<br />
'\\ This is the message in Windows NT/2000<br />
VB_WindowProc = PWR_FAIL<br />
ElseIf wMsg = WM_POWERBROADCAST And wParam = _<br />
PBT_APMQUERYSUSPEND Then<br />
VB_WindowProc = BROADCAST_QUERY_DENY<br />
Else<br />
VB_WindowProc = CallWindowProc(oldProcAddress, hWnd, wMsg, _<br />
wParam, lParam)<br />
End If<br />
<br />
End Function<br />
<br />
'\\ IN OUR APP's MAIN FORM:<br />
Private Sub Form_Load()<br />
<br />
oldProcAddress = SetWindowLong(Me.hWnd, GWL_WNDPROC, _<br />
AddressOf VB_WindowProc)<br />
<br />
End Sub<br />
<br />
Private Sub Form_Unload(Cancel As Integer)<br />
<br />
Call SetWindowLong(Me.hWnd, GWL_WNDPROC, oldProcAddress)<br />
<br />
End Sub
That works fine but since I`m a new VB-to-VC++ learner I can hardly do that stuff in VC++ language.
Again thank you so very much for your respond!
Regards.
|
|
|
|
|
It's SO much easier to do this in VC than in VB. If you use MFC, simply hook up a virtual function override for WindowProc (with ClassWizard), and put this code in it:
if( message == WM_POWERBROADCAST )
{
switch( wParam )
{
case PBT_APMQUERYSUSPEND:
{
return BROADCAST_QUERY_DENY;
}
}
}
There ya go, done! If you don't use MFC, simply put a case for WM_POWERBROADCAST in your already existing WindowProc.
Chris Richardson Terrain Software
|
|
|
|
|
Yeap! It`s so MUCH easier. Just a less-than-a-minute work. Great thanks, Chris Richardson! Both MFC and non-MFC work fine.
Thanks to Duncan, too. Hoping this thread useful for the community.
Regards.
|
|
|
|
|