ipconfig /flushdns ???

J

johns

I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems. I went to Microsoft, and all I found
there was jargon ... no help.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns
 
O

Og

johns said:
I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems. I went to Microsoft, and all I found
there was jargon ... no help.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns
#1. If you are going to "support 10 or more CATIA workstations",
you will do well to re-think your aversion to the "jargon" of your
job.
#2. If you have a problem with a CATIA licensing server,
why do you not visit CATIA technical support?
#3. For future reference -- Server Operating issues are best addressed in
newsgroups dedicated to a Server OS, rather than in a Workstation
newsgroup.
Note: It sounds like obtaining CATIA license lease is tied to obtaining a
DNS leas.
If that is the case, when the length of the CATIA license lease is
shorter
than the length of the DNS lease, the license lease will expire and
remain so
until a new DNS lease is obtained.
Steve
 
G

Guest

I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems. I went to Microsoft, and all I found
there was jargon ... no help.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns

consider using static ips or changing the lease time on the dhcp
server.. it sounds like the workstations are caching a name to an ip
address which is expiring before the cache is renewed.

Flamer.
 
B

Bruce Chambers

johns said:
I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems.


It clears the DNS table on the workstation, allowing it to obtain fresh
data (matching IP addresses to computernames) from the servers. That
seems fairly self-explanatory to me.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns

There's something amiss with your DNS servers, but that's beyond my
knowledge. You might try reposting this question in a newsgroup
dedicated to networking and/or the appropriate Server OS.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell
 
J

johns

This has nothing to do with the dhcp server. It is working
fine, and the workstations have their normal ip-addresses.
It is the license server that will not respond without the
resolver cache being cleared ?????

johns
 
J

johns

#1. If you are going to "support 10 or more CATIA workstations",
you will do well to re-think your aversion to the "jargon" of your
job.

No way. That is the first sign of somebody who doesn't know
beans, and tries to cover it with obscure jargon. I learned that
40 years ago. Straight talk is the only way to maintain networks.
#2. If you have a problem with a CATIA licensing server,
why do you not visit CATIA technical support?

Because that is IBM tech support. Ever tried that ? :)
Life is short. Generally I get best info from the gamers
groups. I've found that most of them are pros in the field, and
they've seen it all. IBM hires morons, and all they do is blame
the user for the problems. That is also true for nearly all the
professional tech support groups .. jargon users who don't
know much. I guarantee some kid out there has solved this
problem while hacking his house network ... and I'll get a
good answer from him.
#3. For future reference -- Server Operating issues are best addressed in
newsgroups dedicated to a Server OS, rather than in a Workstation
newsgroup.

This is a Workstation problem .. not a dns problem. It may be
the QGhost trojan, or something like that. I can't tell yet.
Note: It sounds like obtaining CATIA license lease is tied to obtaining a
DNS leas.
If that is the case, when the length of the CATIA license lease is
shorter
than the length of the DNS lease, the license lease will expire and
remain so
until a new DNS lease is obtained.

HMMMMMM ! That is a thought. The CATIA license is good as long
as CATIA is running on the workstation. It is suppose to expire
immediately when CATIA is shut down. I've checked that, and it works
for a couple of days, and then craps out. ?? We run bootp here, so
if the workstation is shut down and restarted, the DNS server has
to renew the same license each time. That always works with
no problems.

I got to the "kid" in another group. He said put an entry in my host
file, and point the license request application to the ip-address of
the license server. So far that has held for 3 days. Maybe ??

johns
 
P

Poprivet

It is said that some people are their own worst enemies, and I think we have
a case of that here. He's adverse to "jargon" meaning he doesn't want to
know the proper syntax and linguistics to describe a problem completely, or
its workings/troubleshooting/repairing of same, and since only one site hit
him that way, is painting all sites with the same brush. Eventually these
people are exposed and replaced wiht one of the "kids" he refers to, who
WILL do what is necessary to be good at their job.

