![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
OK, everything has been fine, come in this morning and the connection to the mvbase server is taking about 30 to 45 secounds to connect. No new hardware added. Patches up to date. I use the IP adrr. have no problem pinging server. Once I am connected, it is fine. this is just the connection to the MVbase server. Have not changed anything in the router. any ideas???? |
#3
| |||
| |||
|
|
What is the connection with mvTERM like? Have you stopped and started the mv Workstation? Do you have anything else on the networj you can try a telnet to and see how long that takes? Do you have anything that can monitor network traffic? Have you done a LISTLINES recently to see if you have any dead sessions that have not been disconnected yet? Just a few quick thoughts Craig spayne (AT) jitservices (DOT) com> wrote in message news:1164655719.113618.37260 (AT) n67g2000cwd (DOT) googlegroups.com... OK, everything has been fine, come in this morning and the connection to the mvbase server is taking about 30 to 45 secounds to connect. No new hardware added. Patches up to date. I use the IP adrr. have no problem pinging server. Once I am connected, it is fine. this is just the connection to the MVbase server. Have not changed anything in the router. any ideas???? |
#4
| |||
| |||
|
|
OK, everything has been fine, come in this morning and the connection to the mvbase server is taking about 30 to 45 secounds to connect. No new hardware added. Patches up to date. I use the IP adrr. have no problem pinging server. Once I am connected, it is fine. this is just the connection to the MVbase server. Have not changed anything in the router. any ideas???? |
#5
| |||
| |||
|
|
spayne (AT) jitservices (DOT) com> wrote in message news:1164655719.113618.37260 (AT) n67g2000cwd (DOT) googlegroups.com OK, everything has been fine, come in this morning and the connection to the mvbase server is taking about 30 to 45 secounds to connect. No new hardware added. Patches up to date. I use the IP adrr. have no problem pinging server. Once I am connected, it is fine. this is just the connection to the MVbase server. Have not changed anything in the router. any ideas???? Don't know much about MV base, but I know I had exactly the same problem with a D3 Linux box one time. I eventually traced it back to a DNS issue. Even though the client was connecting using IP addresses, (like you), correcting the DNS entries on the RedHat box resolved the problem whereby they were connected to the box, but had to wait 30 seconds or so for the D3 Login prompt. (Their ISP had changed the addresses of their DNS servers and retired the old ones after about six months. They'd been sent warnings and had reconfigured routers, etc. but didn't see the need to make the changes on the RedHat box. By the time the old DNS servers were retired, the client had completely forgotten about the configuration changes.) Hope that helps. With Kindest Regards Mike Wooding |
#6
| |||
| |||
|
|
Mike Wooding wrote: spayne (AT) jitservices (DOT) com> wrote in message news:1164655719.113618.37260 (AT) n67g2000cwd (DOT) googlegroups.com OK, everything has been fine, come in this morning and the connection to the mvbase server is taking about 30 to 45 secounds to connect. No new hardware added. Patches up to date. I use the IP adrr. have no problem pinging server. Once I am connected, it is fine. this is just the connection to the MVbase server. Have not changed anything in the router. any ideas???? Don't know much about MV base, but I know I had exactly the same problem with a D3 Linux box one time. I eventually traced it back to a DNS issue. Even though the client was connecting using IP addresses, (like you), correcting the DNS entries on the RedHat box resolved the problem whereby they were connected to the box, but had to wait 30 seconds or so for the D3 Login prompt. (Their ISP had changed the addresses of their DNS servers and retired the old ones after about six months. They'd been sent warnings and had reconfigured routers, etc. but didn't see the need to make the changes on the RedHat box. By the time the old DNS servers were retired, the client had completely forgotten about the configuration changes.) Hope that helps. With Kindest Regards Mike Wooding My guess is that Mike has the answer. We had the problem a couple of times on a D3/Linux box and Doug Dimitru checking the Linux file that holds the DNS addresses and like Mike, this solved our problems. I am not at work (and not a linux guru) so I can't remember the file but I will email it again from work tomorrow unless someone has sent the information or you have indicated whether or not this solved the problem Good luck Bob Marik |
![]() |
| Thread Tools | |
| Display Modes | |
| |