OK guys its in the home network. Not the ISP. the Gateway machine will connect to chat. All the clients will not. Something has changed in the set up and despite reseting up home network several times no luck. Got any clues?
Java Jive!
Collapse
X
-
-
dave_p
i love the manhatten transfer
killer joe
my cat fell in the well
airegin
all that good stuff!
any hoo, is your gateway also acting as a firewall?, may need to forward some ports.
if not, well?
heres a good place toget answers:
Comment
-
yes it is. but it was for months up until something reset after a power glitch the last week. And its showing some DNS settings in it. I wonder if I plug those same ones into the clients it would work?Comment
-
I could be wrong, but wouldn't changing the DNS in the clients defeat the purpose of a gateway?
It sounds more like the clients don't have premissions to use the gateway, or the client DNS isn't pointing to the gateway anymore.
It could be ports, but I would think that is also controlled in the Gateway machine. (6667 - IRC )Go with the Flow
___________________
AIM:bman1967
AO Feedback Thread
eBay Feedback
PB Nation Feedback ThreadComment
-
Sorry -
I forgot to add.
Start - Run - Type "Command"
Will bring up the MSDos Prompt
You can then type "Tracert irc.automags.org" and start a trace route session of the hops to the irc serverGo with the Flow
___________________
AIM:bman1967
AO Feedback Thread
eBay Feedback
PB Nation Feedback ThreadComment
-
Well I donno if its not allowing it to be used why am I online? its just DNS stuff that seems affected...
Pointing? All three of em changed not the one? that could happen I suppose but they are set up in sequential IP's and sharing internet connection right now. Why not DNS?
Something is real fish to me that the DNS routes are not being allowed at the client. But I am grasping at straws now!
This set up is rather odd too. its satellite using a modem run into the Gateway which is running software to decode the satellite signals and one machine must run that for the others to take advantage of. its doing it for Internet. and was for DNS up until that power flicker. Maybe I should try reloading that Satellite software to see if its in error?Comment
-
CPhilip,
Did you try using 67.97.255.231 instead of irc.automags.org?
They are one and the same, If you can ping the IP# and not the .org then I would agree that you seem to have a DNS problem.
If you can't reach either IP# or the .org using ping or tracert then the problem isn't DNS.
I sounds like you are running a multi-homed machine, that is working correctly.( the gateway sattelite machine) I understand that the IP addresses of the clients are static, but the gateway address (in the IP setup of the client) of each client should be the IP of the gateway machine. (sorry that is what I ment by Point to the Gateway )
Also, if you can browse the web in any machine, I would think that the DNS server is doing it's job of resolving the host name to the IP address.
I'm just speculating anyway... I have only dealt with Proxy servers.Go with the Flow
___________________
AIM:bman1967
AO Feedback Thread
eBay Feedback
PB Nation Feedback ThreadComment
-
Phil...did you try an "IP release", then "IP renew"on the client machines?. They may have lost the static IPs.Comment
-
Cphilip: If you have a dynamic IP address, just remove the DNS servers from your router and set them to be obtained automatically. If you don't have a dynamic IP, this won't work, but this will ensure you have the most up to date servers that are being provided via DHCP.
Pinging automags.org [67.97.255.231] with 32 bytes of data:
That is the IP I'm getting. Try pinging that and see if it responds (it certainly should!!)
If you use mIRC or some other IRC client, you can then try connecting to the chat server by connecting to that IP. If you use the java chat, I don't think you have that option.Comment
-
Shirow, not using a router just a simple hub. At this point all set to sequential IP's on the clients. 192.168.0.1 for the Gateway and then 192.168.0.2 and so on for the clients. I coulda sworn I had it set origainaly at all clients and the gateway were 192.168.0.1. And now it refuses to let me use that for all of them as it sees them as being used. before I swear it didn't and then when this happened before I was able to get everything working even DNS through sequential IP numbering like it is now. But when this happened again last week all I could get up and running was Internet connections. I did find the Gateways sharing connection IP reset to 192.168.2.1 this time. I changed it back to 192.168.0.1 and set all the clients to 192.168.0.X at least the internet came back up on them like before but unlike before the chat stuff would not work now. Because everything is working on the gateway I am fairly certain the problem is in there somewhere in how its connection is sharing through the home network. Just do not know what or where.
Army, I slapped it silly several times!
Tuna, I am plugging in static IP's. thats the only way to get it to work. See above. If I allow it to find its own it will always chose the wrong one. I can get internet with the way I am pluggin them in but not DNS this time.Comment
-
What OS are you using? I know when I upgraded some of my systems' OSs I had a heck of a time getting everything to work right again... yeah, I know, upgrading is suppose to make things run BETTER...

www.ShartleyCustoms.com
Custom Paintball Products and Accessories
CLICK HERE to Check out our PDU SERIES GEAR!
its more like a paper cut that has primadonna's yelling murder... - GlickmanComment
-
XP on the Gateway and the Client laptop with OS 10.2 on the iMacs but none of that has been upgraded in a while and was working fine on all of them up till the power outage that seemed to cause the complete reset. That has happened twice now from power blinks. First time it reset up farily easy and DNS came back too. this time thats all that will not. So something reset up wrong that did not do so last time. Changes occured to the network set up for some reason I do not understand. The power back up was not plugged in but you can bet your life it will be after I get it all up this time!!!Comment
-
It must be a router if you're using 192.168.0.x because you must be using network address translation. Hubs can't do that. The clients will all have to be a different IP, pointing to the router - they can't all use the same IP address, if I'm understanding what you're saying correctly.Shirow, not using a router just a simple hub. At this point all set to sequential IP's on the clients. 192.168.0.1 for the Gateway and then 192.168.0.2 and so on for the clients. I coulda sworn I had it set origainaly at all clients and the gateway were 192.168.0.1. And now it refuses to let me use that for all of them as it sees them as being used. before I swear it didn't and then when this happened before I was able to get everything working even DNS through sequential IP numbering like it is now. But when this happened again last week all I could get up and running was Internet connections. I did find the Gateways sharing connection IP reset to 192.168.2.1 this time. I changed it back to 192.168.0.1 and set all the clients to 192.168.0.X at least the internet came back up on them like before but unlike before the chat stuff would not work now. Because everything is working on the gateway I am fairly certain the problem is in there somewhere in how its connection is sharing through the home network. Just do not know what or where.
Army, I slapped it silly several times!
Tuna, I am plugging in static IP's. thats the only way to get it to work. See above. If I allow it to find its own it will always chose the wrong one. I can get internet with the way I am pluggin them in but not DNS this time.
If you're running Windows XP or 2k, try this:
Click Start, Run, type cmd
Type nslookup irc.automags.org
Then try nslookup irc.automags.org 64.4.207.8
See if they differ. I think they probably will.. if they do, it's a DNS problem. Call up your ISP and tell them that you can't resolve automags.org - it's very, very easy to fix. Now if it works OFF the router, then there is some problem with the dns inside the router. The easiest thing to do is, again, call your ISP and find out the DNS server IPs and put them in the router and try again. Punch it into each client too, if you're using static IPs - they won't pull the information automatically unless you use DHCP.
What I would do if I was you would be to reset your router to its defaults, punch in whatever information is required to make a connection and leave everything else to be obtained automatically. Then turn on private DHCP inside the router and set each client to obtain an IP/DNS info automatically. From what you're saying, it sounds like that would probably fix it.Comment







Comment