Pop`
 
J

johns

I'm looking at a possible problem of DNS protocol vs
html protocol. If my license app runs pure dns
protocol, and the license server is looking for html,
that might be a cause of the mix up. Microsoft just
loves to do this kind of thing ... run server access
with a "share" protocol ... like all the print server
appliances do. Try administering one of those
monsters in a network running Unix dns. It will work
if you pipe the share route to WINS ... as long as
you don't put the print server in a domain ... or
try to understand it by reading the jargon at the
Microsoft or HP websites. I think the kid got it.
My host file is holding. Heh!

johns
 
M

Malke

johns said:
I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems. I went to Microsoft, and all I found
there was jargon ... no help.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns
Let's approach this from a different point of view.

1. What operating system is your DNS server running?

2. Is the DNS server the primary domain controller or a separate server?

3. What are the DNS settings for the server and the workstation?
a. The server should only look to itself for DNS with forward/reverse
lookup zones set for Internet access.
b. The workstations should all have static IP addresses and only look
to the server for DNS.

If the DNS settings are *not* as described in Item #3 above, make your
changes to correct this. Here are links which will help with details:

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
DNS and AD FAQs - http://support.microsoft.com/?id=291382


Malke
 
Z

zerof

johns escreveu:
I've read recent posts in this group on this command, but nobody
seems to have a clue as to what it is doing, and why it solves
failed connectivity problems. I went to Microsoft, and all I found
there was jargon ... no help.

Here's the problem I'm seeing. I have 2 CAD workstations running
CATIA. They send a license request to a server in the same subnet.
That works fine for about 2 days, and then CATIA fails to get a
license, and gives an error message. I can open a command
window, and type .. ipconfig /flushdns ... and the license request
restores, and CATIA works fine, until the next time.

I can duplicate this error by simply pulling the lan chord and
starting CATIA. However, when I get the error "normally", I can
ping the license server, browse normally, and obviously the lan
is working fine, and our DNS server is working fine. Only the
license server seems blocked. And that block is very simply
removed by "flushdns" ???????????????????????

What the heck is going on ???? Very soon, I will have to
support 10 or more CATIA workstations, and my morning
duty will be to run around 365 days a year "flushing" the
dns resolver cache. Stupid.

johns
Have you tried: ipconfig /h ?
 
J

johns

1. What operating system is your DNS server running?

This is exactly what I mean by "jargon". This issue has
absolutely nothing to do with my DNS server. As I said,
when CATIA fails, I still have an ip-address ( bootp ) and
I can browse, email, and do anything on the internet
I want to. The DNS server is not involved. It just amazes
me how the average professional out there cannot
problem solve because their focus is entirely on jargon,
and not the actual issue. Like I said, a kid at home
solved this one ... create a host file, and point the
license request manager application at the ip-address
of the license server. Good kid. Knows nothing about
jargon. Bought his network from Walmart.

johns
 
J

johns

Have you tried: ipconfig /h ?

Nope. Just went and read about it. Seems I do
have 2 network connections on the mobos. One
is FireWire 400mbit ??? I tried disabling that
early on, thinking it might be an IRQ thingy ??
But no luck. If the problem ever shows up
again, I'll bang on that door.

johns
 
M

Malke

johns said:
This is exactly what I mean by "jargon". This issue has
absolutely nothing to do with my DNS server. As I said,
when CATIA fails, I still have an ip-address ( bootp ) and
I can browse, email, and do anything on the internet
I want to. The DNS server is not involved. It just amazes
me how the average professional out there cannot
problem solve because their focus is entirely on jargon,
and not the actual issue. Like I said, a kid at home
solved this one ... create a host file, and point the
license request manager application at the ip-address
of the license server. Good kid. Knows nothing about
jargon. Bought his network from Walmart.

johns

I'm very sorry that you feel this way. I'll be careful not to bother you
with my "jargon" ever again.

*plonk*


Malke
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top