I’ll try and keep this brief
I’m replacing my neighbour’s current adsl router, an efficient networks 5861 (provided by bt) with a linksys WAG54GS
the old router looks like this in case your wondering
http://www.andovercg.com/ebay/images/gre-0412.jpg
I wanted to check the old routers config page so I could set the new one up correctly. After finding the manual for the old router on the net, it tells me that the web config address for this router is 192.168.254.254
When trying to access the web config page I just get a very basic blue bt page with 2 options for vpn and another to change the connection login, it looked nothing like what it was supposed to in the manual and didn’t display any dns/dhcp/port forwarding options etc
I gave bt’s tech support a couple of tries, they were pretty useless, with responses such as “I’m sorry that’s not a router we support” even though it was from them
So I plugged the new linksys router in (and set it up from one of the clients), it works perfectly fine with all the clients as they just obtain there ip’s automatically, the server however is a different matter.
The server at present cannot access the internet, despite the fact it’s all plugged in fine I can’t even ping the router from the server let alone view the linksys config page.
I decided to plug the old router back in since I couldn’t get the new one working with the server, once plugged back in, the old router failed to power up and is now as dead as the dodo – doh!!!
The server is used as an incoming mail server and file server, it is running windows 2000 advanced server
I’ll point out now that it was not me who set the server up
I’ll also point out that I don’t have any experience of setting up a dns/dhcp/gateways as it’s not something I’ve ever needed to do before
I could probably get net access working on the server if I set all the ip settings to auto but it needs a static ip for all of the clients to get their mail
I presume that the reason the server can’t connect to the net is to do with the ip settings gateway/dns etc though I’m not sure how to fix it myself, the server is also acting as a dns (I think) not sure why though as the clients do not need it to (maybe the mail server app needs it?)
Here is what the ipconfig of the server looks like
There is also a program called wingate running in the sys tray, I’m not sure if this is actually doing anything or just a relic from when the server used to run win nt and share the 56k net connection with the clients
http://homepage.ntlworld.com/pengwinzz/Image5.jpg
Here is what the working ipconfig of one of the clients looks like
http://homepage.ntlworld.com/pengwinzz/Image6.jpg
Can anybody please help me out and let me know what I need to change to get the server working again?
I’m replacing my neighbour’s current adsl router, an efficient networks 5861 (provided by bt) with a linksys WAG54GS
the old router looks like this in case your wondering
http://www.andovercg.com/ebay/images/gre-0412.jpg
I wanted to check the old routers config page so I could set the new one up correctly. After finding the manual for the old router on the net, it tells me that the web config address for this router is 192.168.254.254
When trying to access the web config page I just get a very basic blue bt page with 2 options for vpn and another to change the connection login, it looked nothing like what it was supposed to in the manual and didn’t display any dns/dhcp/port forwarding options etc
I gave bt’s tech support a couple of tries, they were pretty useless, with responses such as “I’m sorry that’s not a router we support” even though it was from them
So I plugged the new linksys router in (and set it up from one of the clients), it works perfectly fine with all the clients as they just obtain there ip’s automatically, the server however is a different matter.
The server at present cannot access the internet, despite the fact it’s all plugged in fine I can’t even ping the router from the server let alone view the linksys config page.
I decided to plug the old router back in since I couldn’t get the new one working with the server, once plugged back in, the old router failed to power up and is now as dead as the dodo – doh!!!
The server is used as an incoming mail server and file server, it is running windows 2000 advanced server
I’ll point out now that it was not me who set the server up
I’ll also point out that I don’t have any experience of setting up a dns/dhcp/gateways as it’s not something I’ve ever needed to do before
I could probably get net access working on the server if I set all the ip settings to auto but it needs a static ip for all of the clients to get their mail
I presume that the reason the server can’t connect to the net is to do with the ip settings gateway/dns etc though I’m not sure how to fix it myself, the server is also acting as a dns (I think) not sure why though as the clients do not need it to (maybe the mail server app needs it?)
Here is what the ipconfig of the server looks like
There is also a program called wingate running in the sys tray, I’m not sure if this is actually doing anything or just a relic from when the server used to run win nt and share the 56k net connection with the clients
http://homepage.ntlworld.com/pengwinzz/Image5.jpg
Here is what the working ipconfig of one of the clients looks like
http://homepage.ntlworld.com/pengwinzz/Image6.jpg
Can anybody please help me out and let me know what I need to change to get the server working again?
, thanks again