The_Unbeliever
Honorary Master
Just a quick note - we've had issues with accessing this specific win2k3 server on an iburst line.
What would happen is that the IP address would change somehow, and the dynamic DNS URL wasn't updated, so we could not access the machine remotely.
Which is interesting, as we've got another PC operating next to it, identical in setup, except that it's running Windows XP Professional, and we haven't had any issues with the XP machine.
And asking the technician to reset the PC is a tedious affair, and would not always resolve the issue.
So, to resolve the issue (using automated methods) I created a simple batch file, called iburps.cmd with the following contents :
and bunged it up in the Task Scheduler, and set it to run twice, once at midnight, and at noon (12:00).
All it does is it disconnects the iBurst connection, and the Dynamic DNS updater application reconnects after 5 or 10 seconds.
This morning I was unable to access the PC again, but when the task was executed, I was able to access the PC again.
I have no idea why this anomaly occur on win2k3 server, we even changed the MTU's size to the iburps recommended size, but even that didn't help.
So we'll see if my script will do the trick for now.
Eish...
What would happen is that the IP address would change somehow, and the dynamic DNS URL wasn't updated, so we could not access the machine remotely.
Which is interesting, as we've got another PC operating next to it, identical in setup, except that it's running Windows XP Professional, and we haven't had any issues with the XP machine.
And asking the technician to reset the PC is a tedious affair, and would not always resolve the issue.
So, to resolve the issue (using automated methods) I created a simple batch file, called iburps.cmd with the following contents :
Code:
rasdial iBurst /disconnectand bunged it up in the Task Scheduler, and set it to run twice, once at midnight, and at noon (12:00).
All it does is it disconnects the iBurst connection, and the Dynamic DNS updater application reconnects after 5 or 10 seconds.
This morning I was unable to access the PC again, but when the task was executed, I was able to access the PC again.
I have no idea why this anomaly occur on win2k3 server, we even changed the MTU's size to the iburps recommended size, but even that didn't help.
So we'll see if my script will do the trick for now.
Eish...